Back to list
therealityreport

skillcreator

by therealityreport

0🍴 0📅 Jan 23, 2026

SKILL.md


name: skillcreator description: "Ultimate meta-skill for creating production-ready Claude Code skills. Uses deep iterative analysis with 11 thinking models, regression questioning until exhausted, evolution and timelessness as core lens, and multi-agent synthesis panel for unanimous approval. Includes automation analysis for agentic scripts. Fully autonomous execution at maximum depth produces categorically the best possible skills." license: MIT metadata: version: 3.2.0 model: claude-opus-4-5-20251101 subagent_model: claude-opus-4-5-20251101 domains: [meta-skill, automation, skill-creation, orchestration, agentic] type: orchestrator inputs: [user-goal, domain-hints] outputs: [SKILL.md, references/, scripts/, SKILL_SPEC.md]

SkillCreator 3.2 - Ultimate Meta-Skill

Create categorically the best possible Claude Code skills.


Quick Start

Just tell me what skill you need:

SkillCreator: create a skill for automated code review

That's it. The skill will be created autonomously with full analysis, verification, and quality gates.


Triggers

  • SkillCreator: {goal} - Full autonomous skill creation
  • create skill - Natural language activation
  • design skill for {purpose} - Purpose-first creation
  • ultimate skill - Emphasize maximum quality
  • skillcreator --plan-only - Generate specification without execution
InputOutputQuality Gate
Your goalProduction-ready skillUnanimous 3/3 panel approval

Process Overview

Your Request
    │
    ▼
┌─────────────────────────────────────────────────────┐
│ Phase 1: DEEP ANALYSIS                              │
│ • Expand requirements (explicit, implicit, unknown) │
│ • Apply 11 thinking models + Automation Lens        │
│ • Question until no new insights (3 empty rounds)   │
│ • Identify automation/script opportunities          │
├─────────────────────────────────────────────────────┤
│ Phase 2: SPECIFICATION                              │
│ • Generate XML spec with all decisions + WHY        │
│ • Include scripts section (if applicable)           │
│ • Validate timelessness score ≥ 7                   │
├─────────────────────────────────────────────────────┤
│ Phase 3: GENERATION                                 │
│ • Write SKILL.md with fresh context                 │
│ • Generate references/, assets/, and scripts/       │
├─────────────────────────────────────────────────────┤
│ Phase 4: SYNTHESIS PANEL                            │
│ • 3-4 Opus agents review independently              │
│ • Script Agent added when scripts present           │
│ • All agents must approve (unanimous)               │
│ • If rejected → loop back with feedback             │
└─────────────────────────────────────────────────────┘
    │
    ▼
Production-Ready Agentic Skill

Key principles:

  • Evolution/timelessness is the core lens (score ≥ 7 required)
  • Every decision includes WHY
  • Zero tolerance for errors
  • Autonomous execution at maximum depth
  • Scripts enable self-verification and agentic operation

Commands

CommandAction
SkillCreator: {goal}Full autonomous execution
SkillCreator --plan-only {goal}Generate specification only
SkillCreator --quick {goal}Reduced depth (not recommended)

Validation & Packaging

Before distribution, validate your skill:

# Quick validation (required for packaging)
python scripts/quick_validate.py ~/.claude/skills/my-skill/

# Full structural validation
python scripts/validate-skill.py ~/.claude/skills/my-skill/

# Package for distribution
python scripts/package_skill.py ~/.claude/skills/my-skill/ ./dist

Frontmatter Requirements

Skills must use only these allowed frontmatter properties:

PropertyRequiredDescription
nameYesHyphen-case, max 64 chars
descriptionYesMax 1024 chars, no angle brackets
licenseNoMIT, Apache-2.0, etc.
allowed-toolsNoRestrict tool access
metadataNoCustom fields (version, model, etc.)
---
name: my-skill
description: What this skill does
license: MIT
metadata:
  version: 1.0.0
  model: claude-opus-4-5-20251101
