AI ecosystem support

Cratis authors one passive skill tree and generates the wrapper each host expects. A wrapper changes packaging and discovery—not the behavior of the skill. This keeps a projection workflow or event-modeling workflow consistent when your team uses different assistants.

Current matrix

Ecosystem	Generated form	Current evidence	Public install status
Agent Skills	`skills/<name>/SKILL.md`	Format and name/frontmatter validation	Blocked pending an approved target
Claude Code	Skills-only plugin and marketplace	Strict validation plus isolated install/list/remove smoke	Blocked pending an immutable release
OpenAI Codex / ChatGPT	Skills-only Codex plugin and marketplace	Manifest generation and Codex marketplace add/remove smoke	Blocked; ChatGPT desktop review remains
GitHub Copilot	Skills-only plugin and marketplace	Isolated marketplace install/list/remove smoke	Blocked pending an immutable release
Cursor	Skills-only Cursor plugin and marketplace	Manifest and canonical-byte parity	Blocked; Cursor host and vendor review remain
Kiro	Agent Plugins 1.0 skills-only power	Agent Plugin manifest and canonical-byte parity	Blocked; Kiro host review remains
Junie	Skills-only Junie extension	Extension manifest and canonical-byte parity	Blocked; Junie host review remains
Gemini CLI	Skills-only extension	Isolated link/list/remove smoke	Blocked pending an immutable release
Pi	Passive `pi-package` npm layout	Isolated install/list/remove smoke	Blocked pending package ownership and release
npm	`@cratis/ai` passive tarball	Pack/install/uninstall with scripts disabled	Blocked pending trusted publishing

What every adapter must preserve

Every generated target must contain the same approved SKILL.md, references, assets, and required licenses. Target-native manifests may add names, versions, and discovery roots, but they may not redefine workflow behavior.

The passive package excludes:

lifecycle scripts and executable extensions;
MCP implementations and credentials;
engineering rules, agents, hooks, prompts, evals, and authoring tooling;
project-specific context;
private product or Strategy content.

Why installation is still closed

Packaging is working, but packaging is not approval. Public installation opens only after one Cratis product owner approves exact source bytes and claims, the target passes behavior and collision evidence, an immutable generated release is reviewed, and a real consuming repository proves install, update, rollback, and emergency disable.

The manual gates are tracked in:

Cratis/AI#148 — first approved public target and source contract;
Cratis/Workflows#72 — PR/release-capable distribution bot;
Cratis/Workflows#70 — npm package ownership and stage-only trusted publishing;
Cratis/Workflows#71 — first real consumer canary and rollback;
Cratis/AI#147 — vendor marketplace submissions after release approval.

What to do now

Use cratis init and Chronicle MCP for documented operating workflows today. Cratis maintainers can use the existing repository- local AI setup as described in Using AI as a Cratis maintainer. External application teams should wait for the first immutable release rather than copying internal repository trees.