skill-create

Scaffolds new Summer library skills with resource.yaml, SKILL.md frontmatter, and stub sections.

66|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/SummerEngine/summer --skill skill-create-summerengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-create
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/skill-create
Command: npx skills add https://github.com/SummerEngine/summer --skill skill-create-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors adding a new skill to the Summer library must follow a strict folder structure, frontmatter format, and registry schema; doing this by hand is error-prone and easy to get wrong. ## Core Features & Use Cases - Guided scaffolding: Walks through slug selection, domain facets from registry/schemas/domains.json, and summary wording before creating library/skills/<slug>/. - Canonical templates: Provides ready-to-fill resource.yaml and SKILL.md templates with routing metadata, frontmatter, and stub sections. - Validation workflow: Runs npm run generate:registry, npm run validate:library, and npm test so the new skill passes schema, facet, and capability-lint checks. - Use Case: A contributor wants to document a state-machine pattern as a reusable skill; this Skill creates the folder, writes both files, and regenerates the registry in one guided flow. ## Quick Start Ask the agent to bootstrap a new Summer library skill and provide a slug, domain facets, and a one-sentence summary when prompted.

Frequently Asked Questions about skill-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new skill for the Summer library?

Run the skill-create workflow inside a checkout of the summer-engine agent repository. It prompts for a kebab-case slug, domain facets, and a summary, then creates library/skills/<slug>/ with resource.yaml and SKILL.md templates.

What files does a Summer library skill require?

A skill needs a resource.yaml with routing metadata (id, kind, facets, use_when) and a SKILL.md with YAML frontmatter containing name and description. An optional references/ directory can hold supporting detail.

How do I validate a new Summer skill after creating it?

Run npm run generate:registry, npm run validate:library, and npm test from the repository root. These regenerate the registry, check schema and capability lint, and verify manifest parity; commit the generated files with the skill.

Can I use skill-create outside the summer-engine repository?

No, it only works inside a checkout containing the library/ and registry/ directories. In a game project, capture lessons with the gameskill workflow instead.

When should a skill status change from preview to stable?

Keep status as preview until the skill has been exercised against a live engine. Flip it to stable in the same change that adds the evidence of that live-engine validation.