Claude Code
Native or explicit plugin delivery. Skills, agents, slash commands, rules, hooks, and status line can be active at project or user scope.
AgentKit · Adapters
AgentKit Runtime Support
How adapters deliver Kits into coding agents — not a full parity matrix.
Model
An adapter is a compatibility boundary
Coding assistants do not share one file layout, tool set, or lifecycle model. A runtime adapter converts a Kit into surfaces that assistant can discover and use. Without an equivalent, AgentKit may keep supporting content, drop with a warning, or report unsupported.
Invocation
Confirmed invocation syntax
Syntax and supported surfaces vary by runtime.
| Runtime | Syntax | Examples |
|---|---|---|
| Claude Code | /ak:<skill> | /ak:cook /ak:plan |
| Cursor | /ak:<skill> | /ak:cook /ak:plan |
| Codex | $ak:<skill> | $ak:cook $ak:plan |
Expectations
Each runtime has its own reality
Codex
Native skill discovery and agent dispatch. Partial Hook support — some groups drop/narrow. No status line. Command files may stay supporting content.
Cursor
Projects skills, agents, rules, hooks. Live install/update/invocation coverage is incomplete across setups — do not infer full parity.
Beyond the three above
Other runtimes can still load AgentKit skills
Some coding agents can still read/discover AgentKit skills (often via standard skill folders), but AgentKit does not commit full harness support: hooks, adapter install/update, status line, or command parity like Claude Code / Codex / Cursor. Loading skills ≠ official support.
OpenCode Skills load — not full harness 
Grok Skills load — not full harness 
Cline Skills load — not full harness Do not infer install/update/invocation parity just because a skill appears in the agent. Check the install summary and real behavior on your runtime.