benai-skill-creator-skilllisted

Turn a task you just finished into a small, reliable, single-purpose skill by reverse-engineering the process from the conversation you already had. Also improves or audits an existing skill. Use this AFTER you have done a piece of knowledge work in a chat (research, a draft, an analysis, a prep doc) and want to lock the process in as a skill. Triggers include "build a skill from this", "turn this into a skill", "make a skill out of what we just did", "skill-ify this", "build a skill", "improve this skill", "audit my skill", "why does my skill suck", "make my skill smaller", or when the user finishes a repeatable task and wants to reuse it. Built for knowledge workers, not just engineers. For skills you have NOT done yet (only an idea), hand off to process-interviewer instead.
naveedharri/benai-skills · ★ 46 · AI & Automation · score 71

Install: claude install-skill naveedharri/benai-skills

# BenAI Skill Creator Most skills are built wrong: someone describes a process from memory before running it, and gets the cleaned-up version that drops the judgment and the exceptions. This does the opposite. You do the task once in a chat, then this turns what actually happened into a small, reliable skill. Two rules carry the whole skill: keep it **modular** (one goal, one job) and remember **skills are never finished** (ship a small working one, then improve it by using it). The reasoning is in `references/scope-and-mindset.md`. ## Route first Read the situation and pick a branch. Say which branch you picked and why, then proceed. | Situation | Branch | Do this | |-----------|--------|---------| | The user just finished a real task in this chat | **Build** | Steps 1 to 5 below | | The user only has an idea, nothing has been done yet | **Plan** | Hand off to the `process-interviewer` skill (interview first, then it builds). Stop here. | | The user points at an existing skill to fix or shrink | **Improve** | Skip step 2 (Extract). Run steps 1, 3, 4, 5 against the existing skill. | If unsure, ask one question: "Did we already do this task in this chat, or is it still just an idea?" ## The build flow Track progress out loud: ``` Task Progress: - [ ] 1. Scope: one goal, right size, split or not - [ ] 2. Extract: pull the real process out of the chat - [ ] 3. Structure: write a small SKILL.md + reference files - [ ] 4. Prune: cut everything that does not change behavio