Agent skill · Frontend

observal-registry

Submit, browse, install, edit, archive, restore, transfer, and version MCPs, skills, hooks, prompts, and sandboxes in the Observal registry, and get components recommended for the current user. Use when the user wants to submit a component, install one, edit a draft, publish a new version, browse the component library, or asks what they should install or are missing.

Observalgithub.com/ObservalGitHub ↗
claude-codecodexcursorApache-2.0
Install
npx skills add Observal/Observal --skill observal-registry --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 12 KB
Bundled scripts: none
Version: 2.1.0
Path: observal_cli/skills/observal-registry/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,254
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Observal Registry: Component CRUD ## Critical Rules 1. **EXECUTE commands**: run them in your shell. Set timeout to 60 seconds. 2. **Pass `--output json`** on list/show commands. 3. **Pass `--yes`** on destructive lifecycle commands (`archive`, `unarchive`) and MCP JSON submit when defaults are acceptable. 4. **When in doubt about a flag, run `<command> --help` first.** 5. **`--from-file` does NOT exist on `mcp submit`**: that flag is on `mcp edit`. --- ## Procedure: Browse Registry Use natural-language keywords with `--search`; do not require exact whole-query matches. ```bash observal registry mcp list --category developer-tools --output json observal registry mcp list --namespace platform-tools --output json observal registry skill list --namespace platform-tools --output json observal registry skill list --team platform-tools --search 'frontend design' --output json observal registry skill list --task-type code-review --harness claude-code --output json observal registry hook list --event UserPromptSubmit --output json observal registry prompt list --category coding --output json observal registry sandbox list --runtime docker --output json observal registry mcp my --output j

What's inside
Steps it walks through
  1. Critical Rules
  2. Procedure: Browse Registry
  3. Procedure: Recommend Components For This User
  4. Procedure: Submit Component
  5. MCP
  6. Skill
  7. Hook
  8. Prompt
  9. Sandbox
  10. Procedure: Install Component
  11. Procedure: Edit Component
  12. Procedure: Publish Component Version
  13. Procedure: Archive / Restore Component
  14. Procedure: Manage Co-Authors
Commands it runs
observal registry mcp list --category developer-tools --output json
observal registry mcp list --namespace platform-tools --output json
observal registry skill list --namespace platform-tools --output json
observal registry skill list --team platform-tools --search 'frontend design' --output json
observal registry skill list --task-type code-review --harness claude-code --output json
observal registry hook list --event UserPromptSubmit --output json
observal registry prompt list --category coding --output json
observal registry sandbox list --runtime docker --output json
observal registry mcp my --output json
observal registry skill my --output json
More from Observal
All skills →
About this skill
What does the observal-registry skill do?

Submit, browse, install, edit, archive, restore, transfer, and version MCPs, skills, hooks, prompts, and sandboxes in the Observal registry, and get components recommended for the current user. Use when the user wants to submit a component, install one, edit a draft, publish a new version, browse the component library, or asks what they should install or are missing.

How do I install it?

Run `npx skills add Observal/Observal --skill observal-registry --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.

Keep going