/skill-maker

What it does

Describe the skill you want and /as:skill-maker builds it, in three steps:

1. Scaffold from the canonical template. A new skill directory with a SKILL.md in the shape every other skill in the catalog uses — name, trigger-rich description, scoped tools, focused body.
2. Apply the conventions. The repo’s PATTERNS.md — the checklist of how ALPA builds plugins, from naming to cross-skill contracts — is read at runtime, not paraphrased from memory, and applied to the draft.
3. Verify. Inside the catalog, the result runs against the repo lint (every referenced file must resolve, counts can’t drift). Outside it, the same checks run as a portable checklist.

There is no interview step. The skill derives the name, the description, the tool scope, and the body from your request — you review the result, the way you’d review any file it proposes.

Install

Claude Desktop:

1. Open Customize → Browse plugins
2. Click + → Add marketplace from GitHub
3. Enter AlpacaLabsLLC/skills-for-architects
4. Install Architecture Studio

Claude Code (terminal):

claude plugin marketplace add AlpacaLabsLLC/skills-for-architects
claude plugin install as@skills-for-architects

Usage

/as:skill-maker a skill that turns raw site photos into a numbered photo log

House rules vs. your rules

Skills contributed to the repo face the lint and CI — the conventions are enforced because the catalog has to stay coherent. Skills you build for your own firm owe it nothing: the template and the checklist are defaults, not law. Keep what serves your office, strike the rest.

Skills stay useful by staying small — one verb each, composable, honest about what they hand off. /as:skill-maker bakes those PATTERNS.md conventions in; the course’s module 5 teaches the same anatomy by hand first, and that’s the right order.