ahood

A public registry for AI agent skills — browsable, searchable, and downloadable.

Why ahood

You write the same instructions over and over

Every new project starts with pasting the same prompts, conventions and guardrails you wrote last time — slightly differently, every time.

Your agent finds and installs them for you

Point your agent at ahood's MCP server and it discovers the right skill and installs it mid-task — no copy-paste, no context switch.

Three ways in

Whichever fits how you already work.

CLI: install and publish from your terminal
Registry: browse and search what others shipped
MCP: let your agent do both, on its own

Quick start

Install the CLI

Pick your package manager.

npm i -g @ahood/cli

Or run a single command without installing anything: npx @ahood/cli@latest <command>

Set up an AI agent

Paste this into Claude Code, Cursor, or any coding agent.

You are helping me set up the ahood CLI so I can install and use skills from https://ahood.vercel.app in this project.

1. Install the ahood CLI: `npm i -g @ahood/cli` gives you a persistent `ahood` command, used in every step below. For a single one-off command instead, run `npx @ahood/cli@latest <command>` without installing anything. To build from source instead: https://github.com/AlexKay28/ahood-cli, `npm run build`.
2. Run `ahood login`. It prints a URL for a device-code login -- open it in a browser and approve it there; the CLI stores the resulting token at ~/.config/ahood/credentials.json.
3. Use `ahood skill search <query>` to find skills relevant to what we're building, and `ahood skill add <owner>/<skill>[@version]` to install one into .claude/skills/<owner>/<skill>/, pinned in .claude/skills.lock.json. Check the lockfile afterward to confirm the pin landed.
4. `ahood skill update [<owner>/<skill>]` moves an existing pin forward to the latest version; `ahood skill remove <owner>/<skill>` uninstalls and unpins.
5. If I ask you to publish something: run `ahood skill publish <owner>/<skill>@<version>` from a folder containing SKILL.md. If the skill doesn't exist yet, add `--name "<Display Name>"` (and optionally `--tagline`/`--tags`/`--license`) to create it as part of that same publish -- there's no separate create step. New skills are created private; if I want it publicly discoverable, run `ahood skill edit <owner>/<skill> --visibility public` afterward. The publish command uploads then polls until the version finishes processing server-side, printing "Published ..." on success or the real failure reason if it doesn't.
6. Agents are a second artifact kind, parallel to skills: a folder with AGENT.md (persona/behavior definitions) instead of SKILL.md. Publish one the same way but add `--kind agent` (auto-detected and optional if the folder only has AGENT.md). `ahood skill add` then installs it to .claude/agents/<owner>@<agent>.md instead of .claude/skills/, automatically based on the artifact's kind -- no extra flag needed on `add`.
7. MCP servers are a third artifact kind: a folder with server.json (the MCP server manifest) at its root instead of SKILL.md/AGENT.md. Publish one the same way but add `--kind mcp` (auto-detected and optional if the folder only has server.json). `ahood skill add` then merges the install into the installing project's .mcp.json instead of writing into .claude/, prompting for any server.json `environment_variables` marked secret that aren't already set in your shell.
8. For CI or any non-interactive environment, use the AHOOD_TOKEN environment variable instead of `login` -- every command checks it first.

Confirm you understand the install step above, then go ahead.

Full docs