2.2 KiB

Raw Permalink Blame History

Stable Skills Manifest v1

This page documents the skills_index.json manifest contract used by stable integrations.

Manifest contract (v1)

Canonical file: skills_index.json at repository root.
Mirror file: data/skills_index.json must be an exact compatibility mirror of skills_index.json.
Format: JSON array, one object per skill.
Schema: schemas/skills-index.v1.schema.json

Required fields

Each manifest entry includes:

id – skill identifier (same as @skill-id).
path – relative skill folder, e.g. skills/brainstorming.
category – grouping used by UI/search surfaces.
name – display name.
description – short purpose/trigger summary.
risk – one of repo risk labels.
source – source of authority/trust metadata.
date_added – ISO date string or null.

Additional fields are allowed, and plugin metadata is optional.

Recommended host behavior

Stable integrations must not load every skill instruction file up front.

Read the manifest (skills_index.json).
Resolve only the requested @skill-id values from the conversation.
For each resolved skill, read that one SKILL.md lazily.
Enforce a per-turn maximum so user prompts stay below context limits.
Validate each resolved path stays under your configured SKILLS_ROOT.

This is the core prevention for context truncation and trajectory conversion errors in larger multi-skill hosts.

Why the `data/` mirror exists

data/skills_index.json remains for downstream compatibility where clients still read from the data/ subtree. The stable contract is that both files contain the same payload.

Quick structure example

{
  "id": "brainstorming",
  "path": "skills/brainstorming",
  "category": "planning",
  "name": "brainstorming",
  "description": "Use before any creative or constructive work.",
  "risk": "safe",
  "source": "official",
  "date_added": "2026-02-27"
}

2.2 KiB Raw Permalink Blame History Unescape Escape