Skills
Skill package structure
The folder layout GenCMS expects, and the smaller subset the MVP accepts.
Availability note — these docs describe both working and planned product areas. Account authentication, administrator-managed AIHK/AICA tenant regions and keys, signed-in Composer runs and public Guard scans are connected. Skills, Memory, Agents, Workflows, Apps, billing, the public SDK/CLI and the unified API are previews unless a section explicitly says otherwise.
Roadmap and package-contract reference: this page describes the intended GenCMS runtime. The current deployment persists workspace records and drafts but does not execute marketplace Skills, index Memory for retrieval, publish packages, or run Agents, Workflows or Apps. See the deployed API reference for the routes available today.
A Skill is a directory. Nothing about it is hidden from the person installing it — that is what makes marketplace review possible.
seo-audit/ ├── skill.yaml manifest — identity, permissions, models, pricing ├── SKILL.md what it does, limits, sample input and output ├── prompts/ │ ├── system.md the instruction the model receives │ └── analysis.md task-specific prompt fragments ├── schemas/ │ ├── input.json JSON Schema for the typed input │ └── output.json JSON Schema for the typed output ├── examples/ │ ├── input.json │ └── output.json ├── tests/ │ └── cases.json inputs plus expected properties ├── assets/ │ └── icon.svg ├── LICENSE └── README.md
The minimum that will publish
- skill.yaml — identity, category, permissions, execution mode
- SKILL.md — the description shown on the Skill page
- prompts/system.md or a handler entry point
- schemas/input.json and schemas/output.json
- one example pair, so the Skill page can show a real sample
Compiled artefacts (.so, .dll, .exe, .wasm) are not accepted in a marketplace Skill package. Guard flags them and publication is blocked.