---

Skill Output Structure

~/.claude/skills/{skill-name}/
├── SKILL.md                    # Main entry point (required)
├── references/                 # Deep documentation (optional)
│   ├── patterns.md
│   └── examples.md
├── assets/                     # Templates (optional)
│   └── templates/
└── scripts/                    # Automation scripts (optional)
    ├── validate.py             # Validation/verification
    ├── generate.py             # Artifact generation
    └── state.py                # State management

Scripts Directory

Scripts enable skills to be agentic - capable of autonomous operation with self-verification.

CategoryPurposeWhen to Include
ValidationVerify outputs meet standardsSkill produces artifacts
GenerationCreate artifacts from templatesRepeatable artifact creation
State ManagementTrack progress across sessionsLong-running operations
TransformationConvert/process dataData processing tasks
CalculationCompute metrics/scoresScoring or analysis

Script Requirements:

  • Python 3.x with standard library only (graceful fallbacks for extras)
  • Result dataclass pattern for structured returns
  • Exit codes: 0=success, 1=failure, 10=validation failure, 11=verification failure
  • Self-verification where applicable
  • Documented in SKILL.md with usage examples

See: references/script-integration-framework.md


Anti-Patterns

AvoidWhyInstead
Duplicate skillsBloats registryCheck existing first
Single triggerHard to discover3-5 varied phrases
No verificationCan't confirm successMeasurable outcomes
Over-engineeringComplexity without valueStart simple
Missing WHYCan't evolveDocument rationale
Invalid frontmatterCan't packageUse allowed properties only

Verification Checklist

After creation:

  • Frontmatter valid (only allowed properties)
  • Name is hyphen-case, ≤64 chars
  • Description ≤1024 chars, no < or >
  • 3-5 trigger phrases defined
  • Timelessness score ≥ 7
  • python scripts/quick_validate.py passes

1A: Input Expansion

Transform user's goal into comprehensive requirements:

USER INPUT: "Create a skill for X"
                │
                ▼
┌─────────────────────────────────────────────────────────┐
│ EXPLICIT REQUIREMENTS                                    │
│ • What the user literally asked for                      │
│ • Direct functionality stated                            │
├─────────────────────────────────────────────────────────┤
│ IMPLICIT REQUIREMENTS                                    │
│ • What they probably expect but didn't say               │
│ • Standard quality expectations                          │
│ • Integration with existing patterns                     │
├─────────────────────────────────────────────────────────┤
│ UNKNOWN UNKNOWNS                                         │
│ • What they don't know they need                         │
│ • Expert-level considerations they'd miss                │
│ • Future needs they haven't anticipated                  │
├─────────────────────────────────────────────────────────┤
│ DOMAIN CONTEXT                                           │
│ • Related skills that exist                              │
│ • Patterns from similar skills                           │
│ • Lessons from skill failures                            │
└─────────────────────────────────────────────────────────┘

Check for overlap with existing skills:

ls ~/.claude/skills/
# Grep for similar triggers in existing SKILL.md files
Match ScoreAction
>7/10Use existing skill instead
5-7/10Clarify distinction before proceeding
<5/10Proceed with new skill

1B: Multi-Lens Analysis

Apply all 11 thinking models systematically:

LensCore QuestionApplication
First PrinciplesWhat's fundamentally needed?Strip convention, find core
InversionWhat guarantees failure?Build anti-patterns
Second-OrderWhat happens after the obvious?Map downstream effects
Pre-MortemWhy did this fail?Proactive risk mitigation
Systems ThinkingHow do parts interact?Integration mapping
Devil's AdvocateStrongest counter-argument?Challenge every decision
ConstraintsWhat's truly fixed?Separate real from assumed
ParetoWhich 20% delivers 80%?Focus on high-value features
Root CauseWhy is this needed? (5 Whys)Address cause not symptom
ComparativeHow do options compare?Weighted decision matrix
Opportunity CostWhat are we giving up?Explicit trade-offs

