agentsclimarketplace

Claude code capabilities

Skill ucsandman/claude-code-capability-primer/skills/claude-code-capabilities

Claude Code plugin: injects a capability self-awareness card at session start so Claude actually knows and uses its built-in capabilities — skills, subagents, dynamic workflows, hooks, MCP, plugins, GitHub Actions, the Agent SDK, and more.

Install
npx -y skills add ucsandman/claude-code-capability-primer --skill claude-code-capabilities

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when unsure which Claude Code capability fits a task, when about to single-thread large/cross-cutting/repetitive work, or when you or the user ask what Claude Code can do — loads the full capability map (signal → capability) and points to the deep-dive skills.

SKILL.md

3.4 KB, 714 tokens by cl100k_base, as published. Nobody here has run it

Claude Code Capabilities

This skill is your capability index. Its job: before you plan, single-thread something big, or decide a thing is impossible, make sure you have considered the right built-in Claude Code capability.

Do this now

  1. Read the full map: open references/capability-map.md (in this skill's directory). It maps concrete task signals → the capability to reach for → how to invoke it → which deep-dive skill to read. It also lists the anti-patterns that this primer exists to prevent.
  2. Match the task to a row. If a capability fits, invoke its deep-dive skill (below) for the exact mechanics before implementing.
  3. If nothing fits, proceed normally — not every task needs special machinery. The point is to consider these first, not to force them.

Condensed trigger list (full detail in references/capability-map.md)

SignalCapabilityDeep-dive skill
Repeatable workflow / knowledge you keep re-derivingSkills & slash commandsclaude-code-skills
Research, exploration, big review, 2+ independent tasksSubagents (Agent/Task)claude-code-subagents
Broad audit, migration, fan-out > one contextDynamic workflows (Workflow, ultracode)claude-code-dynamic-workflows
"Each time X, do Y" the harness must enforceHooksclaude-code-hooks
Long build/test/watch, polling external stateBackground agents & tasksclaude-code-background-agents
Undo a bad edit path / restore stateCheckpointing & /rewindclaude-code-checkpointing
Live external tool / API / data sourceMCP serversclaude-code-mcp
Reuse skills/hooks/agents/MCP as a bundlePluginsclaude-code-plugins
Server-side PR / issue automationGitHub Actions (@claude)claude-code-github-actions
Build a custom/headless agentAgent SDKclaude-code-agent-sdk
Task too hard/trivial for current settingEffort, models & fast modeclaude-code-effort-models

Each row's deep-dive skill is a separate skill in this plugin — invoke it with the Skill tool when you are actually doing that kind of work (they auto-surface on the matching signal too).

Staying current (automatic)

This primer keeps itself current:

  • An async SessionStart hook (hooks/auto-update.sh) does a throttled git pull --ff-only so your install tracks the latest merged main, and flags this card when your installed Claude Code is newer than the version the content was generated for (references/.generated-for).
  • A scheduled refresh agent fetches the latest official docs/changelog, adds or updates the card, map, and claude-code-* skills for any new capabilities, verifies every claim against the live docs, and opens a PR — auto-merging only when verification passes (AUTO_MERGE_POLICY = verified; see references/refresh-runbook.md).

To refresh manually: run bash scripts/update-docs.sh, then follow references/refresh-runbook.md in a Claude session.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.