arthai-marketplace

/skills

Browse the installed skill catalog — filter by category or keyword, see what each slash command does.

Synopsis

/skills [category|keyword]

When to use it

• You forgot which slash command does the thing you want and don’t want to wait for the once-per-session routing table to scroll back
• You just installed a bundle and want to see what /-commands it added
• You want to scope a category — “what’s in Quality?” — before picking a workflow
• Not for: deciding which command fits a specific task — that’s /routing, which scores the task and recommends a route

Quickstart

/skills

What you’ll see: every user-invocable skill installed in this project, grouped by category, each with its one-line description — generated live from the manifest, so it always matches what’s actually installed.

Examples

/skills              # full catalog, grouped by category
/skills quality      # skills matching "quality" in name, description, or category (currently: the Quality category)
/skills deploy       # keyword match across name + description (deploy, deploy-ios…)
/skills consulting   # everything in the consulting bundle

Example output for /skills quality:

## Skills catalog (2 skills, filter: 'quality')

### Quality
- `/qa` — Run QA checks.
- `/qa-learn` — Review QA knowledge base stats, prune stale entries.

Arguments

Argument	Values	Default	What it does
filter	category name or keyword	none (show all)	Narrows the catalog: matches if the filter string appears anywhere in a skill’s name, description, or category name — a single combined search, not separate strategies per field. Results are still grouped by each skill’s real install category, so a match on a different field can pull in a skill from a category you didn’t expect.

What it does

1. Reads portable.manifest (the source of truth) and each skill’s frontmatter, so the catalog can never drift from what is installed.
2. Skips skills marked user-invocable: false (internal helpers other skills use).
3. Maps each skill to its install category so the grouping matches how it was installed.
4. Applies the optional filter (category or keyword) and prints the grouped catalog. No agents are spawned — it’s a local read, effectively zero cost.

Output & artifacts

• A grouped, formatted catalog printed into the conversation. Nothing is written to disk.
• If the filter matches nothing, the list of available categories is shown instead.

Troubleshooting

Problem	Fix
skills catalog: manifest not found	The toolkit isn’t installed where expected; run ~/.claude-agents/install.sh --status to confirm the install path
A skill you expect is missing	It may be user-invocable: false (internal) or not installed in this project’s bundle — check with /skills unfiltered, or install the bundle that contains it
Empty result for a real category	Category names are lowercase (e.g. quality, operations) and come from install.sh’s install categories/bundles, not from the skill’s own frontmatter — try /skills unfiltered to see valid category names, or use a keyword instead

Related

• /routing — score a specific task and get a recommended route
• /onboard — full project briefing with prioritized next steps
• Skills reference — the complete generated index