Minimum requirement: All 11 lenses scanned, at least 5 applied in depth.

See: references/multi-lens-framework.md

1C: Regression Questioning

Iterative self-questioning until no new insights emerge:

ROUND N:
│
├── "What am I missing?"
├── "What would an expert in {domain} add?"
├── "What would make this fail?"
├── "What will this look like in 2 years?"
├── "What's the weakest part of this design?"
└── "Which thinking model haven't I applied?"
    │
    └── New insights > 0?
        │
        ├── YES → Incorporate and loop
        └── NO → Check termination criteria

Termination Criteria:

  • Three consecutive rounds produce no new insights
  • All 11 thinking models have been applied
  • At least 3 simulated expert perspectives considered
  • Evolution/timelessness explicitly evaluated
  • Automation opportunities identified

See: references/regression-questions.md

1D: Automation Analysis

Identify opportunities for scripts that enable agentic operation:

FOR EACH operation in the skill:
│
├── Is this operation repeatable?
│   └── YES → Consider generation script
│
├── Does this produce verifiable output?
│   └── YES → Consider validation script
│
├── Does this need state across sessions?
│   └── YES → Consider state management script
│
├── Does this involve external tools?
│   └── YES → Consider integration script
│
└── Can Claude verify success autonomously?
    └── NO → Add self-verification script

Automation Lens Questions:

QuestionScript Category if YES
What operations will be repeated identically?Generation
What outputs require validation?Validation
What state needs to persist?State Management
Can the skill run overnight autonomously?All categories
How will Claude verify correct execution?Verification

Decision: Script vs No Script

Create Script WhenSkip Script When
Operation is deterministicRequires human judgment
Output can be validatedOne-time setup
Will be reused across invocationsSimple text output
Enables autonomous operationNo verification needed
External tool integrationPure Claude reasoning

See: references/script-integration-framework.md

Specification Structure

The specification captures all analysis insights in XML format:

<skill_specification>
  <metadata>
    <name>skill-name</name>
    <analysis_iterations>N</analysis_iterations>
    <timelessness_score>X/10</timelessness_score>
  </metadata>

  <context>
    <problem_statement>What + Why + Who</problem_statement>
    <existing_landscape>Related skills, distinctiveness</existing_landscape>
  </context>

  <requirements>
    <explicit>What user asked for</explicit>
    <implicit>Expected but unstated</implicit>
    <discovered>Found through analysis</discovered>
  </requirements>

  <architecture>
    <pattern>Selected pattern with WHY</pattern>
    <phases>Ordered phases with verification</phases>
    <decision_points>Branches and defaults</decision_points>
  </architecture>

  <scripts>
    <decision_summary>needs_scripts + rationale</decision_summary>
    <script_inventory>name, category, purpose, patterns</script_inventory>
    <agentic_capabilities>autonomous, self-verify, recovery</agentic_capabilities>
  </scripts>

  <evolution_analysis>
    <timelessness_score>X/10</timelessness_score>
    <extension_points>Where skill can grow</extension_points>
    <obsolescence_triggers>What would break it</obsolescence_triggers>
  </evolution_analysis>

  <anti_patterns>
    <pattern>What to avoid + WHY + alternative</pattern>
  </anti_patterns>

  <success_criteria>
    <criterion>Measurable + verification method</criterion>
  </success_criteria>
</skill_specification>

See: references/specification-template.md

Specification Validation

Before proceeding to Phase 3:

  • All sections present with no placeholders
  • Every decision includes WHY
  • Timelessness score ≥ 7 with justification
  • At least 2 extension points documented
  • All requirements traceable to source
  • Scripts section complete (if applicable)
  • Agentic capabilities documented (if scripts present)

Context: Fresh, clean (no analysis artifacts polluting) Standard: Zero errors—every section verified before proceeding

Generation Order

