# auto-skill-generator

> Use when repeated prompts, missing capability, or a blocked workflow indicate a new reusable skill is needed.

- Author: AttendantLion8
- Repository: AttendantLion8/superpowers
- Version: 20251222023517
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-07
- Source: https://github.com/AttendantLion8/superpowers
- Web: https://mule.run/skillshub/@@AttendantLion8/superpowers~auto-skill-generator:20251222023517

---

---
name: auto-skill-generator
description: Use when repeated prompts, missing capability, or a blocked workflow indicate a new reusable skill is needed.
---

# Auto Skill Generator

## Overview
Create a minimal new skill only when a capability gap blocks progress.

## When to use
- Repeated prompts or steps keep reappearing across tasks.
- A missing capability blocks task completion.
- You need a reusable, scoped workflow instead of ad-hoc guidance.

## When not to use
- A one-off task does not justify a skill.
- An existing skill already covers the workflow.
- The request is just a doc update or simple clarification.

## Inputs
- Capability gap description
- Scope boundaries and exclusions
- Example prompts and expected output (if available)

## Workflow
1. Check existing skills for overlap or partial coverage.
2. Propose a short hyphenated skill name and trigger conditions.
3. Draft a minimal SKILL.md outline (overview, when to use, workflow, approval gate).
4. Ask for approval on the draft and file location.
5. Create the skill folder and SKILL.md only after approval.
6. Provide a short validation prompt to test the new skill.

## Output format
- Short proposal plus a short bullet list of scope and triggers.

## Output template
```text
Proposal: <one paragraph>
Triggers:
- <trigger 1>
- <trigger 2>
Scope:
- In scope: <items>
- Out of scope: <items>
```

## Approval gate
- Never create or modify files before explicit approval.

## Quick reference
| Step | Action |
| --- | --- |
| 1 | Check existing skills |
| 2 | Propose name and triggers |
| 3 | Draft minimal outline |
| 4 | Ask for approval |
| 5 | Create files after approval |
| 6 | Provide validation prompt |

## Common mistakes
- Creating files before approval.
- Over-scoping the skill beyond the gap.
- Missing trigger phrases in the description.

## Rationalizations to avoid
| Excuse | Reality |
| --- | --- |
| "I will just create the files now." | Approval is required first. |
| "We can make it cover everything." | Over-scoping breaks reuse. |

## Red flags
- "I'll just write the file now."
- "No need for example prompts."
- "We can make this skill cover everything."

## Example
User: "We keep repeating our release checklist. Make a skill."
You: Propose a skill name, list triggers, draft a minimal outline, ask for approval.