skill-architect
Orchestrates complete skill lifecycle from creation to optimization. Use for comprehensive skill development, reviewing skills, or managing skill quality.
What this skill does
# Skill Architect
## Purpose
Meta-orchestrator for the complete Claude Code skill lifecycle. Manages skill creation, review, optimization, and quality assurance through coordinated subagent workflows.
## When to Use
- User asks to "manage skills" or "oversee skill development"
- Complete skill lifecycle management
- Quality assurance for skill libraries
- Team skill development workflows
- Comprehensive skill audits
## Available Subagents
This orchestrator coordinates three specialized skills:
1. **@skill-generator** - Creates new skills from descriptions
2. **@skill-reviewer** - Reviews skills for quality and best practices
3. **@skill-optimizer** - Refactors skills using PDA
## Workflows
### Workflow 1: Create and Review
**Use when:** Creating a new skill with quality assurance
```
1. @skill-generator
- Generate SKILL.md from user description
- Create directory structure
- Apply best practices
2. @skill-reviewer
- Review generated skill
- Identify any issues
- Provide quality score
3. Report and Iterate (if needed)
- Present skill to user
- Address review feedback
- Finalize skill
```
**Trigger phrases:**
- "Create a skill for X and review it"
- "Generate and check a new skill"
- "Make a skill for X with quality check"
### Workflow 2: Audit and Optimize
**Use when:** Improving existing skills
```
1. @skill-reviewer
- Review existing skill
- Identify improvement opportunities
- Calculate potential savings
2. @skill-optimizer
- Apply recommended improvements
- Implement PDA refactoring
- Optimize token usage
3. Validation
- Compare before/after
- Verify functionality preserved
- Report improvements
```
**Trigger phrases:**
- "Audit this skill and optimize it"
- "Review and improve this skill"
- "Check and fix this skill"
### Workflow 3: Complete Lifecycle
**Use when:** End-to-end skill development
```
1. Requirements Gathering
- Understand skill purpose
- Identify use cases
- Determine scope
2. @skill-generator
- Create initial skill
- Structure content
- Add examples
3. @skill-reviewer
- Quality assessment
- Best practices check
- Improvement recommendations
4. @skill-optimizer (if needed)
- Apply optimizations
- Implement PDA
- Reduce token usage
5. Final Review
- Validate improvements
- Confirm quality standards
- Deliver production-ready skill
```
**Trigger phrases:**
- "Create a production-ready skill for X"
- "Develop a complete skill from scratch"
- "Build and validate a skill"
### Workflow 4: Skill Library Audit
**Use when:** Reviewing multiple skills
```
1. Discover Skills
- Find all skills in .claude/skills/
- List each skill with metadata
2. @skill-reviewer (parallel)
- Review each skill
- Generate quality scores
- Identify common issues
3. Aggregate Report
- Overall quality assessment
- Prioritized improvements
- Token savings opportunities
4. Recommendations
- Which skills need optimization
- Which skills are excellent
- Best practices to share
```
**Trigger phrases:**
- "Audit all my skills"
- "Review my skill library"
- "Check all skills for quality"
## Output Format
### For Creation Workflows
```markdown
# Skill Creation Complete
## Skill Overview
**Name:** [skill-name]
**Location:** .claude/skills/[skill-name]/
**Size:** [X] KB
## Quality Assessment
**Score:** [X/10]
**PDA Compliance:** Yes/No
**Status:** Ready for use / Needs improvements
## What Was Created
1. SKILL.md - Main orchestrator
2. reference/ - Detailed documentation
3. scripts/ - Utility scripts (if applicable)
## Usage
Invoke with: [example invocation]
## Next Steps
- [ ] Test the skill
- [ ] Adjust if needed
- [ ] Add to version control
```
### For Optimization Workflows
```markdown
# Skill Optimization Complete
## Summary
**Skill:** [skill-name]
**Original Size:** [X] KB
**Optimized Size:** [Y] KB
**Token Savings:** [Z]%
## Improvements Made
### Structure
- [Changes]
### Content
- [Changes]
### Token Efficiency
- [Changes]
## Quality Improvements
**Before:** Score [X]/10
**After:** Score [Y]/10
## Cost Impact
At 100 requests/day:
- Before: $[cost]/year
- After: $[new cost]/year
- Saved: $[savings]/year
## Validation
✅ Functionality preserved
✅ All links work
✅ Performance improved
```
### For Audit Workflows
```markdown
# Skill Library Audit Report
## Overview
**Total Skills:** [N]
**Average Score:** [X]/10
**Skills Needing Work:** [N]
## Skills by Quality
### Excellent (9-10)
- [skill-1]
- [skill-2]
### Good (7-8)
- [skill-3]
- [skill-4]
### Needs Improvement (5-6)
- [skill-5]
- [skill-6]
### Poor (1-4)
- [skill-7]
- [skill-8]
## Common Issues Found
1. [Issue] - [Count] skills affected
2. [Issue] - [Count] skills affected
## Prioritized Recommendations
### P1 (Critical)
- [Recommendations]
### P2 (Important)
- [Recommendations]
### P3 (Nice-to-Have)
- [Recommendations]
## Token Optimization Opportunity
**Current Usage:** [X] MB/day
**Potential Savings:** [Y] MB/day ([Z]%)
**Annual Cost Savings:** $[amount]
## Next Steps
1. Address P1 issues
2. Optimize skills with low scores
3. Apply best practices to all skills
```
## Quality Gates
Each workflow includes quality checks:
### Creation Quality Gates
- [ ] YAML frontmatter valid
- [ ] Description specific and actionable
- [ ] Clear instructions with examples
- [ ] Appropriate use of PDA
- [ ] No reserved words in name
- [ ] File paths use forward slashes
### Optimization Quality Gates
- [ ] Token savings achieved
- [ ] Functionality preserved
- [ ] Links verified working
- [ ] Structure improved
- [ ] User experience enhanced
### Review Quality Gates
- [ ] All dimensions evaluated
- [ ] Severity classification applied
- [ ] Recommendations actionable
- [ ] Token savings calculated
- [ ] Report comprehensive
## Best Practices Applied
This orchestrator ensures:
1. **Progressive Disclosure**
- Skills use PDA when appropriate
- Token-efficient design
- On-demand loading
2. **Quality Standards**
- Consistent structure
- Clear documentation
- Actionable examples
3. **Best Practices**
- Gerund naming
- Third-person descriptions
- Forward slash paths
- Single responsibility
4. **Token Optimization**
- Minimal SKILL.md size
- Reference files for details
- Scripts for mechanical work
## Integration
This orchestrator works with:
- **skill-generator** - For skill creation
- **skill-reviewer** - For quality assessment
- **skill-optimizer** - For improvement
## Advanced Features
### Batch Operations
Process multiple skills:
```
> Audit and optimize all skills in .claude/skills/
# Runs @skill-reviewer on each
# Runs @skill-optimizer on those needing improvement
# Generates aggregate report
```
### Skill Templates
Create from templates:
```
> Create a generator skill following the generator template
# Uses predefined pattern
# Applies best practices automatically
# Delivers consistent structure
```
### Continuous Improvement
Ongoing quality management:
```
> Set up skill quality monitoring
# Establishes quality baseline
# Recommends regular reviews
# Tracks improvements over time
```
## Examples
### Example 1: Create Complete Skill
**User:** "Create a production-ready skill for processing JSON files with validation and transformation"
**Workflow:**
```
1. @skill-generator
Creates: json-processor/
├── SKILL.md (4KB orchestrator)
├── reference/
│ ├── json-schema.md
│ ├── transformations.md
│ └── validation.md
└── scripts/
├── validate.py
└── transform.py
2. @skill-reviewer
Score: 9/10
PDA Compliance: Yes
Status: Ready for use
3. Report
Skill created and validated
All quality gates passed
Ready for production use
```
### Example 2: Optimize Poor Skill
**User:** "This 50KB skill is slow and expensive. Fix it."
**Workflow:**
```
1. @skill-reviewer
Score: 3/10
Issues: Monolithic, no PDA, token-inefficient
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.