1. Create directory structure
   mkdir -p ~/.claude/skills/{skill-name}/references
   mkdir -p ~/.claude/skills/{skill-name}/assets/templates
   mkdir -p ~/.claude/skills/{skill-name}/scripts  # if scripts needed

2. Write SKILL.md
   • Frontmatter (YAML - allowed properties only)
   • Title and brief intro
   • Quick Start section
   • Triggers (3-5 varied phrases)
   • Quick Reference table
   • How It Works overview
   • Commands
   • Scripts section (if applicable)
   • Validation section
   • Anti-Patterns
   • Verification criteria
   • Deep Dive sections (in <details> tags)

3. Generate reference documents (if needed)
   • Deep documentation for complex topics
   • Templates for generated artifacts
   • Checklists for validation

4. Create assets (if needed)
   • Templates for skill outputs

5. Create scripts (if needed)
   • Use script-template.py as base
   • Include Result dataclass pattern
   • Add self-verification
   • Document exit codes
   • Test before finalizing

Quality Checks During Generation

CheckRequirement
FrontmatterOnly allowed properties (name, description, license, allowed-tools, metadata)
NameHyphen-case, ≤64 chars
Description≤1024 chars, no angle brackets
Triggers3-5 distinct, natural language
Phases1-3 max, not over-engineered
VerificationConcrete, measurable
Tables over proseStructured information in tables
No placeholder textEvery section fully written
Scripts (if present)Shebang, docstring, argparse, exit codes, Result pattern
Script docsScripts section in SKILL.md with usage examples

Panel: 3-4 Opus agents with distinct evaluative lenses Requirement: Unanimous approval (all agents) Fallback: Return to Phase 1 with feedback (max 5 iterations)

Panel Composition

AgentFocusKey CriteriaWhen Active
Design/ArchitectureStructure, patterns, correctnessPattern appropriate, phases logical, no circular depsAlways
Audience/UsabilityClarity, discoverability, completenessTriggers natural, steps unambiguous, no assumed knowledgeAlways
Evolution/TimelessnessFuture-proofing, extension, ecosystemScore ≥7, extension points clear, ecosystem fitAlways
Script/AutomationAgentic capability, verification, qualityScripts follow patterns, self-verify, documentedWhen scripts present

Script Agent (Conditional)

The Script Agent is activated when the skill includes a scripts/ directory. Focus areas:

CriterionChecks
Pattern ComplianceResult dataclass, argparse, exit codes
Self-VerificationScripts can verify their own output
Error HandlingGraceful failures, actionable messages
DocumentationUsage examples in SKILL.md
Agentic CapabilityCan run autonomously without human intervention

Script Agent Scoring:

ScoreMeaning
8-10Fully agentic, self-verifying, production-ready
6-7Functional but missing some agentic capabilities
<6Requires revision - insufficient automation quality

Agent Evaluation

Each agent produces:

## [Agent] Review

### Verdict: APPROVED / CHANGES_REQUIRED

### Scores
| Criterion | Score (1-10) | Notes |
|-----------|--------------|-------|

### Strengths
1. [Specific with evidence]

### Issues (if CHANGES_REQUIRED)
| Issue | Severity | Required Change |
|-------|----------|-----------------|

### Recommendations
1. [Even if approved]

Consensus Protocol

IF all agents APPROVED (3/3 or 4/4):
    → Finalize skill
    → Run validate-skill.py
    → Update registry
    → Complete

ELSE:
    → Collect all issues (including script issues)
    → Return to Phase 1 with issues as input
    → Re-apply targeted questioning
    → Regenerate skill and scripts
    → Re-submit to panel

IF 5 iterations without consensus:
    → Flag for human review
    → Present all agent perspectives
    → User makes final decision

See: references/synthesis-protocol.md

Every skill is evaluated through the evolution lens:

Temporal Projection

TimeframeKey Question
6 monthsHow will usage patterns evolve?
1 yearWhat ecosystem changes are likely?
2 yearsWhat new capabilities might obsolete this?
5 yearsIs the core problem still relevant?

