skill-create is a skill from the Summer skill library: a guide your AI agent reads when the task matches, so it builds the good version on the first try. Bootstrap a new Summer library skill (library/skills/<slug>/ with resource.yaml and SKILL.md), frontmatter, and stub sections.
When your agent uses it
- A contributor wants to add a new skill to the Summer library
- Scaffolding a new library skill folder with canonical structure, frontmatter, and stub sections
Install
summer setup installs every skill for your agent. To add only this one:
claude-code for your agent, such as codex or cursor. See Skills for every option.
The skill
Works inside a checkout of the Summer repository,summerengine/summer (the one with library/ and registry/). Outside it, capture the lesson with gameskill in the game project instead.
Steps
1. Get the basics
Ask the user:- Slug (kebab-case, 64 chars or fewer, flat: no category folders). Example:
state-machine-patterns. - Domain facets: pick from the vocabulary in
registry/schemas/domains.json(read it, do not guess). Example:scripting,gameplay. - One-sentence summary and a “Use when …” description for the frontmatter.
- Template-id (optional). Look it up in
library/templates/<id>/resource.yaml.
2. Create the folder
May I createlibrary/skills/<slug>/ with this structure?
3. Write resource.yaml (template)
status: preview until the skill has been exercised against a live engine; flip to stable in the same change as the evidence.
4. Write SKILL.md (template)
library/references/. Cross-reference other skills by bare slug, never by path or @ link.
5. Generate and validate
Nothing is registered by hand. Run:generate:registry rewrites registry/generated/ and every plugin manifest from library/; validate:library checks the schema, facets, related links and capability lint; the test suite checks manifest parity. Commit the generated files with the skill.
6. Run /skill-test
Confirm the structural checks pass and, if the skill drives tools, that the routing eval still finds it (npm run eval:routing).
Collaborative protocol
This skill writes files. Always ask before each write step.See also
collaborative-protocolinlibrary/references/skill-test,skill-improve,gameskill
Related skills
skill-test: Lint a Summer skill before commit, audit the whole library, or check a behavioral spec assertion — static structural rules plus behavioral specs.
Source:
library/skills/skill-create/SKILL.md, rendered from summer-engine@4.3.0 on npm.