skill-creator
Transforms documents containing theoretical knowledge or frameworks (PDFs, markdown, book notes, research papers, methodology guides) into actionable, reusable Claude Code skills using systematic reading methodology. Use when user mentions "create a skill from this document", "turn this into a skill", "extract a skill from this file", or when analyzing documents with methodologies, frameworks, or processes that could be made actionable.
What this skill does
# Skill Creator
## Table of Contents
- [Workflow](#workflow)
- [Step 1: Inspectional Reading](#step-1-inspectional-reading)
- [Step 2: Structural Analysis](#step-2-structural-analysis)
- [Step 3: Component Extraction](#step-3-component-extraction)
- [Step 4: Synthesis and Application](#step-4-synthesis-and-application)
- [Step 5: Skill Construction](#step-5-skill-construction)
- [Step 6: Validation and Refinement](#step-6-validation-and-refinement)
---
This skill applies Mortimer Adler's systematic reading methodology ("How to Read a Book") through a six-step progressive approach: inspectional reading, structural analysis, component extraction, synthesis, skill construction, and validation. The process is collaborative -- at decision points, options and trade-offs are presented for the user to choose.
**Methodology composition.** All five extractable steps are now backed by domain-neutral standalone skills, reusable beyond skill creation. The orchestration is owned by the [`skill-creator` agent](../../agents/skill-creator.md); this skill-file remains as documentation of the methodology and as a way to apply the methodology without the agent's session-workspace overhead.
| Step | Standalone skill | `purpose_context` to pass | Local resource still useful for |
| ---- | ---------------- | ------------------------- | ------------------------------- |
| 1 | [`inspectional-reading`](../inspectional-reading/SKILL.md) | `skill_extraction_from_methodology` | session init mechanics (`$SESSION_DIR`, `global-context.md`) |
| 2 | [`structural-analysis`](../structural-analysis/SKILL.md) | `skill_extraction_from_methodology` | unity-formula examples specific to skill creation |
| 3 | [`component-extraction`](../component-extraction/SKILL.md) | `skill_extraction_from_methodology` | section-based reading patterns specific to long-form skill sources |
| 4 | [`synthesis-application`](../synthesis-application/SKILL.md) | `skill_construction` | completeness inventory specific to skills (terms / propositions / arguments / solutions / decision-criteria / triggers) |
| 5 | [`skill-construction`](../skill-construction/SKILL.md) | `skill_construction` | rubric template + complexity-level decision aid |
| 6 | [`evaluation-rubrics`](../evaluation-rubrics/SKILL.md) | (existing skill, no purpose_context needed) | n/a |
---
## Workflow
**COPY THIS CHECKLIST** and work through each step:
```
Skill Creation Workflow
- [ ] Step 0: Initialize session workspace
- [ ] Step 1: Inspectional Reading
- [ ] Step 2: Structural Analysis
- [ ] Step 3: Component Extraction
- [ ] Step 4: Synthesis and Application
- [ ] Step 5: Skill Construction
- [ ] Step 6: Validation and Refinement
```
**Step 0: Initialize Session Workspace**
Create working directory and global context file. See [resources/inspectional-reading.md#session-initialization](resources/inspectional-reading.md#session-initialization) for setup commands.
**Step 1: Inspectional Reading**
Skim document systematically, classify type, assess skill-worthiness. Writes to `step-1-output.md`. See [resources/inspectional-reading.md#why-systematic-skimming](resources/inspectional-reading.md#why-systematic-skimming) for skim approach, [resources/inspectional-reading.md#why-document-type-matters](resources/inspectional-reading.md#why-document-type-matters) for classification, [resources/inspectional-reading.md#why-skill-worthiness-check](resources/inspectional-reading.md#why-skill-worthiness-check) for assessment criteria.
**Step 2: Structural Analysis**
Reads `global-context.md` + `step-1-output.md`. Classify content, state unity, enumerate parts, define problems. Writes to `step-2-output.md`. See [resources/structural-analysis.md#why-classify-content](resources/structural-analysis.md#why-classify-content), [resources/structural-analysis.md#why-state-unity](resources/structural-analysis.md#why-state-unity), [resources/structural-analysis.md#why-enumerate-parts](resources/structural-analysis.md#why-enumerate-parts), [resources/structural-analysis.md#why-define-problems](resources/structural-analysis.md#why-define-problems).
**Step 3: Component Extraction**
Reads `global-context.md` + `step-2-output.md`. Choose reading strategy, extract terms/propositions/arguments/solutions section-by-section. Writes to `step-3-output.md`. See [resources/component-extraction.md#why-reading-strategy](resources/component-extraction.md#why-reading-strategy) for strategy selection, [resources/component-extraction.md#section-based-extraction](resources/component-extraction.md#section-based-extraction) for programmatic approach, [resources/component-extraction.md#why-extract-terms](resources/component-extraction.md#why-extract-terms) through [resources/component-extraction.md#why-extract-solutions](resources/component-extraction.md#why-extract-solutions) for what to extract.
**Step 4: Synthesis and Application**
Reads `global-context.md` + `step-3-output.md`. Evaluate completeness, identify applications, transform to actionable steps, define triggers. Writes to `step-4-output.md`. See [resources/synthesis-application.md#why-evaluate-completeness](resources/synthesis-application.md#why-evaluate-completeness), [resources/synthesis-application.md#why-identify-applications](resources/synthesis-application.md#why-identify-applications), [resources/synthesis-application.md#why-transform-to-actions](resources/synthesis-application.md#why-transform-to-actions), [resources/synthesis-application.md#why-define-triggers](resources/synthesis-application.md#why-define-triggers).
**Step 5: Skill Construction**
Reads `global-context.md` + `step-4-output.md`. Determine complexity, plan resources, create SKILL.md and resource files, create rubric. Writes to `step-5-output.md`. See [resources/skill-construction.md#why-complexity-level](resources/skill-construction.md#why-complexity-level), [resources/skill-construction.md#why-plan-resources](resources/skill-construction.md#why-plan-resources), [resources/skill-construction.md#why-skill-md-structure](resources/skill-construction.md#why-skill-md-structure), [resources/skill-construction.md#why-resource-structure](resources/skill-construction.md#why-resource-structure), [resources/skill-construction.md#why-evaluation-rubric](resources/skill-construction.md#why-evaluation-rubric).
**Step 6: Validation and Refinement**
Reads `global-context.md` + `step-5-output.md` + actual skill files. Score using rubric, present analysis, refine based on user decision. Writes to `step-6-output.md`. See [resources/evaluation-rubric.json](resources/evaluation-rubric.json) for criteria.
---
## Notes
- **File-Based Context:** Each step writes output files to avoid context overflow
- **Global Context:** All steps read `global-context.md` for continuity
- **Sequential Dependencies:** Each step reads previous step's output
- **User Collaboration:** Always present findings and get approval at decision points
- **Quality Standards:** Use evaluation rubric (threshold ≥ 3.5) before delivery
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.