Timelessness Scoring

ScoreDescriptionVerdict
1-3Transient, will be obsolete in monthsReject
4-6Moderate, depends on current toolingRevise
7-8Solid, principle-based, extensibleApprove
9-10Timeless, addresses fundamental problemExemplary

Requirement: All skills must score ≥7.

Anti-Obsolescence Patterns

DoDon't
Design around principlesHardcode implementations
Document the WHYOnly document the WHAT
Include extension pointsCreate closed systems
Abstract volatile dependenciesDirect coupling
Version-agnostic patternsPin specific versions

See: references/evolution-scoring.md

Select based on task complexity:

PatternUse WhenStructure
Single-PhaseSimple linear tasksSteps 1-2-3
ChecklistQuality/compliance audits☐ Item verification
GeneratorCreating artifactsInput → Transform → Output
Multi-PhaseComplex ordered workflowsPhase 1 → Phase 2 → Phase 3
Multi-Agent ParallelIndependent subtasksLaunch agents concurrently
Multi-Agent SequentialDependent subtasksAgent 1 → Agent 2 → Agent 3
OrchestratorCoordinating multiple skillsMeta-skill chains

Selection Decision Tree

Is it a simple procedure?
├── Yes → Single-Phase
└── No → Does it produce artifacts?
    ├── Yes → Generator
    └── No → Does it verify/audit?
        ├── Yes → Checklist
        └── No → Are subtasks independent?
            ├── Yes → Multi-Agent Parallel
            └── No → Multi-Agent Sequential or Multi-Phase
SKILLCREATOR_CONFIG:
  mode: autonomous
  depth: maximum  # always
  core_lens: evolution_timelessness

  analysis:
    min_lens_depth: 5
    max_questioning_rounds: 7
    termination_empty_rounds: 3

  synthesis:
    panel_size: 3
    require_unanimous: true
    max_iterations: 5
    escalate_to_human: true

  evolution:
    min_timelessness_score: 7
    min_extension_points: 2
    require_temporal_projection: true

  model:
    primary: claude-opus-4-5-20251101
    subagents: claude-opus-4-5-20251101

References


SkillRelationship
skill-composerCan orchestrate created skills
claude-authoring-guideDeeper patterns reference
codereviewPattern for multi-agent panels
maker-frameworkZero error standard source

Extension Points

  1. Additional Lenses: Add new thinking models to references/multi-lens-framework.md
  2. New Synthesis Agents: Extend panel beyond 4 agents for specific domains
  3. Custom Patterns: Add architecture patterns to selection guide
  4. Domain Templates: Add domain-specific templates to assets/templates/
  5. Script Patterns: Add new patterns to references/script-patterns-catalog.md
  6. Script Categories: Extend the 7 script categories for new use cases

Changelog

v3.2.0 (Current)

  • Added Script Integration Framework for agentic skills
  • Added 4th Script Agent to synthesis panel (conditional)
  • Added Phase 1D: Automation Analysis
  • Added Automation Lens questions to regression questioning
  • Created references/script-integration-framework.md
  • Created references/script-patterns-catalog.md
  • Created assets/templates/script-template.py
  • Updated skill-spec-template.xml with <scripts> section
  • Updated validate-skill.py with script validation
  • Skills can now include self-verifying Python scripts

v3.1.0

  • Added progressive disclosure structure
  • Fixed frontmatter for packaging compatibility
  • Added validation & packaging section
  • Deep dive sections now collapsible

v3.0.0

  • Complete redesign as ultimate meta-skill
  • Added regression questioning loop
  • Added multi-lens analysis framework (11 models)
  • Added evolution/timelessness core lens
  • Added multi-agent synthesis panel

v2.0.0

  • Pattern selection guide
  • Quality standards checklist

v1.0.0

  • Basic skill structure

Score

Total Score

60/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon