aiskillstore/marketplace / skills/aaronabuusama/create-skill
create-skill
VerifiedGuide for creating new skills in Kai's personal AI infrastructure. Use when user wants to create, update, or structure a new skill that extends capabilities with specialized knowledge, workflows, or tool integrations. Follows both Anthropic skill standards and PAI-specific patterns.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.3 KB |
| skill-report.json | config | 22.8 KB |
| templates/CLAUDE-template.md | markdown | 5.8 KB |
| templates/README.md | markdown | 4.6 KB |
| templates/complex-skill-template.md | markdown | 2.1 KB |
| templates/simple-skill-template.md | markdown | 1.5 KB |
| templates/skill-with-agents-template.md | markdown | 5.2 KB |
| workflows/create-new.md | markdown | 1.2 KB |
| workflows/update-existing.md | markdown | 1.1 KB |
templates/CLAUDE-template.md
View on GitHub# Skill Name - Comprehensive Guide
## π― PURPOSE: [HIGH-LEVEL GOAL IN CAPS]
**[Value proposition - what this skill enables and why it matters]**
This guide covers:
- [Major topic 1]
- [Major topic 2]
- [Major topic 3]
- [Major topic 4]
## π WHAT IS [MAIN CONCEPT]?
### Definition
[Detailed explanation of the core concept, capability, or methodology]
### Key Concepts
- **Concept 1**: Detailed explanation
- **Concept 2**: Detailed explanation
- **Concept 3**: Detailed explanation
### [Main Approach] vs [Alternative Approach]
**The Problem [Alternative] Solves:**
- Problem 1
- Problem 2
- Problem 3
**Why [Main Approach] Is Different:**
- β
Advantage 1 with explanation
- β
Advantage 2 with explanation
- β
Advantage 3 with explanation
- β
Advantage 4 with explanation
**[Alternative] documentation when you have [better method] = [problem statement].**
## ποΈ ARCHITECTURE / METHODOLOGY
### Overall Framework
[Detailed explanation of the methodology or architecture]
### Core Components
**Component 1:**
- Purpose
- How it works
- When to use
- Integration points
**Component 2:**
[Same structure]
### System Diagram / Workflow Overview
```
[ASCII diagram or structured breakdown of system]
```
## π THE [MAIN WORKFLOW NAME]
**[Brief description of the workflow approach]**
### Phase 0: [Setup/Foundation]
**Command:** `/command-name` (if applicable)
[Detailed instructions for this phase]
**Objectives:**
- Objective 1
- Objective 2
- Objective 3
**Output:**
- Output file 1 - Description
- Output file 2 - Description
- Automatically captured to [location]
**Notes:** [Important notes about this phase]
### Phase 1: [Next Phase Name]
**Command:** `/command-name`
[Detailed instructions]
**Objectives:**
- Objective 1
- Objective 2
**Output:** [What gets created]
### Phase 2: [Next Phase Name]
[Continue for all phases]
**π Goal: [Summary of what the complete workflow achieves]**
## π§ OPTIONAL [ENHANCEMENT] COMMANDS
These enhance [aspect] throughout the process:
### `/command-name-1`
**When:** [When to use this command]
- Purpose and benefits
- What it does
- How it improves results
### `/command-name-2`
**When:** [When to use this command]
- Purpose and benefits
- What it does
- How it improves results
## π― BEST PRACTICES
### [Category 1]
- **Practice 1** - Detailed explanation with rationale
- **Practice 2** - Detailed explanation with rationale
- **Practice 3** - Detailed explanation with rationale
### [Category 2]
- **Practice 1** - Detailed explanation
- **Practice 2** - Detailed explanation
### [Category 3]
- **Practice 1** - Detailed explanation
- **Practice 2** - Detailed explanation
## π οΈ TECHNOLOGY STACK / TOOLS
### Core Technology
[Detailed description of primary technology]
**Key features:**
- Feature 1
- Feature 2
- Feature 3
### Supporting Tools
**Tool 1:**
- Purpose
- Integration
- Usage
**Tool 2:**
[Same structure]
### Configuration
[Standard configuration or setup instructions]
## π [ADDITIONAL MAJOR SECTION]
[Deep dive into important aspect]
### Subsection 1
[Detailed content]
### Subsection 2
[Detailed content]
## π€ [AGENTS / AUTOMATION] (if applicable)
### Agent 1 (Name)
**Training:** [Specialization]
**Voice:** [ID]
**Configuration:** `path`
**Parallel Execution:** [Capabilities]
**Responsibilities:**
- Phase 1: [What agent does]
- Phase 2: [What agent does]
[Continue for each agent]
### Agent Collaboration Protocol
[How agents work together]
**Workflow Handoff:**
1. Agent 1 completes [work]
2. Agent 2 validates [artifacts]
3. Communication protocol
4. Parallel execution rules
## π INTEGRATION POINTS
### With Other Skills
- **Skill 1**: How they integrate
- **Skill 2**: How they integrate
### With Tools
- **Tool 1**: Integration details
- **Tool 2**: Integration details
### With Infrastructure
[How this skill integrates with PAI infrastructure]
## π¨ CRITICAL WARNINGS
### Warning Category 1
**Rule:** [Critical rule]
**Rationale:** [Why this matters]
**Consequences of violation:**
- Consequence 1
- Consequence 2
### Warning Category 2
[Same structure]
## π‘ CORE PRINCIPLES
1. **Principle 1** - Detailed explanation with examples and rationale
2. **Principle 2** - Detailed explanation
3. **Principle 3** - Detailed explanation
[Continue for all principles]
## π EXAMPLES AND PATTERNS
### Example 1: [Scenario Name]
**Context:** [Situation description]
**Approach:**
```
Step-by-step walkthrough with commands/code
```
**Result:** [What was achieved]
**Lessons:** [What to learn from this]
### Example 2: [Scenario Name]
[Same structure]
## π SUCCESS METRICS / VALIDATION
### How to Measure [Quality]
- Metric 1: Target value
- Metric 2: Target value
- Metric 3: Target value
### Validation Checklist
- [ ] Check 1
- [ ] Check 2
- [ ] Check 3
## π§ TROUBLESHOOTING
### Problem 1: [Common Issue]
**Symptoms:**
- Symptom 1
- Symptom 2
**Diagnosis:**
[How to identify the problem]
**Solution:**
[Step-by-step fix]
### Problem 2: [Common Issue]
[Same structure]
## π SUPPLEMENTARY RESOURCES
### Internal Resources
- Path to related documentation
- Path to components
- Path to examples
### External Resources
- Official documentation links
- Community resources
- Learning materials
## π― QUICK REFERENCE
### Common Commands
```bash
# Task 1
command-sequence
# Task 2
command-sequence
# Task 3
command-sequence
```
### Decision Tree
**When to use approach A:**
- Condition 1
- Condition 2
**When to use approach B:**
- Condition 1
- Condition 2
## π APPENDIX
### Glossary
- **Term 1**: Definition
- **Term 2**: Definition
### Configuration Reference
[Detailed configuration options]
### API Reference
[If applicable - API documentation]
---
## π― SUMMARY
**Key Takeaways:**
1. Takeaway 1
2. Takeaway 2
3. Takeaway 3
**Remember:**
- Critical point 1
- Critical point 2
- Critical point 3
**Next Steps:**
- Action 1
- Action 2
- Action 3
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path β even casually (like "the xlsx in my downloads") β and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |