/toolkit

Present the capabilities of Bharat's Claude Toolkit to the user: the vendored skills/agents grouped by domain, plus the always-on external plugins. Be a navigator, not a parser — keep the output scannable.

Sources of truth (read these; do NOT hardcode the catalog)

1. SKILLS.md at the repo root — the generated inventory of every vendored skill and agent. This is the authoritative list of what exists.
   • If SKILLS.md is missing, do not fail silently. Tell the user the catalog hasn't been generated yet and to run: python scripts/validate_skills.py --catalog (or the repo's bootstrap step) to produce it, then re-run /toolkit. Stop there.
2. settings.json at the repo root — read enabledPlugins to list the always-on external plugins (every entry whose id is NOT bharats-claude-toolkit@bharats-claude-toolkit-dev).

Read both at invocation time. Never embed a static skill list in this command — the catalog is regenerated by the freshness gate and must not drift.

Grouping the vendored skills BY DOMAIN

SKILLS.md is a flat list. Re-group it into the human-facing domain taxonomy below (the same one in the README). Place each skill/agent from SKILLS.md under the domain it belongs to. Any skill you cannot map to a domain goes in an Other bucket — never drop a skill silently.

Domains:

• Workflow & engineering
• Architecture & planning (agents)
• Building AI products
• Python & data
• Frontend & React
• Design & UI polish
• Copywriting & content
• UX writing
• SEO
• Market & customer research
• Go-to-market
• Full-stack marketing
• Audio & video
• Enterprise layer — with subgroups: Exec & strategy; Commercial & finance; Enterprise sales; Customer success & retention; Business operations; Enterprise software; Compliance-as-code
• Other — anything in SKILLS.md not mapped above

Under each domain, list the skill names (comma-separated or short bullets). One line of context per domain is plenty; this is a map, not documentation.

Always-on external plugins

After the vendored skills, list the enabled EXTERNAL plugins from settings.json enabledPlugins (everything except bharats-claude-toolkit), so the user sees the full always-on surface — e.g. frontend-design, ui-ux-pro-max, web-quality-skills, the pm-* discovery/strategy/execution plugins, and the claude-code-workflows agent/ops/data plugins.

Headline counts

State the headline: always-on = 20 plugins / 114 skills + 4 agents. Where it's cheap, compute the live numbers instead of trusting the headline:

• external plugins = count of enabledPlugins entries in settings.json (≈20),
• vendored skills = count of skill entries in SKILLS.md (≈114),
• vendored agents = count of agent entries in SKILLS.md (4), and report whichever you actually computed.

Reminders to close with

• Skills auto-trigger by their description — the user does not invoke them manually; just work and Claude reaches for the right one.
• To pull more on demand, the firehose is one command away — point to the README cheatsheet (/plugin install ecc@ecc, /plugin install superpowers@superpowers-marketplace, then /reload-plugins).