← ClaudeAtlas

skill-builderlisted

Scaffold a new ralvaskills skill per SPECS.md — SKILL.md skeleton, optional STACK/RECIPES, folder placement, SPECS updates. Interview-first; never guesses. Use when authoring a new skill or invoking /skill-builder.
ralvarezdev/ralvaskills · ★ 2 · Web & Frontend · score 75
Install: claude install-skill ralvarezdev/ralvaskills
# Skill Builder Meta-skill that scaffolds new skills under `skills/<category>/<skill-name>/` following [SPECS.md](../../../docs/SPECS.md). Generates structure; hands off content authoring. Templates and the full validation checklist live in [RECIPES.md](RECIPES.md). ## 1. When to invoke - User says "let's create a new skill", "scaffold a skill", "I want to add a `<topic>-architect`", or invokes `/skill-builder`. - User wants to verify whether an existing folder structure matches the conventions. - User wants to move / rename a skill and needs the SPECS updates handled correctly. ## 2. Source of truth **SPECS.md is canonical.** This skill cites and applies the rules; it does not redefine them. Sections it enforces: - **Skill Authoring Guide** — SKILL.md format, STACK.md format, naming convention, description quality, supporting files (`UPPER_SNAKE_CASE.md`). - **Repository & Folder Structure** — discovery rule (folder with `SKILL.md` is terminal; nested SKILL.md forbidden), category placement, personal-skills path-segment rule. - **Which Skills Need a `STACK.md`** — heuristic table by parent folder; per-skill exceptions allowed. - **Bundle & Skill Catalog** — bundle membership decisions. If a question isn't answered here, **read SPECS.md before guessing.** ## 3. Interview-first protocol **Never scaffold without an interview.** Ask in order; wait for each answer: 1. **Topic + suffix** — what does the skill enforce? Confirm the resulting `<name>` matches the SPECS nami