2.13.0-beta.20). Features may change before the next stable release.Switch to stable →Choose a Kit
Compare the public Engineer and Marketing Kits, then choose the one that matches your work.
A Kit is a versioned package of Skills, Agents, runtime automation, rules, and supporting files for a related kind of work. You install a Kit for a chosen runtime, then invoke the Skill that matches the outcome you need.
The public Kit lineup has two choices: Engineer and Marketing. Choose by the work you need to finish, not by the runtime you use. Both Kits can be projected for Claude Code, Codex, and Cursor, but each runtime activates packaged capabilities differently.
Choose by your primary outcome
| Kit | Best fit | Typical outcomes |
|---|---|---|
| Engineer Kit | Software delivery and technical maintenance | Clarify and plan a change, implement a feature or fix, debug a failure, review code, run verification, or prepare work for release. |
| Marketing Kit | Marketing planning and execution | Research a market or audience, define positioning, create content or campaign assets, improve a funnel, analyze performance, or plan conversion work. |
Start with the Kit that owns your primary deliverable. For example, use Engineer when the deliverable is a tested product change, even if the work includes a landing page. Use Marketing when the deliverable is campaign strategy or conversion content, even if the workflow needs light technical support.
Some Skill names appear in both Kits. The name alone does not mean the workflow or supporting content is identical, so use the version from the Kit selected for your work.
Invoke Skills in each runtime
After installation, use the invocation style of the selected runtime:
| Runtime | Skill invocation | What to know |
|---|---|---|
| Claude Code | /ak:<skill> | For example, /ak:cook. Native delivery is the default; plugin delivery is an explicit install choice. |
| Codex | $ak:<skill> | For example, $ak:cook. Codex translates supported Kit capabilities, but some automation is partial or unavailable. |
| Cursor | /ak:<skill> | Cursor's slash-command picker uses entries such as /ak:cook. This invocation spelling is user-verified and does not establish equivalent support for every packaged capability. |
Read Runtime adapters before assuming that a Skill, Agent, Hook, rule, or statusline behaves the same across runtimes.
Install and confirm access
Released Kits are resolved through the authenticated AgentKit registry and
require an entitlement for the selected Kit. Complete
Onboarding, then run ak licenses to inspect
the grants available to the signed-in account.
Each installation targets one runtime and one scope. Follow Installing kits to choose project or user scope, select Claude Code native or plugin delivery, install a smaller Skill set, and verify runtime discovery. The guide provides the exact commands and supported flags.
Keep lifecycle changes safe
Refresh, delivery-mode changes, and uninstall use AgentKit ownership evidence and recovery snapshots. Normal lifecycle operations preserve unknown or user-modified content instead of treating an entire runtime directory as Kit content.
Before changing an install, read Projects, artifacts, and checkpoints for the ownership and recovery model. Use the matching target, scope, and delivery mode from the original install, and review every preview before applying it.
Explore the Kits
- Open Engineer Kit for its software-delivery workflow, included components, runtime boundaries, and first guided task.
- Open Marketing Kit for its marketing workflow, included components, runtime boundaries, and first guided task.
- Open Workflow guides for complete Skill chains covering software delivery, marketing growth, and cross-Kit product launches.