insight-skill-generator
Use PROACTIVELY when working with projects that have docs/lessons-learned/ directories to transform Claude Code explanatory insights into reusable, production-ready skills. Analyzes insight files, clusters related content, and generates interactive skills following Anthropic's standards.
What this skill does
# Insight-to-Skill Generator ## Overview This skill transforms insights from the `extract-explanatory-insights` hook into production-ready Claude Code skills. It discovers insight files, clusters related insights using smart similarity analysis, and guides you through interactive skill creation. **Key Capabilities**: - Automatic discovery and parsing of insight files from `docs/lessons-learned/` - **Deduplication** to remove duplicate entries from extraction hook bugs - **Quality filtering** to keep only actionable, skill-worthy insights - Smart clustering using keyword similarity, category matching, and temporal proximity - Interactive skill design with customizable patterns (phase-based, mode-based, validation) - Flexible installation (project-specific or global) ## When to Use This Skill **Trigger Phrases**: - "create skill from insights" - "generate skill from lessons learned" - "turn my insights into a skill" - "convert docs/lessons-learned to skill" **Use PROACTIVELY when**: - User mentions they have accumulated insights in a project - You notice `docs/lessons-learned/` directory with multiple insights - User asks how to reuse knowledge from previous sessions - User wants to create a skill but has raw insights as source material **NOT for**: - Creating skills from scratch (use skill-creator instead) - Creating sub-agents (use sub-agent-creator instead) - User has no insights or lessons-learned directory - User wants to create MCP servers (use mcp-server-creator instead) ## Response Style **Interactive and Educational**: Guide users through each decision point with clear explanations of trade-offs. Provide insights about why certain patterns work better for different insight types. ## Quick Decision Matrix | User Request | Action | Reference | |--------------|--------|-----------| | "create skill from insights" | Full workflow | Start at Phase 1 | | "show me insight clusters" | Clustering only | `workflow/phase-2-clustering.md` | | "design skill structure" | Design phase | `workflow/phase-3-design.md` | | "install generated skill" | Installation | `workflow/phase-5-installation.md` | ## Workflow Overview ### Phase 1: Insight Discovery and Parsing Locate, read, **deduplicate**, and **quality-filter** insights from lessons-learned directory. → **Details**: `workflow/phase-1-discovery.md` ### Phase 2: Smart Clustering Group related insights using similarity analysis to identify skill candidates. → **Details**: `workflow/phase-2-clustering.md` ### Phase 3: Interactive Skill Design Design skill structure with user customization (name, pattern, complexity). → **Details**: `workflow/phase-3-design.md` ### Phase 4: Skill Generation Create all skill files following the approved design. → **Details**: `workflow/phase-4-generation.md` ### Phase 5: Installation and Testing Install the skill and provide testing guidance. → **Details**: `workflow/phase-5-installation.md` ## Quality Thresholds **Minimum quality score: 4** (out of 9 possible) Score calculation: - Has actionable items (checklists, steps): +3 - Has code examples: +2 - Has numbered steps: +2 - Word count > 200: +1 - Has warnings/notes: +1 **Skip insights that are**: - Basic explanatory notes without actionable steps - Simple definitions or concept explanations - Single-paragraph observations **Keep insights that have**: - Actionable workflows (numbered steps, checklists) - Decision frameworks (trade-offs, when to use X vs Y) - Code patterns with explanation of WHY - Troubleshooting guides with solutions ## File Naming Convention Files MUST follow: `YYYY-MM-DD-descriptive-slug.md` - ✅ `2025-11-21-jwt-refresh-token-pattern.md` - ✅ `2025-11-20-vitest-mocking-best-practices.md` - ❌ `2025-11-21.md` (missing description) ## Important Reminders - **Deduplicate first**: Extraction hook may create 7-8 duplicates per file - always deduplicate - **Quality over quantity**: Not every insight should become a skill (minimum score: 4) - **Descriptive filenames**: Use `YYYY-MM-DD-topic-slug.md` format - **Avoid skill duplication**: Check existing skills before generating - **User confirmation**: Always get user approval before writing files to disk - **Pattern selection matters**: Wrong pattern makes skill confusing. When in doubt, use phase-based - **Test before sharing**: Always test trigger phrases work as expected ## Limitations - Requires `docs/lessons-learned/` directory with insight files - Insight quality determines output quality (garbage in, garbage out) - Cannot modify existing skills (generates new ones only) - Clustering algorithm may need threshold tuning for different domains ## Reference Materials | Resource | Purpose | |----------|---------| | `workflow/*.md` | Detailed phase instructions | | `reference/troubleshooting.md` | Common issues and fixes | | `data/clustering-config.yaml` | Similarity rules and thresholds | | `data/skill-templates-map.yaml` | Insight-to-skill pattern mappings | | `data/quality-checklist.md` | Validation criteria | | `templates/*.md.j2` | Generation templates | | `examples/` | Sample outputs | ## Success Criteria - [ ] Insights discovered and parsed from lessons-learned - [ ] Clusters formed with user approval - [ ] Skill design approved (name, pattern, structure) - [ ] All files generated and validated - [ ] Skill installed in chosen location - [ ] Trigger phrases tested and working --- **Version**: 0.2.0 **Author**: Connor **Integration**: extract-explanatory-insights hook
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.