All authors
Claude Skills by rfxlamia
github.com/rfxlamia22 skills2 installs94 views
- Claude SkillkitProfessional skill creation with research-driven workflow and automated validation. USE WHEN: Creating new skills, validating existing skills, deciding between Skills vs Subagents, migrating documents to skills, or running individual validation tools. PRIMARY TRIGGERS: "create skill" = Full creation (12 steps with research + execution planning) "validate skill" = Validation workflow (steps 3-8) "Skills vs Subagents" = Decision workflow (step 0) "convert doc to skill" = Migration workflow "e...Votes: 0GitHub stars: 101
- References**Use when:** User has existing skill, wants to validate quality/compliance **Prerequisites:** - Skill folder exists - SKILL.md file present **Entry Point:** User says "validate my skill" or "check skill quality" Execute Steps 3-8 from Full Creation Workflow: 1. **Structure Validation** (Step 3) - Run `scripts/validate_skill.py skill-name/ --format json` - Check critical issues - Fix if needed 2. **Security Audit** (Step 4) - Run `scripts/security_scanner.py skill-name/ --format json` - Addre...Votes: 0GitHub stars: 101
- Skillkit HelpPre-build orientation for skill creators. Answers "what are skills?", "should I make one?", and "is my skill good enough?" before you start building. Use for: understand skills, decide skills vs subagents, validate an existing skill. When ready to actually build, invoke /skillkit directly instead.Votes: 0GitHub stars: 101
- TemplateOne sentence: what this skill does and when to invoke it. Use for: [list 2-3 trigger phrases users would naturally type].Votes: 0GitHub stars: 101
- SkillkitToolkit for creating and validating skills and subagents. Use when: creating a new skill (fast or full mode), validating an existing skill, deciding Skills vs Subagents, migrating docs to skills, estimating token cost, or running a security scan. Triggers: "create skill", "build skill", "validate skill", "new subagent", "skills vs subagents", "estimate tokens", "security scan".Votes: 0GitHub stars: 101
- Skillkit HelpPre-build orientation for skill creators. Answers "what are skills?", "should I make one?", and "is my skill good enough?" before you start building. Use for: understand skills, decide skills vs subagents, validate an existing skill. When ready to actually build, invoke /skillkit directly instead.Votes: 0GitHub stars: 101
- TemplateOne sentence: what this skill does and when to invoke it. Use for: [list 2-3 trigger phrases users would naturally type].Votes: 0GitHub stars: 101
- SkillkitToolkit for creating and validating skills and subagents. Use when: creating a new skill (fast or full mode), validating an existing skill, deciding Skills vs Subagents, migrating docs to skills, estimating token cost, or running a security scan. Triggers: "create skill", "build skill", "validate skill", "new subagent", "skills vs subagents", "estimate tokens", "security scan".Votes: 0GitHub stars: 101
- References**Use when:** User has existing document, wants to convert to skill **Entry Point:** User says "convert this doc to skill" or "migrate document" **Prerequisites:** - Document file available (markdown, text, PDF, docx) - User confirms content ownership 1. **Decision Check** (Step 0) - Run decision_helper.py to confirm Skills appropriate - Proceed only if recommendation = "Skills" 2. **Migration Analysis** (Enhanced Step 2) ```bash python scripts/migration_helper.py user-doc.md --format json ``...Votes: 0GitHub stars: 101
- Brand DesignBrand-aware design system generator that acts as Head of Brand. Translates abstract brand language into a mathematically-validated, implementation-ready design system, then writes creative-brief.md as the source of truth for all UI/UX in a project. Standalone skill (like bug-hunting and hotfix — no full pipeline required). Trigger on "/brand-design", "design system", "creative brief", "define the brand", "brand identity", "set up UI tokens", or when starting UI work without an existing design...Votes: 0GitHub stars: 5
- Bug HuntingUse when fixing bugs, debugging failures, or proactively reviewing code for hidden bugs. Reactive mode: fix known bugs. Proactive mode: hunt for bugs in code. Enforces confirmed root cause before any fix.Votes: 0GitHub stars: 5
- HotfixFast iteration workflow with mandatory subagent plan review. Use when implementing small-to-medium changes quickly. Trigger on "quick fix", "small change", "just update X", or any change where full superpowers ceremony is overkill but accuracy still matters. Enforces brief-plan + subagent-review gates before any implementation.Votes: 0GitHub stars: 5
- Pocket ClosingTerminal pocket stage. User invokes after pocket-development's phase-level pass writes verdicts. Reconciles reviews against log.json, gates on REVIEW_FAIL/REVIEW_BLOCKED, advances REVIEW→DONE, runs `log close`, and emits a closeout summary. Trigger on "pocket-closing", "close the plan", "close out", "finalize plan", or when a plan is fully reviewed and all verdicts pass.Votes: 0GitHub stars: 5
- Pocket DevelopmentUse when executing implementation plans of one or more tasks. Trigger on execute plan, delegate tasks, dispatch subagents. Combines delegate handoff discipline with prompt-engineering attention mechanics.Votes: 0GitHub stars: 5
- Pocket GrindingBDD-driven feature/fix discovery before any implementation. Use when planning a feature, designing a fix, or exploring options before building. Trigger on "pocket-grinding", "brainstorm", "think through", "plan this", "before we build". Invokes pocket-planning at handoff.Votes: 0GitHub stars: 5
- Pocket HelpOnboarding and routing guide for the Pocket skill ecosystem. Use when someone asks what Pocket is, which Pocket skill to use, how the end-to-end flow works, or when Pocket is better than lighter Superpowers-style flows. Trigger on "what is pocket", "how do I use pocket", "which pocket skill", "explain pocket", "pocket-help", or any onboarding/routing question. This is a compact entry point — it summarizes every skill so agents and users do NOT have to load each SKILL.md to orient.Votes: 0GitHub stars: 5
- Pocket PitchingPre-grinding problem exploration. Use BEFORE pocket-grinding when the problem is unformed or needs exploration. Guides diverge→converge with structured brainstorming methods and LLM-to-LLM curation (advisor tool), then produces a pitch exploration doc. Trigger on "pocket-pitching", "pitch this", "explore this idea", "I have a rough idea", or when no clear problem definition exists yet. Do NOT use for "brainstorm" — that triggers pocket-grinding.Votes: 0GitHub stars: 5
- Pocket PlanningConverts a pocket-grinding spec into a TDD-structured execution plan of full Pocket Packets. Use when pocket-grinding handoff arrives (spec path + acceptance criteria). Trigger on "create plan", "build plan", "pocket-planning", or when pocket-grinding skill invokes this. Outputs tasks ready to dispatch via pocket-development skill.Votes: 0GitHub stars: 5
- Pocket StructuringBridges pocket-planning and pocket-development for all execution plans. Use when pocket-planning hands off any execution plan. Routes ≤6-task plans as a passthrough to pocket-development; splits ≥7-task plans into phase files. Trigger on "structure plan", "split plan", or when pocket-planning invokes this.Votes: 0GitHub stars: 5
- Structured ResearchStandalone skill for validating an explicit assumption with structured research. Use when a user holds a belief that is still an assumption — a technical claim, a library's behavior, a "this is probably how X works" — and wants it investigated methodically before it leaks into planning or code. Recommends a research methodology (non-binding) and returns an evidence-backed, graded verdict (Confirmed / Refuted / Inconclusive). Trigger on "structured-research", "validate this assumption", "is it...Votes: 0GitHub stars: 5
- Create PrOpens a GitHub PR for the current branch linked to the Pocket issue (Pocket Enterprise). User-triggered recorder — commits traveling state, formats a structured PR body, discovers or creates the PR, and records it in .pocket-meta.json. Trigger on "create-pr", "open a PR", "create pull request", or when pocket-development offers it after a phase completes in enterprise mode.Votes: 0GitHub stars: 5
- Pocket InitOnboards an existing (brownfield) project onto Pocket. Scans the codebase and writes a project memory file (CLAUDE.md or AGENTS.md), optionally enables Pocket Enterprise (mode init) and scaffolds GitHub issue/PR templates. Trigger on "pocket-init", "set up pocket", "onboard this project", "generate CLAUDE.md", "enable enterprise mode".Votes: 0GitHub stars: 5