skills-visibility

# Make agent skills discoverable Apply the steps below to publish a catalog of [agent skills](https://agentskills.io/) and make it findable and installable by AI coding agents. An agent skill is a `SKILL.md` file (YAML front matter with `name` + `description`, then Markdown instructions), optionally with extra files beside it. Publishing one skill is easy. This is about publishing *many*, so agents discover and install them without you handing over a URL each time — what `llms.txt` does for pages, done for skills. The mechanism is a discovery index at a well-known path. Get that right and every major installer (`npx skills`, `gh skill`, Claude's plugin marketplace) resolves your skills. ## Workflow Steps 1–5 build on each other. Steps 6–8 are independently shippable. ### 1. Author each skill in a Git repo Lay each one out as `skills/<name>/SKILL.md`. A repo is a hard requirement rather than a convenience, because two install paths resolve *directly* from it: - `gh skill install <owner>/<repo> <name>` reads `SKILL.md` straight from the repo. - Claude's plugin marketplace installs from a repo with a `.claude-plugin/marketplace.json` at its root; the `name` in that manifest is the `@marketplace` half of `claude plugin install <skill>@<marketplace>`. The repo is also where the skill is reviewed, versioned, and improved. Treat a skill like code, because it is. ### 2. Decide each skill's shape Three shapes, handled differently at every layer. Classify each skill before p...