observal
Core Observal CLI operations: pull agents into your harness, scan installed components, diagnose and patch harness configs, authenticate, manage CLI settings, get components recommended for you, and discuss agent insights. Use when the user wants to install an agent, check setup, login, configure the CLI, ask what they should install, or ask how an agent is doing.
npx skills add Observal/Observal --skill observal --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Observal: Core CLI Operations ## Critical Rules 1. **EXECUTE commands**: run them in your shell, do not just display them. 2. **Set timeout to 60 seconds**: most commands make HTTP calls. 3. **Use single quotes** for `--prompt` and `--description` values to avoid shell quoting issues. 4. **Do NOT run `observal auth status` first.** Other commands surface auth problems clearly on their own. 5. **When in doubt about a flag, run `<command> --help` first.** Never guess flag names. 6. **Pass `--output json` on every list/show command.** It is stable and machine readable. 7. **Pass `--yes` / `-y` on destructive commands** so they do not block on a confirmation prompt. 8. **Use canonical registry identities:** prefer the returned `qualified_name` (`namespace/slug`) for agent and component show, install, pull, archive, and transfer commands. Bare names work only when unambiguous. 9. **Resolve 409 conflicts deterministically:** if the error says a name is ambiguous, retry with `namespace/slug`; otherwise use `--update` for in-place edits or `--bump` for versioned releases. 10. **Only fall back to local file writes** if a command exits with `Connection failed` or `Not configured`. 11. **Ne
- Critical Rules
- Procedure: Natural-Language Registry Search
- Procedure: Pull Agent
- Procedure: Outdated
- Procedure: Scan harnesses
- Procedure: Doctor
- Procedure: Doctor Patch
- Procedure: Doctor Cleanup
- Procedure: Auth
- Procedure: Teamspaces
- Procedure: CLI Config
- Procedure: Discuss Agent Insights
- Error Reference
- Output Contract
observal agent list --search 'incident resolution' --output json observal registry skill list --search 'frontend design' --output json observal registry skill list --team platform-tools --search 'frontend design' --output json observal registry mcp list --search 'github docker' --output json observal agent pull NAMESPACE/AGENT_SLUG --harness kiro --no-prompt --dir . observal scan --harness kiro observal outdated observal outdated --harness claude-code --output json observal scan observal scan --harness claude-code
What does the observal skill do?
Core Observal CLI operations: pull agents into your harness, scan installed components, diagnose and patch harness configs, authenticate, manage CLI settings, get components recommended for you, and discuss agent insights. Use when the user wants to install an agent, check setup, login, configure the CLI, ask what they should install, or ask how an agent is doing.
How do I install it?
Run `npx skills add Observal/Observal --skill observal --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Observal/Observal, a repository with 2,254 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.