ScBee
Fix it

rifqifitriady/ZAAFPulse: files to add.

Starting points for the files agents look for, made by fixed templates from public facts. Anything only you know is marked TODO. Read each one, edit it, then add it to your repo yourself. ScBee never changes your repo.

llms.txt

A short description models can read first.

# ZAAFPulse

> ZAAFPulse: AI command center for macOS, Linux and Windows. Observability for Claude Code and Codex (usage, cost, quality, second brain over 15 sources) plus an agentic workspace

## Docs
- [README](https://github.com/rifqifitriady/ZAAFPulse#readme): what it is and how to install it
- [Source](https://github.com/rifqifitriady/ZAAFPulse): the code
- [Licence](https://github.com/rifqifitriady/ZAAFPulse/blob/HEAD/LICENSE): MIT

AGENTS.md

Instructions for coding agents that work inside the repo.

# ZAAFPulse

ZAAFPulse: AI command center for macOS, Linux and Windows. Observability for Claude Code and Codex (usage, cost, quality, second brain over 15 sources) plus an agentic workspace

## Build and test
- Install: TODO
- Test: TODO
- Run: TODO

## Conventions
- TODO: the rules a new contributor (or agent) must follow

## Do not
- TODO: files or actions that are off limits

agent.json

A card other agents can read: what this is and what it can do.

{
  "name": "ZAAFPulse",
  "description": "ZAAFPulse: AI command center for macOS, Linux and Windows. Observability for Claude Code and Codex (usage, cost, quality, second brain over 15 sources) plus an agentic workspace",
  "url": "https://github.com/rifqifitriady/ZAAFPulse",
  "skills": [
    {
      "name": "TODO: what it can do",
      "description": "TODO: one sentence"
    }
  ]
}

Starting something new? The agent-ready starter is a GitHub template with all of these files, two skills and this check in CI from the first commit.

Back to the score