add-capsule

kind	skill
name	add-capsule
description	Scaffold a full release capsule — folder, spec-driven README, notebook skeleton, deps, CHANGELOG row.
inputs	[{"name":"publisher","type":"string","description":"Publisher slug (kebab-case) matching a folder under models/.","required":true},{"name":"model","type":"string","description":"Model slug (kebab-case).","required":true},{"name":"release_date","type":"date","description":"Public release date (YYYY-MM-DD); also the capsule folder name.","required":true},{"name":"capabilities","type":"array","description":"Capability tags from the taxonomy in the repo README.","required":true},{"name":"model_card","type":"url","description":"Official model card URL — prefer learn.microsoft.com when available.","required":true},{"name":"announcement","type":"url","description":"Official release-announcement URL.","required":false},{"name":"pricing","type":"string","description":"Free-form pricing summary or structured object.","required":false},{"name":"dependencies","type":"array","description":"Extra Python packages appended to requirements-dev.txt (Capsule dependencies section).","required":false},{"name":"domains","type":"array","description":"Domains for the interesting use cases (e.g. travel, healthcare).","required":false},{"name":"summary","type":"string","description":"One sentence (20-160 chars) naming the model, what you can do with it, and Microsoft Foundry. Stored in frontmatter and reused as the meta description in catalog.json, llms.txt, CAPSULE-TOC.md, and the repo README - so it must read standalone, out of context.","required":true},{"name":"references","type":"array","description":"Author-supplied best-practice references (model card, docs, sample repos, blog posts). The agent MUST prompt the creator for these before scaffolding. Written as markdown bullets in the `## References` section of the capsule README and the notebook's final References cell - NOT as frontmatter, so crawlers and agents follow them as real links.","required":true},{"name":"concepts","type":"array","description":"Ordered list of teaching concepts for this release. Each concept becomes its own notebook (1–3 concepts per notebook max). Provide {slug, title, concepts_covered[]} so the skill can name and scaffold each notebook file.","required":true}]
produces	["models/<publisher>/<release>/README.md","models/<publisher>/<release>/<release>.ipynb","CHANGELOG.md","CAPSULE-TOC.md","catalog.json","llms.txt","models/<publisher>/README.md","requirements-dev.txt"]
validates_against	[".github/specs/schemas/capsule.schema.json"]
depends_on	["add-publisher","add-model","refresh-recent-activity"]

add-capsule

Produces a complete release capsule:

1. Creates models/<publisher>/<model>/<release_date>/ with a README whose frontmatter matches capsule.schema.json — including a Before You Begin section with pricing, release / expiry dates, model-card link, and a link to models/quickstart/.
2. Scaffolds one or more notebooks under notebooks/ following the pedagogy rules in plan.md §15:
   • Each notebook covers 1–3 concepts. If the release needs more, the skill scaffolds additional notebooks (01-…, 02-…, 03-…) rather than growing a single long notebook. The author declares the split up front via the concepts prompt.
   • Every notebook is independently runnable — it repeats the Before You Begin + env-precheck cells at the top.
   • Numbered, alternating markdown ↔ code sections so the Outline reads like a tutorial table of contents. Section titles are verbs (e.g. "Send a chat request", "Attach an image").
   • ## 1. Before You Begin (markdown) — pricing, dates, model card, link to models/quickstart/.
   • ## 2. Verify your environment (code) — env precheck against the vars listed in models/quickstart/README.md frontmatter (required_env).
   • Content sections 3..N-2 alternating markdown/code.
   • ## N-1. Your Turn to Explore (markdown + empty code cell) — required. Suggests 2–3 concrete directions without solutions.
   • ## N. Summary (markdown) — required. What was covered, when to reach for this model, links to primers and glossary terms.
   • ## N+1. References (markdown) — required. A bulleted list of the author-supplied references, written directly as markdown (- [title](url) — note). References are body content, not frontmatter. If the author supplied none, the scaffold prints a TODO reminder rather than silently omitting the section.
   • Voice: action-focused, no hype/marketing language.
3. Appends any capsule-specific under the section of .