Skills

Manifest reference

Every field in skill.yaml, what it controls and what validation rejects.

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.

skill.yaml
id: gencms/seo-audit
name: SEO Audit
version: 3.0.1
publisher: GenCMS
category: marketing

visibility: public          # public | unlisted | organization | private
pricing: paid               # free | paid
price:
  type: subscription        # one_time | subscription | credit_premium
  tier: pro

models:
  mode: auto                # fixed | recommended | auto | user_choice | compare
  recommended:
    - openai
    - anthropic

permissions:
  - web.fetch
  - memory.read

input_schema: schemas/input.json
output_schema: schemas/output.json

entry: prompts/system.md
tests: tests/cases.json
FieldRequiredNotes
idyespublisher/slug — immutable once published
versionyesSemantic version. A published version is never overwritten (§53).
categoryyesOne of the ten launch categories. New categories are not created on demand.
visibilityyesOrganization and private Skills never appear in the public marketplace.
pricing / priceyesFree Skills still consume the installer's credits when they run.
models.modeyesSee Execution modes.
permissionsyesOnly what the code exercises. Guard reports the mismatch if it is short.
input_schema / output_schemayesJSON Schema. A Workflow relies on these shapes.
entryyesPrompt file or handler module.
testsrecommendedRun on every publish; failures block release.

What validation rejects

  • A permission that is not in the supported set, or `shell` on a marketplace Skill.
  • An output schema that the example output does not satisfy.
  • A version that is not greater than the current published version.
  • A wildcard permission or tool declaration.
  • A missing LICENSE when visibility is public.