Changes
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..f051907
--- /dev/null
+++ b/README.md
@@ -0,0 +1,16 @@
+# Agent Skills
+
+My agent skills collection. Some of them are just direct copies from
+public skill repositories.
+
+## Skills
+
+## `deep-research`
+
+Heavily modified from
+https://github.com/wshuyi/deep-research/tree/main/skills/deep-research
+.
+
+## `skill-creator`
+
+This is from Claude.
diff --git a/skills/deep-research/SKILL.md b/skills/deep-research/SKILL.md
new file mode 100644
index 0000000..909381f
--- /dev/null
+++ b/skills/deep-research/SKILL.md
@@ -0,0 +1,550 @@
+---
+name: deep-research-recursive
+description: |
+ Deep Research with Enforced Recursion: A methodology that forces deep exploration
+ by mandating recursive research on significant findings until root causes are reached.
+
+ Key difference from regular deep-research: This skill GUARANTEES recursion depth
+ through explicit task spawning and tracking.
+
+ Trigger phrases:
+ - "deep research" / "in-depth analysis"
+ - "recursive research" / "root cause analysis"
+ - "help me research"
+ - "why does X happen" / "what causes X"
+---
+
+# Deep Research with Enforced Recursion
+
+Transform vague topics into research reports by **forcing recursive exploration**
+until fundamental truths are reached.
+
+## Core Philosophy
+
+1. **Recursion is not optional** - Every research thread MUST recurse at least once
+2. **Findings spawn sub-research** - Significant facts automatically trigger new research
+3. **Depth until root cause** - Keep recursing until you hit irreducible facts
+4. **Accumulate, don't lose** - All recursive findings merge into final report
+5. **Conclusions come from mechanism comparison, not "I feel like"**
+6. **First pin down facts, then derive**
+7. **Authority of sources prioritized: L1 > L2 > L3 > L4**
+
+---
+
+## Working Directory Structure
+
+```
+./research/<topic>/
+├── 00_problem_decomposition.md
+├── 01_source_references.md
+├── 02_fact_cards.md
+├── 03_comparison_framework.md
+├── 04_derivation_process.md
+├── 05_verification_records.md
+├── recursion_tree.md # Track recursion depth
+├── recursive/ # Sub-research artifacts
+│ ├── level1_<subtopic>/
+│ │ ├── findings.md
+│ │ └── sources.md
+│ ├── level2_<subtopic>/
+│ └── level3_<subtopic>/
+└── FINAL_research_report.md
+```
+
+---
+
+## The Recursion Guarantee
+
+### Minimum Depth Rule
+
+You MUST achieve at least **3 levels of recursion depth**:
+
+```
+Level 0: Original question
+ └── Level 1: First significant finding
+ └── Level 2: Deeper cause of Level 1
+ └── Level 3: Root cause or fundamental principle
+```
+
+**BLOCKING**: Cannot complete report until minimum depth achieved.
+
+### Recursion Tracking File
+
+Create `recursion_tree.md` at the start:
+
+```markdown
+# Research Recursion Tree
+
+## Level 0: [Original Topic]
+- Status: pending/in_progress/completed
+- Key Finding: [main finding]
+- Spawns: Level 1 research on [topic]
+
+## Level 1: [Subtopic]
+- Parent: Level 0
+- Status: pending/in_progress/completed
+- Key Finding: [finding]
+- Spawns: Level 2 research on [topic] (if deeper exists)
+
+## Depth Achievement
+- Current Depth: 0
+- Minimum Required: 3
+- Can Stop: NO
+```
+
+### When Recursion is MANDATORY
+
+| Finding Type | Must Recurse On | Example |
+|--------------|-----------------|---------|
+| Cause identified | WHY this cause exists | "Revenue dropped" → recurse on why |
+| Trend observed | WHAT drives it | "Usage increasing" → recurse on driver |
+| Difference found | WHY the difference | "X is faster than Y" → recurse on reason |
+| Correlation found | THE causation mechanism | "A correlates with B" → recurse on how |
+| Problem diagnosed | ROOT cause | "System slow" → recurse on bottleneck |
+
+### When Recursion Can Stop
+
+1. **Fundamental principle**: Physics laws, math theorems, definitions
+2. **Irreducible fact**: "Company founded in 1995" (no deeper cause)
+3. **Maximum depth**: Hit depth limit (default: 5 levels)
+4. **Out of scope**: Leaves original question's domain
+
+**Document stopping reason** in recursion tree.
+
+---
+
+## Workflow
+
+### Step 0: Problem Type Judgment
+
+Determine research question type:
+
+| Problem Type | Core Task | Focus Dimensions |
+|--------------|-----------|------------------|
+| **Concept Comparison** | Establish comparison framework | Mechanism differences, applicable boundaries |
+| **Decision Support** | Weigh trade-offs | Cost, risk, benefit |
+| **Trend Analysis** | Sort evolution context | History, driving factors, predictions |
+| **Problem Diagnosis** | Root cause analysis | Symptoms, causes, evidence chain |
+| **Knowledge Organization** | Systematically organize | Definition, classification, relationships |
+
+### Step 0.5: Time Sensitivity Judgment (BLOCKING)
+
+Before research, determine time sensitivity:
+
+| Sensitivity | Typical Domains | Source Time Window |
+|-------------|-----------------|-------------------|
+| **🔴 Very High** | AI/LLM, Blockchain | 3-6 months |
+| **🟠 High** | Cloud Services, Frontend | 6-12 months |
+| **🟡 Medium** | Languages, Databases | 1-2 years |
+| **🟢 Low** | Algorithms, Patterns | No limit |
+
+**For 🔴 Very High sensitivity**:
+- Use `time_range: "month"` in searches
+- Must consult official docs first
+- All technical descriptions must include version numbers
+- Sources older than 6 months: historical reference only
+
+**Save**: Append to `00_problem_decomposition.md`
+
+### Step 1: Problem Decomposition
+
+Break topic into 2-4 researchable sub-problems:
+
+- **Sub-problem A**: "What is X, how does it work?"
+- **Sub-problem B**: "What's the relationship/difference between X and Y?"
+- **Sub-problem C**: "In what scenarios is X applicable/not applicable?"
+- **Sub-problem D**: "What are X's development trends/best practices?"
+
+**Define research boundaries**:
+
+| Dimension | Must Define | Example |
+|-----------|-------------|---------|
+| Population | Which group? | College vs. high school students |
+| Region | Where? | US vs. China vs. global |
+| Time Period | When? | After 2020 vs. historical |
+| Level | What level? | Undergrad vs. graduate |
+
+**Save**: Write `00_problem_decomposition.md`
+
+### Step 2: Source Layering
+
+Grade sources by authority:
+
+| Tier | Source Type | Purpose | Credibility |
+|------|-------------|---------|-------------|
+| **L1** | Official docs, papers, RFCs | Definitions, mechanisms | ✅ High |
+| **L2** | Official blogs, talks | Design intent | ✅ High |
+| **L3** | Media, tutorials | Cases, intuition | ⚠️ Medium |
+| **L4** | Community, forums | Blind spots, verification | ❓ Low |
+
+**Principles**:
+- Conclusions traceable to L1/L2
+- L3/L4 for assistance only
+- Record all sources
+
+**Time filtering** (based on Step 0.5):
+
+| Sensitivity | Filter Rule |
+|-------------|-------------|
+| 🔴 Very High | Only < 6 months as factual basis |
+| 🟠 High | Prioritize < 1 year |
+| 🟡 Medium | Normal use < 2 years |
+| 🟢 Low | No limit |
+
+**Save**: Append each source to `01_source_references.md`:
+```markdown
+## Source #[N]
+- **Title**: [title]
+- **Link**: [URL]
+- **Tier**: L1/L2/L3/L4
+- **Release Date**: [YYYY-MM-DD]
+- **Timeliness**: ✅/⚠️/❌
+- **Target Object**: [who/what this applies to]
+- **Summary**: [1-2 sentences]
+```
+
+### Step 3: Fact Extraction
+
+Transform sources into **verifiable fact cards**:
+
+```markdown
+## Fact #[N]
+- **Statement**: [specific fact]
+- **Source**: [Source #N] [Link]
+- **Confidence**: ✅/⚠️/❓
+- **Related Dimension**: [comparison dimension]
+```
+
+**Confidence levels**:
+- ✅ High: Explicitly in official docs
+- ⚠️ Medium: Official blog/talk, not formal doc
+- ❓ Low: Non-official source or speculation
+
+**Save**: Append to `02_fact_cards.md`
+
+### Step 4: Comparison Framework
+
+Select analysis dimensions based on problem type:
+
+**General Dimensions**:
+1. Goal/solving what problem
+2. Mechanism/process
+3. Input/output/boundaries
+4. Advantages/disadvantages
+5. Applicable scenarios
+6. Cost/benefit/risk
+7. Historical evolution
+8. Security/permissions
+
+**Concept Comparison Dimensions**:
+1. Definition and essence
+2. Trigger method
+3. Execution subject
+4. Input/output constraints
+5. Determinism
+6. Resource management
+7. Composition methods
+8. Security boundaries
+
+**Decision Support Dimensions**:
+1. Solution overview
+2. Implementation cost
+3. Maintenance cost
+4. Risk assessment
+5. Benefit expectation
+6. Applicable scenarios
+7. Team requirements
+8. Migration difficulty
+
+**Save**: Write `03_comparison_framework.md`
+
+### Step 5: Reference Alignment
+
+Ensure unified definitions:
+
+- [ ] Is reference object's definition stable?
+- [ ] Need verification or use common sense?
+- [ ] Reader's understanding matches mine?
+- [ ] Ambiguities need clarifying?
+
+### Step 6: Derivation Chain
+
+Write "fact → comparison → conclusion" explicitly:
+
+```markdown
+## Dimension: [Name]
+
+### Fact Confirmation
+According to [Fact #X], X's mechanism is...
+
+### Comparison Reference
+Y's mechanism is... (Source: [Fact #Y])
+
+### Conclusion
+Therefore, the difference is...
+
+### Confidence
+✅/⚠️/❓ + Reason
+```
+
+**Save**: Write `04_derivation_process.md`
+
+### Step 7: Use Case Verification
+
+Verify conclusions with typical scenario:
+
+**Verification Questions**:
+- According to my conclusion, how should this scenario be handled?
+- Is it actually that way?
+- Are there counterexamples?
+
+**Backtracking Checklist**:
+- [ ] Conclusions align with fact cards?
+- [ ] Important dimensions missed?
+- [ ] Over-inference?
+- [ ] Actionable/verifiable?
+
+**Save**: Write `05_verification_records.md`
+
+---
+
+### Step 8: Recursion Execution (BLOCKING)
+
+**This step is MANDATORY.**
+
+#### 8.1 Identify Recursion Candidates
+
+From findings, identify 2-3 most significant facts that:
+1. Are central to main conclusion
+2. Have underlying cause worth researching
+3. Are not yet "fundamental"
+
+For each:
+```markdown
+## Recursion Candidate: [Finding]
+- Significance: [why it matters]
+- Has Deeper Cause?: YES/NO
+- Deeper Hypothesis: [what might explain it]
+- Recursion Required?: YES/NO
+```
+
+#### 8.2 Check Depth Requirement
+
+```
+Current Depth: [N]
+Minimum Required: 3
+Maximum Allowed: 5
+
+Status: [ ] Need more recursion / [ ] Met
+```
+
+If not met, **MUST spawn recursive research**.
+
+#### 8.3 Spawn Recursive Research
+
+Use **Task tool**:
+
+```
+Task(
+ description="Recursive research: [subtopic]",
+ subagent_type="general",
+ prompt="""
+ RECURSIVE RESEARCH TASK
+
+ Parent Topic: [parent]
+ Current Depth: [N]
+ Your Topic: [subtopic]
+
+ Execute deep-research-recursive skill for this subtopic.
+
+ Save artifacts to: ./research/[parent]/recursive/level[N]_[subtopic]/
+
+ REQUIRED OUTPUT (concise):
+ 1. Key findings (2-3 bullets)
+ 2. Has deeper cause worth researching? YES/NO
+ 3. If YES, what deeper topic?
+ 4. Key sources (with links)
+
+ Do NOT output full report. Output only structured summary.
+ """
+)
+```
+
+#### 8.4 Record in Recursion Tree
+
+After each spawn completes:
+
+```markdown
+## Level [N]: [Subtopic]
+- Parent: Level [N-1]
+- Status: completed
+- Key Findings:
+ 1. [finding]
+ 2. [finding]
+- Has Deeper Cause: YES/NO
+- Deeper Topic: [if YES]
+- Sources: [list]
+```
+
+#### 8.5 Recursion Loop
+
+```
+WHILE depth < minimum OR significant_findings_have_deeper_causes:
+ spawn_recursive_research()
+ depth += 1
+ update_recursion_tree()
+
+ IF depth >= maximum:
+ log("Max depth reached")
+ BREAK
+```
+
+---
+
+### Step 9: Synthesis and Report
+
+#### 9.1 Create Depth Trail
+
+```markdown
+# Recursive Findings Synthesis
+
+## Depth Trail
+[Original Question]
+ → [Level 1]: [finding]
+ → [Level 2]: [finding]
+ → [Level 3]: [finding]
+ → [Root/Fundamental]: [irreducible fact]
+
+## Chain of Causation
+1. [Level 0 conclusion] because...
+2. [Level 1 reason] because...
+3. [Level 2 reason] because...
+4. [Level 3 / fundamental truth]
+```
+
+#### 9.2 Generate Final Report
+
+```markdown
+# [Topic] Research Report
+
+## Abstract
+[One-line summary with root cause]
+
+## Recursive Depth
+This research reached depth [N]:
+- Level 1: [finding]
+- Level 2: [finding]
+- Level 3: [finding]
+
+## Root Cause / Fundamental
+[The irreducible truth at deepest level]
+
+## Main Findings
+[Integrated findings from all levels]
+
+## 1. Concept Alignment
+### 1.1 What is X
+### 1.2 What is Y (reference)
+
+## 2. Working Mechanism
+[Core differences]
+
+## 3. Connections
+[Common problems solved]
+
+## 4. Differences
+[Dimension-by-dimension comparison]
+
+## 5. Use Cases
+
+## 6. Summary and Suggestions
+
+## References
+[All sources with links]
+```
+
+---
+
+## Quality Checklist
+
+Before completion:
+
+- [ ] `recursion_tree.md` exists and complete
+- [ ] Minimum depth 3 achieved
+- [ ] Each level has documented findings
+- [ ] Stopping reason documented for leaf nodes
+- [ ] Chain of causation explicitly stated
+- [ ] All core conclusions have L1/L2 support
+- [ ] At least one use case verification
+- [ ] References complete, links accessible
+
+---
+
+## Anti-Patterns
+
+| Wrong | Correct |
+|-------|---------|
+| "Revenue dropped" → Stop | → Recurse on WHY |
+| "X better than Y" → Stop | → Recurse on WHAT MAKES IT BETTER |
+| "Trend increasing" → Stop | → Recurse on DRIVER |
+| "It's complicated" → Stop | → Decompose and recurse |
+| "Multiple factors" → List | → Recurse on each significant factor |
+
+---
+
+## Example: Recursion in Action
+
+**Request**: "Why is Phil Spencer leaving Xbox?"
+
+```
+Level 0: Original
+→ Finding: Xbox hardware revenue declining rapidly
+→ Recurse: WHY is revenue declining?
+
+Level 1: Revenue Decline
+→ Finding: Game Pass cannibalizing game sales; hardware loss-making
+→ Recurse: WHY does Game Pass cannibalize?
+
+Level 2: Game Pass Cannibalization
+→ Finding: Subscription model reduces individual purchases
+→ Recurse: WHY did Microsoft choose this model?
+
+Level 3: Microsoft Strategy
+→ Finding: Shift to recurring revenue and ecosystem lock-in
+→ Recurse: WHY this strategic shift?
+
+Level 4: Root Cause (STOP)
+→ Finding: Nadella's company-wide strategy: cloud services, subscriptions,
+ platforms over one-time sales. Xbox is now a cloud gaming service.
+→ This is a fundamental business strategy decision.
+```
+
+**Depth: 4 levels**
+**Root Cause: Strategic pivot to cloud/subscription under Nadella**
+
+---
+
+## Quick Reference
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ Deep Research with Enforced Recursion │
+├─────────────────────────────────────────────────────────────┤
+│ MINIMUM DEPTH: 3 | MAXIMUM: 5 │
+│ │
+│ 0. Problem type → select framework │
+│ 0.5. Time sensitivity → filter sources │
+│ 1. Decompose → 2-4 sub-problems │
+│ 2. Source layering → L1 > L2 > L3 > L4 │
+│ 3. Fact extraction → with confidence levels │
+│ 4. Comparison framework → select dimensions │
+│ 5. Reference alignment → unified definitions │
+│ 6. Derivation chain → fact → comparison → conclusion │
+│ 7. Use case verification → sanity check │
+│ 8. RECURSION → spawn sub-research (MANDATORY) │
+│ 9. Synthesis → merge all recursive findings │
+├─────────────────────────────────────────────────────────────┤
+│ STOP WHEN: fundamental principle / irreducible fact / │
+│ max depth / out of scope │
+└─────────────────────────────────────────────────────────────┘
+```
diff --git a/skills/deep-research/templates/comparison-framework.md b/skills/deep-research/templates/comparison-framework.md
new file mode 100644
index 0000000..bb5bac8
--- /dev/null
+++ b/skills/deep-research/templates/comparison-framework.md
@@ -0,0 +1,207 @@
+# Comparison Framework Template
+
+Select the corresponding comparison dimension framework based on problem type.
+
+---
+
+## I. Concept Comparison Framework
+
+Applicable to: Technical concept comparison, product comparison, solution comparison
+
+### 8-Dimension Comparison Table
+
+| Dimension | X | Y | Difference Description |
+|-----------|---|---|------------------------|
+| **1. Definition and Essence** | | | |
+| **2. Trigger/Invocation Method** | | | |
+| **3. Execution Subject** | | | |
+| **4. Input/Output and Type Constraints** | | | |
+| **5. Determinism and Repeatability** | | | |
+| **6. Resource and Context Management** | | | |
+| **7. Composition and Reuse Methods** | | | |
+| **8. Security Boundaries and Permission Control** | | | |
+
+### Usage Instructions
+
+1. First fill in facts (based on fact cards)
+2. Then fill in difference descriptions (derivation)
+3. Mark which are "decisive differences"
+4. Supplement missing dimensions (if any)
+
+---
+
+## II. Decision Support Framework
+
+Applicable to: Technology selection, solution decision, tool choice
+
+### Decision Matrix
+
+| Dimension | Solution A | Solution B | Solution C | Weight |
+|-----------|------------|------------|------------|--------|
+| **Implementation Cost** | | | | |
+| **Maintenance Cost** | | | | |
+| **Learning Curve** | | | | |
+| **Team Experience** | | | | |
+| **Community Ecosystem** | | | | |
+| **Performance** | | | | |
+| **Scalability** | | | | |
+| **Risk Assessment** | | | | |
+| **Migration Difficulty** | | | | |
+| **Overall Score** | | | | |
+
+### Risk Assessment Sub-Table
+
+| Risk Item | Likelihood | Impact Level | Mitigation |
+|-----------|------------|--------------|------------|
+| | High/Medium/Low | High/Medium/Low | |
+
+### Scenario Applicability
+
+| Scenario | Recommended Solution | Reason |
+|----------|----------------------|--------|
+| Scenario A | | |
+| Scenario B | | |
+| Scenario C | | |
+
+---
+
+## III. Trend Analysis Framework
+
+Applicable to: Technology trends, market analysis, development predictions
+
+### Evolution Timeline
+
+```
+[Origin Stage] → [Development Stage] → [Maturity Stage] → [Current State] → [Future Trends]
+ ↓ ↓ ↓ ↓ ↓
+ [Key Event] [Key Event] [Key Event] [Key Event] [Prediction Basis]
+```
+
+### PESTEL Analysis (External Driving Factors)
+
+| Factor | Current State | Trend Direction | Impact Assessment |
+|--------|---------------|-----------------|-------------------|
+| **P**olitical | | ↑/↓/→ | |
+| **E**conomic | | ↑/↓/→ | |
+| **S**ocial | | ↑/↓/→ | |
+| **T**echnological | | ↑/↓/→ | |
+| **E**nvironmental | | ↑/↓/→ | |
+| **L**egal | | ↑/↓/→ | |
+
+### Competitive Landscape
+
+| Player | Position | Advantages | Disadvantages | Movements |
+|--------|----------|------------|--------------|-----------|
+| | | | | |
+
+### Predictions and Uncertainty
+
+| Prediction Item | Time Range | Confidence | Basis |
+|-----------------|------------|------------|-------|
+| | Short/Medium/Long term | High/Medium/Low | |
+
+---
+
+## IV. Problem Diagnosis Framework
+
+Applicable to: Fault analysis, problem root cause, bottleneck diagnosis
+
+### 5 Why Analysis
+
+```
+Problem Phenomenon: [Description]
+ ↓ Why?
+Cause 1:
+ ↓ Why?
+Cause 2:
+ ↓ Why?
+Cause 3:
+ ↓ Why?
+Cause 4:
+ ↓ Why?
+Root Cause: [Root Cause]
+```
+
+### Fishbone Diagram Analysis
+
+```
+ ┌─ Human Factors
+ ├─ Process Factors
+Problem ←───────────┼─ Technical Factors
+ ├─ Environmental Factors
+ └─ Tool Factors
+```
+
+### Evidence Chain
+
+| Number | Symptom/Phenomenon | Related Evidence | Pointing to Cause |
+|--------|---------------------|------------------|-------------------|
+| 1 | | | |
+| 2 | | | |
+| 3 | | | |
+
+### Solution Comparison
+
+| Solution | Target Cause | Implementation Difficulty | Time to Effect | Recommendation |
+|----------|--------------|--------------------------|----------------|----------------|
+| | | High/Medium/Low | Short/Medium/Long | ★☆☆☆☆ |
+
+---
+
+## V. Knowledge Organization Framework
+
+Applicable to: Concept organization, knowledge system, domain introduction
+
+### Concept Hierarchy
+
+```
+Primary Concept (Domain)
+├── Secondary Concept (Category)
+│ ├── Tertiary Concept (Subcategory)
+│ │ └── Specific Example
+│ └── Tertiary Concept
+└── Secondary Concept
+ └── ...
+```
+
+### Concept Relationship Table
+
+| Concept A | Relationship Type | Concept B | Description |
+|-----------|-------------------|-----------|-------------|
+| | is-a (inheritance) | | |
+| | has-a (containment) | | |
+| | uses | | |
+| | depends-on | | |
+| | conflicts-with | | |
+
+### Core Concept Cards
+
+```markdown
+## Concept: [Name]
+
+**Definition**: [One-sentence definition]
+
+**Essence**: [Deeper explanation]
+
+**Analogy**: [Analogize with familiar things]
+
+**Boundaries**:
+- What it is:
+- What it's not:
+
+**Related Concepts**: [List]
+
+**Common Misconceptions**: [List]
+```
+
+---
+
+## Dimension Selection Guide
+
+| Problem Type | Preferred Framework | Core Dimensions |
+|--------------|---------------------|------------------|
+| A vs B Difference | Concept Comparison | Mechanism, Trigger, Input/Output |
+| Which to Choose | Decision Support | Cost, Risk, Scenario |
+| What Will Happen | Trend Analysis | Driving Factors, Evolution Context |
+| Why Problems Occur | Problem Diagnosis | Symptoms, Evidence Chain, Root Cause |
+| What Is This | Knowledge Organization | Definition, Classification, Relationships |
diff --git a/skills/deep-research/templates/fact-card.md b/skills/deep-research/templates/fact-card.md
new file mode 100644
index 0000000..dab2e3e
--- /dev/null
+++ b/skills/deep-research/templates/fact-card.md
@@ -0,0 +1,87 @@
+# Fact Card Template
+
+Used for recording and organizing verifiable facts extracted during research.
+
+## Template Format
+
+```markdown
+## Fact Card #[Number]
+
+**Topic**: [Associated topic/dimension]
+
+**Fact Statement**:
+[Specific factual description, using declarative sentences, without subjective judgment]
+
+**Source**:
+- Source: [Document name/website]
+- Link: [URL]
+- Section: [Specific section/paragraph]
+- Retrieved Date: [YYYY-MM-DD]
+
+**Confidence**: [✅ High / ⚠️ Medium / ❓ Low]
+
+**Confidence Reason**:
+- ✅ High: Explicitly stated in official documentation
+- ⚠️ Medium: Mentioned in official blog/talk but not formally documented
+- ❓ Low: Speculation or from non-official sources
+
+**Related Facts**: [Other associated fact card numbers]
+
+**Notes**: [Supplementary notes, conflicting information, points to verify]
+```
+
+## Usage Example
+
+```markdown
+## Fact Card #001
+
+**Topic**: Claude Skills Trigger Mechanism
+
+**Fact Statement**:
+Skills are model-invoked; Claude decides whether to enable a Skill based on how well the user's request matches the description field in SKILL.md, without requiring explicit user invocation.
+
+**Source**:
+- Source: Claude Code Official Documentation
+- Link: https://code.claude.com/docs/en/skills
+- Section: How skills work
+- Retrieved Date: 2025-01-11
+
+**Confidence**: ✅ High
+
+**Confidence Reason**:
+Official documentation explicitly states: "Claude will automatically use relevant skills when they match your request"
+
+**Related Facts**: #002 (Progressive Disclosure), #003 (SKILL.md Structure)
+
+**Notes**: Contrasts with traditional function explicit invocation
+```
+
+## Fact Card Summary Table
+
+| Number | Topic | Confidence | Keywords |
+|--------|-------|------------|----------|
+| #001 | Trigger Mechanism | ✅ | model-invoked |
+| #002 | Loading Method | ✅ | progressive disclosure |
+| ... | ... | ... | ... |
+
+## Conflicting Information Recording
+
+When discovering conflicting information from different sources, record as follows:
+
+```markdown
+## Conflict #M001
+
+**Fact A**: [Source A's statement]
+**Fact B**: [Source B's statement]
+
+**Source Comparison**:
+- A comes from: [Source A's authority level]
+- B comes from: [Source B's authority level]
+
+**Handling Method**:
+- [ ] Trust the more authoritative source
+- [ ] Keep both, explain the discrepancy in the report
+- [ ] Need further verification
+
+**Verification Plan**: [How to verify which is correct]
+```
diff --git a/skills/deep-research/templates/recursion-tree.md b/skills/deep-research/templates/recursion-tree.md
new file mode 100644
index 0000000..c8f1b78
--- /dev/null
+++ b/skills/deep-research/templates/recursion-tree.md
@@ -0,0 +1,240 @@
+# Recursion Tree Template
+
+Track research depth and recursive findings.
+
+---
+
+## Template
+
+```markdown
+# Research Recursion Tree
+
+## Research Topic
+[Original question from user]
+
+## Time Sensitivity
+- Level: 🔴/🟠/🟡/🟢
+- Source Time Window: [X months/years]
+
+---
+
+## Level 0: [Original Topic]
+
+- **Status**: pending | in_progress | completed
+- **Started**: [YYYY-MM-DD HH:MM]
+- **Completed**: [YYYY-MM-DD HH:MM]
+- **Problem Type**: Concept Comparison | Decision Support | Trend Analysis | Problem Diagnosis | Knowledge Organization
+- **Key Finding**: [Main discovery]
+- **Significance**: [Why this matters]
+- **Has Deeper Cause**: YES | NO
+- **Recursion Candidate**: [What to research next if YES]
+- **Spawns**: Level 1 research on [specific subtopic]
+
+---
+
+## Level 1: [Subtopic 1]
+
+- **Parent**: Level 0
+- **Status**: pending | in_progress | completed
+- **Started**: [YYYY-MM-DD HH:MM]
+- **Completed**: [YYYY-MM-DD HH:MM]
+- **Key Finding**: [Discovery]
+- **Significance**: [Why this matters to parent finding]
+- **Has Deeper Cause**: YES | NO
+- **Recursion Candidate**: [What to research next if YES]
+- **Spawns**: Level 2 research on [specific subtopic]
+- **Sources**:
+ 1. [Source title](URL)
+ 2. [Source title](URL)
+
+---
+
+## Level 2: [Subtopic 2]
+
+- **Parent**: Level 1
+- **Status**: pending | in_progress | completed
+- **Started**: [YYYY-MM-DD HH:MM]
+- **Completed**: [YYYY-MM-DD HH:MM]
+- **Key Finding**: [Discovery]
+- **Significance**: [Why this matters to parent finding]
+- **Has Deeper Cause**: YES | NO
+- **Recursion Candidate**: [What to research next if YES]
+- **Spawns**: Level 3 research on [specific subtopic]
+- **Sources**:
+ 1. [Source title](URL)
+ 2. [Source title](URL)
+
+---
+
+## Level 3: [Subtopic 3]
+
+- **Parent**: Level 2
+- **Status**: pending | in_progress | completed
+- **Started**: [YYYY-MM-DD HH:MM]
+- **Completed**: [YYYY-MM-DD HH:MM]
+- **Key Finding**: [Discovery]
+- **Is Fundamental**: YES | NO
+- **Stopping Reason**: [If YES, why this is irreducible]
+- **Spawns**: None (depth reached)
+- **Sources**:
+ 1. [Source title](URL)
+ 2. [Source title](URL)
+
+---
+
+## Depth Achievement
+
+| Metric | Value |
+|--------|-------|
+| Current Depth | [N] |
+| Minimum Required | 3 |
+| Maximum Allowed | 5 |
+| Can Stop | YES / NO |
+| Stopping Reason | [If YES, explain] |
+
+---
+
+## Chain of Causation
+
+```
+[Level 0 Finding]
+ ↓ because
+[Level 1 Finding]
+ ↓ because
+[Level 2 Finding]
+ ↓ because
+[Level 3 Finding / Root Cause]
+ ↓
+[FUNDAMENTAL: This is irreducible because...]
+```
+
+---
+
+## Recursive Findings Summary
+
+| Level | Topic | Key Finding | Can Go Deeper? |
+|-------|-------|-------------|----------------|
+| 0 | [topic] | [finding] | YES/NO |
+| 1 | [topic] | [finding] | YES/NO |
+| 2 | [topic] | [finding] | YES/NO |
+| 3 | [topic] | [finding] | NO (fundamental) |
+
+---
+
+## Artifacts Location
+
+| Level | Directory |
+|-------|-----------|
+| 0 | `./research/<topic>/` |
+| 1 | `./research/<topic>/recursive/level1_<subtopic>/` |
+| 2 | `./research/<topic>/recursive/level2_<subtopic>/` |
+| 3 | `./research/<topic>/recursive/level3_<subtopic>/` |
+```
+
+---
+
+## Status Definitions
+
+| Status | Meaning |
+|--------|---------|
+| pending | Not yet started |
+| in_progress | Currently researching |
+| completed | Research finished, findings documented |
+
+---
+
+## Stopping Reasons
+
+When marking `Can Stop: YES`, document one of:
+
+1. **Fundamental principle reached**: Physics law, math theorem, established definition
+2. **Irreducible fact**: Historical fact, documented event, no deeper cause
+3. **Maximum depth reached**: Hit depth limit of 5 levels
+4. **Out of scope**: Further recursion leaves original question's domain
+
+---
+
+## Example
+
+```markdown
+# Research Recursion Tree
+
+## Research Topic
+Why is Phil Spencer leaving Xbox?
+
+## Time Sensitivity
+- Level: 🟡 Medium
+- Source Time Window: 1-2 years
+
+---
+
+## Level 0: Phil Spencer Leaving Xbox
+
+- **Status**: completed
+- **Key Finding**: Xbox hardware revenue declining rapidly, leadership change to software-focused strategy
+- **Has Deeper Cause**: YES
+- **Recursion Candidate**: Why is Xbox hardware revenue declining?
+- **Spawns**: Level 1 research on "Xbox hardware revenue decline causes"
+
+---
+
+## Level 1: Xbox Hardware Revenue Decline
+
+- **Parent**: Level 0
+- **Status**: completed
+- **Key Finding**: Game Pass subscription model cannibalizing individual game sales; hardware sold at loss
+- **Has Deeper Cause**: YES
+- **Recursion Candidate**: Why does Game Pass cannibalize sales?
+- **Spawns**: Level 2 research on "Game Pass cannibalization mechanism"
+
+---
+
+## Level 2: Game Pass Cannibalization Mechanism
+
+- **Parent**: Level 1
+- **Status**: completed
+- **Key Finding**: Users wait for games to hit Game Pass instead of buying; subscription revenue doesn't offset lost sales for third-party titles
+- **Has Deeper Cause**: YES
+- **Recursion Candidate**: Why did Microsoft choose this model despite cannibalization?
+- **Spawns**: Level 3 research on "Microsoft strategic shift"
+
+---
+
+## Level 3: Microsoft Strategic Shift
+
+- **Parent**: Level 2
+- **Status**: completed
+- **Key Finding**: Under Satya Nadella, Microsoft pivoted from one-time sales to cloud services and recurring revenue. Xbox is now a cloud gaming service, not primarily a console.
+- **Is Fundamental**: YES
+- **Stopping Reason**: This is a fundamental business strategy decision at CEO level - no deeper cause within gaming domain
+
+---
+
+## Depth Achievement
+
+| Metric | Value |
+|--------|-------|
+| Current Depth | 4 |
+| Minimum Required | 3 |
+| Maximum Allowed | 5 |
+| Can Stop | YES |
+| Stopping Reason | Fundamental strategic decision reached |
+
+---
+
+## Chain of Causation
+
+```
+Phil Spencer leaving Xbox
+ ↓ because
+Xbox hardware revenue declining rapidly
+ ↓ because
+Game Pass cannibalizing game sales, hardware loss-making
+ ↓ because
+Subscription model changes user purchasing behavior
+ ↓ because
+Microsoft's strategic pivot to cloud/recurring revenue under Nadella
+ ↓
+FUNDAMENTAL: CEO-level company strategy shift
+```
+```
diff --git a/skills/deep-research/templates/report-structure.md b/skills/deep-research/templates/report-structure.md
new file mode 100644
index 0000000..24e9861
--- /dev/null
+++ b/skills/deep-research/templates/report-structure.md
@@ -0,0 +1,328 @@
+# Report Structure Template
+
+Select the corresponding report structure based on problem type.
+
+---
+
+## I. Concept Comparison Report
+
+```markdown
+# [X] vs [Y]: In-Depth Comparative Analysis
+
+## Abstract
+
+[One-line core conclusion, can be directly repeated]
+
+Example: "X is more like [Position A], Y is more like [Position B]; the core difference lies in [decisive difference]."
+
+---
+
+## 1. Concept Alignment
+
+### 1.1 What is X
+
+**Official Definition**: [Cite official documentation]
+
+**Plain Language Explanation**: [Explain in terms familiar to readers]
+
+**Why It Exists**: [What problem it solves]
+
+### 1.2 What is Y (Reference)
+
+**Definition**: [Stable/accepted definition]
+
+**Reason for Being Comparison Baseline**: [Why it's selected as reference]
+
+---
+
+## 2. Working Mechanism
+
+> This is the core chapter distinguishing X from Y
+
+### 2.1 X's Working Mechanism
+
+[Describe in detail how X runs, what the key processes are]
+
+### 2.2 Y's Working Mechanism
+
+[Briefly describe Y's mechanism, as comparison reference]
+
+### 2.3 Mechanism Difference Summary
+
+| Dimension | X | Y |
+|-----------|---|---|
+| [Key Dimension 1] | | |
+| [Key Dimension 2] | | |
+| [Key Dimension 3] | | |
+
+---
+
+## 3. Connections (Common Points)
+
+> Build bridges, avoid extreme statements of "completely different"
+
+1. **[Common Point 1]**: [Explanation]
+2. **[Common Point 2]**: [Explanation]
+3. **[Common Point 3]**: [Explanation]
+
+---
+
+## 4. Differences (Core Differences)
+
+> Compare item by item by dimension, focus on highlighting decisive differences
+
+### 4.1 [Dimension 1]: [Dimension Name]
+
+- **X**: [Description]
+- **Y**: [Description]
+- **Difference Impact**: [What this difference means]
+
+### 4.2 [Dimension 2]: [Dimension Name]
+
+...
+
+### 4.3 Decisive Difference Summary
+
+The 3 most critical differences:
+
+1. **[Difference 1]**: [One-sentence explanation]
+2. **[Difference 2]**: [One-sentence explanation]
+3. **[Difference 3]**: [One-sentence explanation]
+
+---
+
+## 5. Use Case Demonstration
+
+> Ground the abstract to specific scenarios
+
+### Scenario: [Scenario Description]
+
+**If Using X**:
+[How to do it specifically]
+
+**If Using Y**:
+[How to do it specifically]
+
+**Comparison**:
+[Which is more suitable in this scenario and why]
+
+---
+
+## 6. Summary and Suggestions
+
+### 6.1 One-Line Summary
+
+> Can be directly repeated in meetings
+
+[Summary sentence]
+
+### 6.2 When to Choose X
+
+- [Scenario 1]
+- [Scenario 2]
+
+### 6.3 When to Choose Y
+
+- [Scenario 1]
+- [Scenario 2]
+
+### 6.4 Precautions
+
+- [Point of attention 1]
+- [Point of attention 2]
+
+---
+
+## References
+
+### Primary Sources (L1/L2)
+
+1. [Title](Link) - [Brief description]
+2. ...
+
+### Supporting Sources (L3/L4)
+
+1. [Title](Link) - [Brief description]
+2. ...
+
+---
+
+## Appendix: Fact Card Summary
+
+| Number | Fact | Source | Confidence |
+|--------|------|--------|------------|
+| #001 | | | ✅ |
+| #002 | | | ⚠️ |
+```
+
+---
+
+## II. Decision Support Report
+
+```markdown
+# [Decision Question]: Solution Analysis and Suggestions
+
+## Abstract
+
+**Question**: [One-sentence describing the decision question]
+
+**Suggestion**: [Recommended solution] + [Core reason]
+
+**Prerequisites**: [Prerequisites for the suggestion to hold]
+
+---
+
+## 1. Decision Background
+
+### 1.1 Business Scenario
+
+[Describe the business background requiring a decision]
+
+### 1.2 Key Constraints
+
+- Constraint 1: [Description]
+- Constraint 2: [Description]
+
+### 1.3 Decision Objectives
+
+- Primary objective: [Description]
+- Secondary objective: [Description]
+
+---
+
+## 2. Candidate Solution Overview
+
+### Solution A: [Name]
+
+[One paragraph overview]
+
+### Solution B: [Name]
+
+[One paragraph overview]
+
+### Solution C: [Name] (if applicable)
+
+[One paragraph overview]
+
+---
+
+## 3. Multi-Dimensional Comparison
+
+| Dimension | Solution A | Solution B | Solution C |
+|-----------|------------|------------|------------|
+| Implementation Cost | | | |
+| Maintenance Cost | | | |
+| Learning Curve | | | |
+| Performance | | | |
+| Scalability | | | |
+| Ecosystem Maturity | | | |
+
+---
+
+## 4. Risk Analysis
+
+### Solution A Risks
+
+| Risk | Likelihood | Impact | Mitigation |
+|------|------------|--------|------------|
+| | | | |
+
+### Solution B Risks
+
+| Risk | Likelihood | Impact | Mitigation |
+|------|------------|--------|------------|
+| | | | |
+
+---
+
+## 5. Scenario-Based Suggestions
+
+| If You Are... | Recommended | Reason |
+|---------------|-------------|--------|
+| [Scenario 1] | Solution A | |
+| [Scenario 2] | Solution B | |
+| [Scenario 3] | Solution C | |
+
+---
+
+## 6. Final Suggestions
+
+### 6.1 Recommended Solution
+
+**Recommended**: [Solution Name]
+
+### 6.2 Recommendation Reasons
+
+1. [Reason 1]
+2. [Reason 2]
+3. [Reason 3]
+
+### 6.3 Prerequisites
+
+This suggestion is based on the following assumptions:
+- [Assumption 1]
+- [Assumption 2]
+
+### 6.4 Next Steps
+
+1. [Action 1]
+2. [Action 2]
+
+---
+
+## References
+
+[Same as above]
+```
+
+---
+
+## III. Quick Report Template (Simplified)
+
+Applicable for time-constrained or relatively simple questions.
+
+```markdown
+# [Topic] Research Brief
+
+## Core Conclusion
+
+[One-sentence conclusion]
+
+## Key Findings
+
+1. **[Finding 1]**: [Explanation] ([Source])
+2. **[Finding 2]**: [Explanation] ([Source])
+3. **[Finding 3]**: [Explanation] ([Source])
+
+## Main Differences/Points
+
+| Dimension | Conclusion |
+|-----------|------------|
+| | |
+| | |
+| | |
+
+## Suggestions
+
+- [Suggestion 1]
+- [Suggestion 2]
+
+## References
+
+- [Source 1](Link)
+- [Source 2](Link)
+```
+
+---
+
+## Delivery Checklist
+
+Before completing the report, confirm the following items:
+
+- [ ] **Abstract Relayable**: One-line summary clear, boss can relay
+- [ ] **Conclusions Supported**: Each core conclusion has fact card support
+- [ ] **Sources Traceable**: Key citations all have links
+- [ ] **Clear Structure**: Divided with subheadings, can quickly locate
+- [ ] **Uncertainty Marked**: Speculative conclusions marked
+- [ ] **Use Cases Grounded**: At least one actual scenario verification
+- [ ] **Consistent Format**: Tables, lists, heading styles unified
diff --git a/skills/skill-creator/LICENSE.txt b/skills/skill-creator/LICENSE.txt
new file mode 100644
index 0000000..7a4a3ea
--- /dev/null
+++ b/skills/skill-creator/LICENSE.txt
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
\ No newline at end of file
diff --git a/skills/skill-creator/SKILL.md b/skills/skill-creator/SKILL.md
new file mode 100644
index 0000000..1589797
--- /dev/null
+++ b/skills/skill-creator/SKILL.md
@@ -0,0 +1,357 @@
+---
+name: skill-creator
+description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
+license: Complete terms in LICENSE.txt
+---
+
+# Skill Creator
+
+This skill provides guidance for creating effective skills.
+
+## About Skills
+
+Skills are modular, self-contained packages that extend Claude's capabilities by providing
+specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific
+domains or tasks—they transform Claude from a general-purpose agent into a specialized agent
+equipped with procedural knowledge that no model can fully possess.
+
+### What Skills Provide
+
+1. Specialized workflows - Multi-step procedures for specific domains
+2. Tool integrations - Instructions for working with specific file formats or APIs
+3. Domain expertise - Company-specific knowledge, schemas, business logic
+4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
+
+## Core Principles
+
+### Concise is Key
+
+The context window is a public good. Skills share the context window with everything else Claude needs: system prompt, conversation history, other Skills' metadata, and the actual user request.
+
+**Default assumption: Claude is already very smart.** Only add context Claude doesn't already have. Challenge each piece of information: "Does Claude really need this explanation?" and "Does this paragraph justify its token cost?"
+
+Prefer concise examples over verbose explanations.
+
+### Set Appropriate Degrees of Freedom
+
+Match the level of specificity to the task's fragility and variability:
+
+**High freedom (text-based instructions)**: Use when multiple approaches are valid, decisions depend on context, or heuristics guide the approach.
+
+**Medium freedom (pseudocode or scripts with parameters)**: Use when a preferred pattern exists, some variation is acceptable, or configuration affects behavior.
+
+**Low freedom (specific scripts, few parameters)**: Use when operations are fragile and error-prone, consistency is critical, or a specific sequence must be followed.
+
+Think of Claude as exploring a path: a narrow bridge with cliffs needs specific guardrails (low freedom), while an open field allows many routes (high freedom).
+
+### Anatomy of a Skill
+
+Every skill consists of a required SKILL.md file and optional bundled resources:
+
+```
+skill-name/
+├── SKILL.md (required)
+│ ├── YAML frontmatter metadata (required)
+│ │ ├── name: (required)
+│ │ ├── description: (required)
+│ │ └── compatibility: (optional, rarely needed)
+│ └── Markdown instructions (required)
+└── Bundled Resources (optional)
+ ├── scripts/ - Executable code (Python/Bash/etc.)
+ ├── references/ - Documentation intended to be loaded into context as needed
+ └── assets/ - Files used in output (templates, icons, fonts, etc.)
+```
+
+#### SKILL.md (required)
+
+Every SKILL.md consists of:
+
+- **Frontmatter** (YAML): Contains `name` and `description` fields (required), plus optional fields like `license`, `metadata`, and `compatibility`. Only `name` and `description` are read by Claude to determine when the skill triggers, so be clear and comprehensive about what the skill is and when it should be used. The `compatibility` field is for noting environment requirements (target product, system packages, etc.) but most skills don't need it.
+- **Body** (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers (if at all).
+
+#### Bundled Resources (optional)
+
+##### Scripts (`scripts/`)
+
+Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.
+
+- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed
+- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks
+- **Benefits**: Token efficient, deterministic, may be executed without loading into context
+- **Note**: Scripts may still need to be read by Claude for patching or environment-specific adjustments
+
+##### References (`references/`)
+
+Documentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.
+
+- **When to include**: For documentation that Claude should reference while working
+- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications
+- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides
+- **Benefits**: Keeps SKILL.md lean, loaded only when Claude determines it's needed
+- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md
+- **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skill—this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files.
+
+##### Assets (`assets/`)
+
+Files not intended to be loaded into context, but rather used within the output Claude produces.
+
+- **When to include**: When the skill needs files that will be used in the final output
+- **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `assets/frontend-template/` for HTML/React boilerplate, `assets/font.ttf` for typography
+- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents that get copied or modified
+- **Benefits**: Separates output resources from documentation, enables Claude to use files without loading them into context
+
+#### What to Not Include in a Skill
+
+A skill should only contain essential files that directly support its functionality. Do NOT create extraneous documentation or auxiliary files, including:
+
+- README.md
+- INSTALLATION_GUIDE.md
+- QUICK_REFERENCE.md
+- CHANGELOG.md
+- etc.
+
+The skill should only contain the information needed for an AI agent to do the job at hand. It should not contain auxilary context about the process that went into creating it, setup and testing procedures, user-facing documentation, etc. Creating additional documentation files just adds clutter and confusion.
+
+### Progressive Disclosure Design Principle
+
+Skills use a three-level loading system to manage context efficiently:
+
+1. **Metadata (name + description)** - Always in context (~100 words)
+2. **SKILL.md body** - When skill triggers (<5k words)
+3. **Bundled resources** - As needed by Claude (Unlimited because scripts can be executed without reading into context window)
+
+#### Progressive Disclosure Patterns
+
+Keep SKILL.md body to the essentials and under 500 lines to minimize context bloat. Split content into separate files when approaching this limit. When splitting out content into other files, it is very important to reference them from SKILL.md and describe clearly when to read them, to ensure the reader of the skill knows they exist and when to use them.
+
+**Key principle:** When a skill supports multiple variations, frameworks, or options, keep only the core workflow and selection guidance in SKILL.md. Move variant-specific details (patterns, examples, configuration) into separate reference files.
+
+**Pattern 1: High-level guide with references**
+
+```markdown
+# PDF Processing
+
+## Quick start
+
+Extract text with pdfplumber:
+[code example]
+
+## Advanced features
+
+- **Form filling**: See [FORMS.md](FORMS.md) for complete guide
+- **API reference**: See [REFERENCE.md](REFERENCE.md) for all methods
+- **Examples**: See [EXAMPLES.md](EXAMPLES.md) for common patterns
+```
+
+Claude loads FORMS.md, REFERENCE.md, or EXAMPLES.md only when needed.
+
+**Pattern 2: Domain-specific organization**
+
+For Skills with multiple domains, organize content by domain to avoid loading irrelevant context:
+
+```
+bigquery-skill/
+├── SKILL.md (overview and navigation)
+└── reference/
+ ├── finance.md (revenue, billing metrics)
+ ├── sales.md (opportunities, pipeline)
+ ├── product.md (API usage, features)
+ └── marketing.md (campaigns, attribution)
+```
+
+When a user asks about sales metrics, Claude only reads sales.md.
+
+Similarly, for skills supporting multiple frameworks or variants, organize by variant:
+
+```
+cloud-deploy/
+├── SKILL.md (workflow + provider selection)
+└── references/
+ ├── aws.md (AWS deployment patterns)
+ ├── gcp.md (GCP deployment patterns)
+ └── azure.md (Azure deployment patterns)
+```
+
+When the user chooses AWS, Claude only reads aws.md.
+
+**Pattern 3: Conditional details**
+
+Show basic content, link to advanced content:
+
+```markdown
+# DOCX Processing
+
+## Creating documents
+
+Use docx-js for new documents. See [DOCX-JS.md](DOCX-JS.md).
+
+## Editing documents
+
+For simple edits, modify the XML directly.
+
+**For tracked changes**: See [REDLINING.md](REDLINING.md)
+**For OOXML details**: See [OOXML.md](OOXML.md)
+```
+
+Claude reads REDLINING.md or OOXML.md only when the user needs those features.
+
+**Important guidelines:**
+
+- **Avoid deeply nested references** - Keep references one level deep from SKILL.md. All reference files should link directly from SKILL.md.
+- **Structure longer reference files** - For files longer than 100 lines, include a table of contents at the top so Claude can see the full scope when previewing.
+
+## Skill Creation Process
+
+Skill creation involves these steps:
+
+1. Understand the skill with concrete examples
+2. Plan reusable skill contents (scripts, references, assets)
+3. Initialize the skill (run init_skill.py)
+4. Edit the skill (implement resources and write SKILL.md)
+5. Package the skill (run package_skill.py)
+6. Iterate based on real usage
+
+Follow these steps in order, skipping only if there is a clear reason why they are not applicable.
+
+### Step 1: Understanding the Skill with Concrete Examples
+
+Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.
+
+To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.
+
+For example, when building an image-editor skill, relevant questions include:
+
+- "What functionality should the image-editor skill support? Editing, rotating, anything else?"
+- "Can you give some examples of how this skill would be used?"
+- "I can imagine users asking for things like 'Remove the red-eye from this image' or 'Rotate this image'. Are there other ways you imagine this skill being used?"
+- "What would a user say that should trigger this skill?"
+
+To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.
+
+Conclude this step when there is a clear sense of the functionality the skill should support.
+
+### Step 2: Planning the Reusable Skill Contents
+
+To turn concrete examples into an effective skill, analyze each example by:
+
+1. Considering how to execute on the example from scratch
+2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly
+
+Example: When building a `pdf-editor` skill to handle queries like "Help me rotate this PDF," the analysis shows:
+
+1. Rotating a PDF requires re-writing the same code each time
+2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill
+
+Example: When designing a `frontend-webapp-builder` skill for queries like "Build me a todo app" or "Build me a dashboard to track my steps," the analysis shows:
+
+1. Writing a frontend webapp requires the same boilerplate HTML/React each time
+2. An `assets/hello-world/` template containing the boilerplate HTML/React project files would be helpful to store in the skill
+
+Example: When building a `big-query` skill to handle queries like "How many users have logged in today?" the analysis shows:
+
+1. Querying BigQuery requires re-discovering the table schemas and relationships each time
+2. A `references/schema.md` file documenting the table schemas would be helpful to store in the skill
+
+To establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.
+
+### Step 3: Initializing the Skill
+
+At this point, it is time to actually create the skill.
+
+Skip this step only if the skill being developed already exists, and iteration or packaging is needed. In this case, continue to the next step.
+
+When creating a new skill from scratch, always run the `init_skill.py` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable.
+
+Usage:
+
+```bash
+scripts/init_skill.py <skill-name> --path <output-directory>
+```
+
+The script:
+
+- Creates the skill directory at the specified path
+- Generates a SKILL.md template with proper frontmatter and TODO placeholders
+- Creates example resource directories: `scripts/`, `references/`, and `assets/`
+- Adds example files in each directory that can be customized or deleted
+
+After initialization, customize or remove the generated SKILL.md and example files as needed.
+
+### Step 4: Edit the Skill
+
+When editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Claude to use. Include information that would be beneficial and non-obvious to Claude. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Claude instance execute these tasks more effectively.
+
+#### Learn Proven Design Patterns
+
+Consult these helpful guides based on your skill's needs:
+
+- **Multi-step processes**: See references/workflows.md for sequential workflows and conditional logic
+- **Specific output formats or quality standards**: See references/output-patterns.md for template and example patterns
+
+These files contain established best practices for effective skill design.
+
+#### Start with Reusable Skill Contents
+
+To begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines` skill, the user may need to provide brand assets or templates to store in `assets/`, or documentation to store in `references/`.
+
+Added scripts must be tested by actually running them to ensure there are no bugs and that the output matches what is expected. If there are many similar scripts, only a representative sample needs to be tested to ensure confidence that they all work while balancing time to completion.
+
+Any example files and directories not needed for the skill should be deleted. The initialization script creates example files in `scripts/`, `references/`, and `assets/` to demonstrate structure, but most skills won't need all of them.
+
+#### Update SKILL.md
+
+**Writing Guidelines:** Always use imperative/infinitive form.
+
+##### Frontmatter
+
+Write the YAML frontmatter with `name` and `description`:
+
+- `name`: The skill name
+- `description`: This is the primary triggering mechanism for your skill, and helps Claude understand when to use the skill.
+ - Include both what the Skill does and specific triggers/contexts for when to use it.
+ - Include all "when to use" information here - Not in the body. The body is only loaded after triggering, so "When to Use This Skill" sections in the body are not helpful to Claude.
+ - Example description for a `docx` skill: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. Use when Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
+
+Do not include any other fields in YAML frontmatter.
+
+##### Body
+
+Write instructions for using the skill and its bundled resources.
+
+### Step 5: Packaging a Skill
+
+Once development of the skill is complete, it must be packaged into a distributable .skill file that gets shared with the user. The packaging process automatically validates the skill first to ensure it meets all requirements:
+
+```bash
+scripts/package_skill.py <path/to/skill-folder>
+```
+
+Optional output directory specification:
+
+```bash
+scripts/package_skill.py <path/to/skill-folder> ./dist
+```
+
+The packaging script will:
+
+1. **Validate** the skill automatically, checking:
+
+ - YAML frontmatter format and required fields
+ - Skill naming conventions and directory structure
+ - Description completeness and quality
+ - File organization and resource references
+
+2. **Package** the skill if validation passes, creating a .skill file named after the skill (e.g., `my-skill.skill`) that includes all files and maintains the proper directory structure for distribution. The .skill file is a zip file with a .skill extension.
+
+If validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again.
+
+### Step 6: Iterate
+
+After testing the skill, users may request improvements. Often this happens right after using the skill, with fresh context of how the skill performed.
+
+**Iteration workflow:**
+
+1. Use the skill on real tasks
+2. Notice struggles or inefficiencies
+3. Identify how SKILL.md or bundled resources should be updated
+4. Implement changes and test again
diff --git a/skills/skill-creator/references/output-patterns.md b/skills/skill-creator/references/output-patterns.md
new file mode 100644
index 0000000..073ddda
--- /dev/null
+++ b/skills/skill-creator/references/output-patterns.md
@@ -0,0 +1,82 @@
+# Output Patterns
+
+Use these patterns when skills need to produce consistent, high-quality output.
+
+## Template Pattern
+
+Provide templates for output format. Match the level of strictness to your needs.
+
+**For strict requirements (like API responses or data formats):**
+
+```markdown
+## Report structure
+
+ALWAYS use this exact template structure:
+
+# [Analysis Title]
+
+## Executive summary
+[One-paragraph overview of key findings]
+
+## Key findings
+- Finding 1 with supporting data
+- Finding 2 with supporting data
+- Finding 3 with supporting data
+
+## Recommendations
+1. Specific actionable recommendation
+2. Specific actionable recommendation
+```
+
+**For flexible guidance (when adaptation is useful):**
+
+```markdown
+## Report structure
+
+Here is a sensible default format, but use your best judgment:
+
+# [Analysis Title]
+
+## Executive summary
+[Overview]
+
+## Key findings
+[Adapt sections based on what you discover]
+
+## Recommendations
+[Tailor to the specific context]
+
+Adjust sections as needed for the specific analysis type.
+```
+
+## Examples Pattern
+
+For skills where output quality depends on seeing examples, provide input/output pairs:
+
+```markdown
+## Commit message format
+
+Generate commit messages following these examples:
+
+**Example 1:**
+Input: Added user authentication with JWT tokens
+Output:
+```
+feat(auth): implement JWT-based authentication
+
+Add login endpoint and token validation middleware
+```
+
+**Example 2:**
+Input: Fixed bug where dates displayed incorrectly in reports
+Output:
+```
+fix(reports): correct date formatting in timezone conversion
+
+Use UTC timestamps consistently across report generation
+```
+
+Follow this style: type(scope): brief description, then detailed explanation.
+```
+
+Examples help Claude understand the desired style and level of detail more clearly than descriptions alone.
diff --git a/skills/skill-creator/references/workflows.md b/skills/skill-creator/references/workflows.md
new file mode 100644
index 0000000..a350c3c
--- /dev/null
+++ b/skills/skill-creator/references/workflows.md
@@ -0,0 +1,28 @@
+# Workflow Patterns
+
+## Sequential Workflows
+
+For complex tasks, break operations into clear, sequential steps. It is often helpful to give Claude an overview of the process towards the beginning of SKILL.md:
+
+```markdown
+Filling a PDF form involves these steps:
+
+1. Analyze the form (run analyze_form.py)
+2. Create field mapping (edit fields.json)
+3. Validate mapping (run validate_fields.py)
+4. Fill the form (run fill_form.py)
+5. Verify output (run verify_output.py)
+```
+
+## Conditional Workflows
+
+For tasks with branching logic, guide Claude through decision points:
+
+```markdown
+1. Determine the modification type:
+ **Creating new content?** → Follow "Creation workflow" below
+ **Editing existing content?** → Follow "Editing workflow" below
+
+2. Creation workflow: [steps]
+3. Editing workflow: [steps]
+```
\ No newline at end of file
diff --git a/skills/skill-creator/scripts/init_skill.py b/skills/skill-creator/scripts/init_skill.py
new file mode 100755
index 0000000..c544fc7
--- /dev/null
+++ b/skills/skill-creator/scripts/init_skill.py
@@ -0,0 +1,303 @@
+#!/usr/bin/env python3
+"""
+Skill Initializer - Creates a new skill from template
+
+Usage:
+ init_skill.py <skill-name> --path <path>
+
+Examples:
+ init_skill.py my-new-skill --path skills/public
+ init_skill.py my-api-helper --path skills/private
+ init_skill.py custom-skill --path /custom/location
+"""
+
+import sys
+from pathlib import Path
+
+
+SKILL_TEMPLATE = """---
+name: {skill_name}
+description: [TODO: Complete and informative explanation of what the skill does and when to use it. Include WHEN to use this skill - specific scenarios, file types, or tasks that trigger it.]
+---
+
+# {skill_title}
+
+## Overview
+
+[TODO: 1-2 sentences explaining what this skill enables]
+
+## Structuring This Skill
+
+[TODO: Choose the structure that best fits this skill's purpose. Common patterns:
+
+**1. Workflow-Based** (best for sequential processes)
+- Works well when there are clear step-by-step procedures
+- Example: DOCX skill with "Workflow Decision Tree" → "Reading" → "Creating" → "Editing"
+- Structure: ## Overview → ## Workflow Decision Tree → ## Step 1 → ## Step 2...
+
+**2. Task-Based** (best for tool collections)
+- Works well when the skill offers different operations/capabilities
+- Example: PDF skill with "Quick Start" → "Merge PDFs" → "Split PDFs" → "Extract Text"
+- Structure: ## Overview → ## Quick Start → ## Task Category 1 → ## Task Category 2...
+
+**3. Reference/Guidelines** (best for standards or specifications)
+- Works well for brand guidelines, coding standards, or requirements
+- Example: Brand styling with "Brand Guidelines" → "Colors" → "Typography" → "Features"
+- Structure: ## Overview → ## Guidelines → ## Specifications → ## Usage...
+
+**4. Capabilities-Based** (best for integrated systems)
+- Works well when the skill provides multiple interrelated features
+- Example: Product Management with "Core Capabilities" → numbered capability list
+- Structure: ## Overview → ## Core Capabilities → ### 1. Feature → ### 2. Feature...
+
+Patterns can be mixed and matched as needed. Most skills combine patterns (e.g., start with task-based, add workflow for complex operations).
+
+Delete this entire "Structuring This Skill" section when done - it's just guidance.]
+
+## [TODO: Replace with the first main section based on chosen structure]
+
+[TODO: Add content here. See examples in existing skills:
+- Code samples for technical skills
+- Decision trees for complex workflows
+- Concrete examples with realistic user requests
+- References to scripts/templates/references as needed]
+
+## Resources
+
+This skill includes example resource directories that demonstrate how to organize different types of bundled resources:
+
+### scripts/
+Executable code (Python/Bash/etc.) that can be run directly to perform specific operations.
+
+**Examples from other skills:**
+- PDF skill: `fill_fillable_fields.py`, `extract_form_field_info.py` - utilities for PDF manipulation
+- DOCX skill: `document.py`, `utilities.py` - Python modules for document processing
+
+**Appropriate for:** Python scripts, shell scripts, or any executable code that performs automation, data processing, or specific operations.
+
+**Note:** Scripts may be executed without loading into context, but can still be read by Claude for patching or environment adjustments.
+
+### references/
+Documentation and reference material intended to be loaded into context to inform Claude's process and thinking.
+
+**Examples from other skills:**
+- Product management: `communication.md`, `context_building.md` - detailed workflow guides
+- BigQuery: API reference documentation and query examples
+- Finance: Schema documentation, company policies
+
+**Appropriate for:** In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Claude should reference while working.
+
+### assets/
+Files not intended to be loaded into context, but rather used within the output Claude produces.
+
+**Examples from other skills:**
+- Brand styling: PowerPoint template files (.pptx), logo files
+- Frontend builder: HTML/React boilerplate project directories
+- Typography: Font files (.ttf, .woff2)
+
+**Appropriate for:** Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.
+
+---
+
+**Any unneeded directories can be deleted.** Not every skill requires all three types of resources.
+"""
+
+EXAMPLE_SCRIPT = '''#!/usr/bin/env python3
+"""
+Example helper script for {skill_name}
+
+This is a placeholder script that can be executed directly.
+Replace with actual implementation or delete if not needed.
+
+Example real scripts from other skills:
+- pdf/scripts/fill_fillable_fields.py - Fills PDF form fields
+- pdf/scripts/convert_pdf_to_images.py - Converts PDF pages to images
+"""
+
+def main():
+ print("This is an example script for {skill_name}")
+ # TODO: Add actual script logic here
+ # This could be data processing, file conversion, API calls, etc.
+
+if __name__ == "__main__":
+ main()
+'''
+
+EXAMPLE_REFERENCE = """# Reference Documentation for {skill_title}
+
+This is a placeholder for detailed reference documentation.
+Replace with actual reference content or delete if not needed.
+
+Example real reference docs from other skills:
+- product-management/references/communication.md - Comprehensive guide for status updates
+- product-management/references/context_building.md - Deep-dive on gathering context
+- bigquery/references/ - API references and query examples
+
+## When Reference Docs Are Useful
+
+Reference docs are ideal for:
+- Comprehensive API documentation
+- Detailed workflow guides
+- Complex multi-step processes
+- Information too lengthy for main SKILL.md
+- Content that's only needed for specific use cases
+
+## Structure Suggestions
+
+### API Reference Example
+- Overview
+- Authentication
+- Endpoints with examples
+- Error codes
+- Rate limits
+
+### Workflow Guide Example
+- Prerequisites
+- Step-by-step instructions
+- Common patterns
+- Troubleshooting
+- Best practices
+"""
+
+EXAMPLE_ASSET = """# Example Asset File
+
+This placeholder represents where asset files would be stored.
+Replace with actual asset files (templates, images, fonts, etc.) or delete if not needed.
+
+Asset files are NOT intended to be loaded into context, but rather used within
+the output Claude produces.
+
+Example asset files from other skills:
+- Brand guidelines: logo.png, slides_template.pptx
+- Frontend builder: hello-world/ directory with HTML/React boilerplate
+- Typography: custom-font.ttf, font-family.woff2
+- Data: sample_data.csv, test_dataset.json
+
+## Common Asset Types
+
+- Templates: .pptx, .docx, boilerplate directories
+- Images: .png, .jpg, .svg, .gif
+- Fonts: .ttf, .otf, .woff, .woff2
+- Boilerplate code: Project directories, starter files
+- Icons: .ico, .svg
+- Data files: .csv, .json, .xml, .yaml
+
+Note: This is a text placeholder. Actual assets can be any file type.
+"""
+
+
+def title_case_skill_name(skill_name):
+ """Convert hyphenated skill name to Title Case for display."""
+ return ' '.join(word.capitalize() for word in skill_name.split('-'))
+
+
+def init_skill(skill_name, path):
+ """
+ Initialize a new skill directory with template SKILL.md.
+
+ Args:
+ skill_name: Name of the skill
+ path: Path where the skill directory should be created
+
+ Returns:
+ Path to created skill directory, or None if error
+ """
+ # Determine skill directory path
+ skill_dir = Path(path).resolve() / skill_name
+
+ # Check if directory already exists
+ if skill_dir.exists():
+ print(f"❌ Error: Skill directory already exists: {skill_dir}")
+ return None
+
+ # Create skill directory
+ try:
+ skill_dir.mkdir(parents=True, exist_ok=False)
+ print(f"✅ Created skill directory: {skill_dir}")
+ except Exception as e:
+ print(f"❌ Error creating directory: {e}")
+ return None
+
+ # Create SKILL.md from template
+ skill_title = title_case_skill_name(skill_name)
+ skill_content = SKILL_TEMPLATE.format(
+ skill_name=skill_name,
+ skill_title=skill_title
+ )
+
+ skill_md_path = skill_dir / 'SKILL.md'
+ try:
+ skill_md_path.write_text(skill_content)
+ print("✅ Created SKILL.md")
+ except Exception as e:
+ print(f"❌ Error creating SKILL.md: {e}")
+ return None
+
+ # Create resource directories with example files
+ try:
+ # Create scripts/ directory with example script
+ scripts_dir = skill_dir / 'scripts'
+ scripts_dir.mkdir(exist_ok=True)
+ example_script = scripts_dir / 'example.py'
+ example_script.write_text(EXAMPLE_SCRIPT.format(skill_name=skill_name))
+ example_script.chmod(0o755)
+ print("✅ Created scripts/example.py")
+
+ # Create references/ directory with example reference doc
+ references_dir = skill_dir / 'references'
+ references_dir.mkdir(exist_ok=True)
+ example_reference = references_dir / 'api_reference.md'
+ example_reference.write_text(EXAMPLE_REFERENCE.format(skill_title=skill_title))
+ print("✅ Created references/api_reference.md")
+
+ # Create assets/ directory with example asset placeholder
+ assets_dir = skill_dir / 'assets'
+ assets_dir.mkdir(exist_ok=True)
+ example_asset = assets_dir / 'example_asset.txt'
+ example_asset.write_text(EXAMPLE_ASSET)
+ print("✅ Created assets/example_asset.txt")
+ except Exception as e:
+ print(f"❌ Error creating resource directories: {e}")
+ return None
+
+ # Print next steps
+ print(f"\n✅ Skill '{skill_name}' initialized successfully at {skill_dir}")
+ print("\nNext steps:")
+ print("1. Edit SKILL.md to complete the TODO items and update the description")
+ print("2. Customize or delete the example files in scripts/, references/, and assets/")
+ print("3. Run the validator when ready to check the skill structure")
+
+ return skill_dir
+
+
+def main():
+ if len(sys.argv) < 4 or sys.argv[2] != '--path':
+ print("Usage: init_skill.py <skill-name> --path <path>")
+ print("\nSkill name requirements:")
+ print(" - Kebab-case identifier (e.g., 'my-data-analyzer')")
+ print(" - Lowercase letters, digits, and hyphens only")
+ print(" - Max 64 characters")
+ print(" - Must match directory name exactly")
+ print("\nExamples:")
+ print(" init_skill.py my-new-skill --path skills/public")
+ print(" init_skill.py my-api-helper --path skills/private")
+ print(" init_skill.py custom-skill --path /custom/location")
+ sys.exit(1)
+
+ skill_name = sys.argv[1]
+ path = sys.argv[3]
+
+ print(f"🚀 Initializing skill: {skill_name}")
+ print(f" Location: {path}")
+ print()
+
+ result = init_skill(skill_name, path)
+
+ if result:
+ sys.exit(0)
+ else:
+ sys.exit(1)
+
+
+if __name__ == "__main__":
+ main()
diff --git a/skills/skill-creator/scripts/package_skill.py b/skills/skill-creator/scripts/package_skill.py
new file mode 100755
index 0000000..5cd36cb
--- /dev/null
+++ b/skills/skill-creator/scripts/package_skill.py
@@ -0,0 +1,110 @@
+#!/usr/bin/env python3
+"""
+Skill Packager - Creates a distributable .skill file of a skill folder
+
+Usage:
+ python utils/package_skill.py <path/to/skill-folder> [output-directory]
+
+Example:
+ python utils/package_skill.py skills/public/my-skill
+ python utils/package_skill.py skills/public/my-skill ./dist
+"""
+
+import sys
+import zipfile
+from pathlib import Path
+from quick_validate import validate_skill
+
+
+def package_skill(skill_path, output_dir=None):
+ """
+ Package a skill folder into a .skill file.
+
+ Args:
+ skill_path: Path to the skill folder
+ output_dir: Optional output directory for the .skill file (defaults to current directory)
+
+ Returns:
+ Path to the created .skill file, or None if error
+ """
+ skill_path = Path(skill_path).resolve()
+
+ # Validate skill folder exists
+ if not skill_path.exists():
+ print(f"❌ Error: Skill folder not found: {skill_path}")
+ return None
+
+ if not skill_path.is_dir():
+ print(f"❌ Error: Path is not a directory: {skill_path}")
+ return None
+
+ # Validate SKILL.md exists
+ skill_md = skill_path / "SKILL.md"
+ if not skill_md.exists():
+ print(f"❌ Error: SKILL.md not found in {skill_path}")
+ return None
+
+ # Run validation before packaging
+ print("🔍 Validating skill...")
+ valid, message = validate_skill(skill_path)
+ if not valid:
+ print(f"❌ Validation failed: {message}")
+ print(" Please fix the validation errors before packaging.")
+ return None
+ print(f"✅ {message}\n")
+
+ # Determine output location
+ skill_name = skill_path.name
+ if output_dir:
+ output_path = Path(output_dir).resolve()
+ output_path.mkdir(parents=True, exist_ok=True)
+ else:
+ output_path = Path.cwd()
+
+ skill_filename = output_path / f"{skill_name}.skill"
+
+ # Create the .skill file (zip format)
+ try:
+ with zipfile.ZipFile(skill_filename, 'w', zipfile.ZIP_DEFLATED) as zipf:
+ # Walk through the skill directory
+ for file_path in skill_path.rglob('*'):
+ if file_path.is_file():
+ # Calculate the relative path within the zip
+ arcname = file_path.relative_to(skill_path.parent)
+ zipf.write(file_path, arcname)
+ print(f" Added: {arcname}")
+
+ print(f"\n✅ Successfully packaged skill to: {skill_filename}")
+ return skill_filename
+
+ except Exception as e:
+ print(f"❌ Error creating .skill file: {e}")
+ return None
+
+
+def main():
+ if len(sys.argv) < 2:
+ print("Usage: python utils/package_skill.py <path/to/skill-folder> [output-directory]")
+ print("\nExample:")
+ print(" python utils/package_skill.py skills/public/my-skill")
+ print(" python utils/package_skill.py skills/public/my-skill ./dist")
+ sys.exit(1)
+
+ skill_path = sys.argv[1]
+ output_dir = sys.argv[2] if len(sys.argv) > 2 else None
+
+ print(f"📦 Packaging skill: {skill_path}")
+ if output_dir:
+ print(f" Output directory: {output_dir}")
+ print()
+
+ result = package_skill(skill_path, output_dir)
+
+ if result:
+ sys.exit(0)
+ else:
+ sys.exit(1)
+
+
+if __name__ == "__main__":
+ main()
diff --git a/skills/skill-creator/scripts/quick_validate.py b/skills/skill-creator/scripts/quick_validate.py
new file mode 100755
index 0000000..ed8e1dd
--- /dev/null
+++ b/skills/skill-creator/scripts/quick_validate.py
@@ -0,0 +1,103 @@
+#!/usr/bin/env python3
+"""
+Quick validation script for skills - minimal version
+"""
+
+import sys
+import os
+import re
+import yaml
+from pathlib import Path
+
+def validate_skill(skill_path):
+ """Basic validation of a skill"""
+ skill_path = Path(skill_path)
+
+ # Check SKILL.md exists
+ skill_md = skill_path / 'SKILL.md'
+ if not skill_md.exists():
+ return False, "SKILL.md not found"
+
+ # Read and validate frontmatter
+ content = skill_md.read_text()
+ if not content.startswith('---'):
+ return False, "No YAML frontmatter found"
+
+ # Extract frontmatter
+ match = re.match(r'^---\n(.*?)\n---', content, re.DOTALL)
+ if not match:
+ return False, "Invalid frontmatter format"
+
+ frontmatter_text = match.group(1)
+
+ # Parse YAML frontmatter
+ try:
+ frontmatter = yaml.safe_load(frontmatter_text)
+ if not isinstance(frontmatter, dict):
+ return False, "Frontmatter must be a YAML dictionary"
+ except yaml.YAMLError as e:
+ return False, f"Invalid YAML in frontmatter: {e}"
+
+ # Define allowed properties
+ ALLOWED_PROPERTIES = {'name', 'description', 'license', 'allowed-tools', 'metadata', 'compatibility'}
+
+ # Check for unexpected properties (excluding nested keys under metadata)
+ unexpected_keys = set(frontmatter.keys()) - ALLOWED_PROPERTIES
+ if unexpected_keys:
+ return False, (
+ f"Unexpected key(s) in SKILL.md frontmatter: {', '.join(sorted(unexpected_keys))}. "
+ f"Allowed properties are: {', '.join(sorted(ALLOWED_PROPERTIES))}"
+ )
+
+ # Check required fields
+ if 'name' not in frontmatter:
+ return False, "Missing 'name' in frontmatter"
+ if 'description' not in frontmatter:
+ return False, "Missing 'description' in frontmatter"
+
+ # Extract name for validation
+ name = frontmatter.get('name', '')
+ if not isinstance(name, str):
+ return False, f"Name must be a string, got {type(name).__name__}"
+ name = name.strip()
+ if name:
+ # Check naming convention (kebab-case: lowercase with hyphens)
+ if not re.match(r'^[a-z0-9-]+$', name):
+ return False, f"Name '{name}' should be kebab-case (lowercase letters, digits, and hyphens only)"
+ if name.startswith('-') or name.endswith('-') or '--' in name:
+ return False, f"Name '{name}' cannot start/end with hyphen or contain consecutive hyphens"
+ # Check name length (max 64 characters per spec)
+ if len(name) > 64:
+ return False, f"Name is too long ({len(name)} characters). Maximum is 64 characters."
+
+ # Extract and validate description
+ description = frontmatter.get('description', '')
+ if not isinstance(description, str):
+ return False, f"Description must be a string, got {type(description).__name__}"
+ description = description.strip()
+ if description:
+ # Check for angle brackets
+ if '<' in description or '>' in description:
+ return False, "Description cannot contain angle brackets (< or >)"
+ # Check description length (max 1024 characters per spec)
+ if len(description) > 1024:
+ return False, f"Description is too long ({len(description)} characters). Maximum is 1024 characters."
+
+ # Validate compatibility field if present (optional)
+ compatibility = frontmatter.get('compatibility', '')
+ if compatibility:
+ if not isinstance(compatibility, str):
+ return False, f"Compatibility must be a string, got {type(compatibility).__name__}"
+ if len(compatibility) > 500:
+ return False, f"Compatibility is too long ({len(compatibility)} characters). Maximum is 500 characters."
+
+ return True, "Skill is valid!"
+
+if __name__ == "__main__":
+ if len(sys.argv) != 2:
+ print("Usage: python quick_validate.py <skill_directory>")
+ sys.exit(1)
+
+ valid, message = validate_skill(sys.argv[1])
+ print(message)
+ sys.exit(0 if valid else 1)
\ No newline at end of file