Files
zooqueen 16571ed9f3 one name for skills, and it can check them
@hanzo/skill installed skills; @hanzo/skills parsed them. Two names differing
only in number are two addresses for one subject, and the parsing half had no
importer at all — its own header claimed app, desktop and the dev harness
consumed it, and none did.

The parser, schema, registry and loader move in beside the installer. The CLI
gains `validate <dir>`: read every SKILL.md with the parser the loaders use and
exit non-zero if any cannot be loaded, so a repository that ships skills can
hold itself to that.

Compiling the tests found four type errors that had never been checked — the
package they came from excluded test/ from tsc and ran them under a runner that
does not typecheck. Three passed an option `recordSource` does not take; one
dereferenced a nullable. 56 tests, one runner.
2026-08-21 11:06:46 -07:00

20 lines
522 B
YAML

interface:
display_name: "Skill Creator"
short_description: "Create or update a skill"
icon_small: "./assets/skill-creator-small.svg"
icon_large: "./assets/skill-creator.png"
brand_color: "#7C5CFF"
default_prompt: "Help me create a new skill"
dependencies:
tools:
- type: mcp
value: filesystem
description: Read and write skill files
transport: stdio
command: "npx @modelcontextprotocol/server-filesystem"
policy:
allow_implicit_invocation: true
products:
- dev
- app