super-skills

Decomposes complex user requests into executable subtasks, identifies required capabilities, searches for existing skills, and creates new skills when needed.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "super-skills" with this command: npx skills add <skill>

Super Skills

Quick Reference

┌─────────────────────────────────────────────────────────────┐
│  🎯 Core: Understand → Plan → Execute → Iterate             │
│  🚨 Rule: Problem → Analyze → Solve → Continue (NEVER WAIT) │
│  📊 Complexity: 4-8 Direct | 9-14 Staged | 15-20 Iterative  │
└─────────────────────────────────────────────────────────────┘

Core Philosophy

PrincipleDescription
Understand FirstDeeply analyze requirements before acting
Incremental DeliveryProduce verifiable intermediate results at each step
Expect FailuresDesign recovery mechanisms for every stage
Never StopSolve problems proactively; NEVER pause waiting for user

Workflow

UNDERSTAND ──→ PLAN ──→ EXECUTE ──→ ITERATE
    │            │          │          │
 Multi-layer  Task       Search &   Feedback
 Analysis     Breakdown  Install    Adjustment
 Complexity   Risk ID    Checkpoint Optimize

Phase 1: Understanding

1.1 Multi-Layer Analysis

understanding:
  surface:    # Literal meaning
    request: "{user's exact words}"
    keywords: [key terms]
    
  intent:     # True intent
    goal: "{what user really wants}"
    success: "{success criteria}"
    
  context:    # Environment
    env: "{OS/language/framework}"
    constraints: "{time/resources/permissions}"
    
  hidden:     # Unstated needs
    assumptions: "{implicit assumptions}"
    edge_cases: "{boundary conditions}"

1.2 Requirement Handling

TypeAction
ExplicitExecute directly
ImplicitProactively supplement
AmbiguousState assumptions, choose most likely interpretation
ConflictingPoint out conflict, request clarification
Out of ScopeExplain why, provide alternatives

1.3 Complexity Score

Dimensions (1-5 each):
  technical + scope + uncertainty + dependencies = total

Strategy:
  4-8   → Direct execution
  9-14  → Staged verification
  15-20 → Iterative prototyping

1.4 Clarification

Confidence ≥70%: State assumptions → Continue → Leave adjustment points
Confidence <70%: Provide options for user to choose (NO open-ended questions)

Phase 2: Planning

2.1 Task Structure

task:
  id: 1
  name: "{task name}"
  capability: "{capability type}"
  input: [required inputs]
  output: "{type/format}"
  depends_on: [prerequisite task IDs]
  timeout: "30s"
  retries: 3
  validation: "{success condition}"
  fallback: "{alternative approach}"

2.2 Dependency Graph

[1:Setup] → [2:Auth] → [3:Fetch] ─┐
                                  ↓
[4:Process] ← [5:Transform] ← [6:Parse]
     ↓
[7:Output]

Critical Path: 1→2→3→6→5→4→7
Parallel Opportunities: Independent tasks can run concurrently

2.3 Capability Map

CapabilityStatusKeywords
browser_automationbrowser, puppeteer, playwright
api_integrationapi, rest, {service}
data_extraction⚠️parse, pdf, ocr
message_deliveryslack, discord, email
database_operationssql, mongodb
deploymentdeploy, docker, k8s
data_transformation
content_generation
code_execution
scheduling

✅ Built-in | ⚠️ Complex | ❌ Skill required


Phase 3: Skill Acquisition

# Search priority
1. npx skills find {service_name}      # Exact match
2. npx skills find {capability} {domain}  # Combined
3. https://skills.sh/                  # Browse

# Install
npx skills add <skill> -g

# On failure: Switch registry → Manual clone → Inline implementation

Evaluation Criteria

DimensionWeight
Feature match40%
Documentation quality20%
Maintenance status20%
Community validation10%
Dependency simplicity10%

Phase 4: Risk & Resilience

4.1 Risk Matrix

RiskDetectionAuto-Resolution
Token expired401/403Refresh → Re-auth → Degrade
Rate limited429Backoff → Cache → Degrade
TimeoutTimeoutIncrease → Reduce batch → Chunk
Parse errorParse ErrorSwitch parser → Regex → Raw text
Connection failedConnectionRetry → Proxy → Offline mode
Missing dependencyImport ErrorAuto-install → Alternative pkg → Inline

4.2 Resilience Patterns

retry:           max=3, backoff=exponential
circuit_breaker: threshold=5, recovery=60s
timeout:         connect=10s, read=30s, total=120s
fallback:        cache | default | skip

4.3 Checkpoints

checkpoint:
  trigger: after_each_task
  content: [task_id, state, data, timestamp]
  recovery: Load checkpoint → Validate → Resume from failure point

Phase 5: Execution

5.0 🚨 Problem Solving (CRITICAL)

On problem → Analyze → Solve → Continue. NEVER pause waiting.

Problem → Diagnose type → Analyze cause → Try solutions by priority → Continue
                                          ↓
                            Plan A fails → Plan B → Plan C → Degraded solution

Auto-Fix Table

ProblemAuto-Resolution (in order)
Missing dependencyInstall → Alternative pkg → Inline
Permission deniedAdjust perms → Alternative path → Minimal perms
API failureRetry (backoff) → Switch endpoint → Cache → Degrade
TimeoutIncrease timeout → Reduce batch → Chunk → Async
Parse errorSwitch parser → Regex → Raw text
Auth failureRefresh token → Re-auth → Backup credentials
Resource exhaustedChunk → Clear cache → Stream → Reduce concurrency
Network issueRetry → Switch network → Proxy → Offline
File not foundCreate → Default value → Skip

Mindset

forbidden:
  - "I encountered a problem and need your help"
  - "Execution paused, waiting for instructions"
  
required:
  - "Encountered X issue, trying Y solution"
  - "Plan A failed, switching to Plan B"
  - "Problem resolved, continuing execution"

Escalation (ONLY when ALL conditions met)

  • Tried ≥3 different solutions
  • All failed
  • Goal completely unachievable
  • No acceptable degraded solution available

5.1 Execution Modes

ModeUse Case
SequentialTasks with strong dependencies
ParallelIndependent tasks
PipelineData stream processing
IterativeRequires feedback loops

5.2 Progress Template

══════════════════════════════════════
📊 PROGRESS
══════════════════════════════════════
Phase 1: Setup              [████████░░] 80%
  ✅ Task 1: Initialize     Done (2.3s)
  🔄 Task 2: Fetch          Running...
  ⏳ Task 3: Process        Waiting
──────────────────────────────────────
⏱️ Elapsed: 3m | ETA: ~5m
══════════════════════════════════════

Phase 6: Iteration

Feedback Loop

Collect feedback → Analyze issues → Adjust approach → Loop

Adjustment Levels

LevelActions
MinorParameter tuning, format adjustment
ModerateReplace skills, add/remove tasks
MajorRedesign architecture

Execution Plan Template

════════════════════════════════════════════════════
📋 SUPER SKILLS PLAN
════════════════════════════════════════════════════

🎯 REQUEST: {user's exact words}

📊 UNDERSTANDING
────────────────────────────────────────────────────
Intent:      {true intent}
Success:     {success criteria}
Complexity:  {score} → {strategy}

Assumptions:
  • {assumption 1}
  • {assumption 2}

────────────────────────────────────────────────────
📋 TASKS
────────────────────────────────────────────────────
│ ID │ Task       │ Capability  │ Status │ Risk │
├────┼────────────┼─────────────┼────────┼──────┤
│ 1  │ {task}     │ {capability}│ ✅/📦  │ 🟢/🔴│

Status: ✅ Built-in | 🔧 Found | 📦 Create
Risk:   🟢 Low | 🟡 Medium | 🔴 High

────────────────────────────────────────────────────
🔧 SKILLS
────────────────────────────────────────────────────
npx skills add {skill} -g

────────────────────────────────────────────────────
🛡️ RESILIENCE
────────────────────────────────────────────────────
Checkpoints: □ After Phase 1  □ After Phase 2
Fallbacks:   {task} → {alternative}

────────────────────────────────────────────────────
✅ COMPLETION
────────────────────────────────────────────────────
□ {acceptance criterion 1}
□ {acceptance criterion 2}
════════════════════════════════════════════════════

Example: E-commerce Pipeline

# "Scrape product data from multiple platforms daily, analyze price trends, send report"

understanding:
  intent: "Automated price monitoring for pricing decisions"
  success: "Daily price trend visualization report received"
  
complexity:
  technical: 4, scope: 4, uncertainty: 3, dependencies: 4
  total: 15 → Iterative prototyping strategy

tasks:
  1. Configure product list  → file_operations ✅
  2. Multi-platform scraping → browser_automation ❌
  3. Data persistence        → database_operations ❌
  4. Data cleaning           → data_transformation ✅
  5. Trend analysis          → code_execution ✅
  6. Generate charts         → content_generation ✅
  7. Generate report         → content_generation ✅
  8. Send email              → message_delivery ❌

resilience:
  checkpoints: [after:2 save:raw_data] [after:5 save:analysis]
  fallbacks:
    task_2: "Skip failed platforms, continue with others"
    task_8: "Save to local file"

Error Handling (Every error has auto-resolution)

PhaseErrorAuto-Resolution
AnalysisUnclear requirementsChoose most likely → State assumptions → Leave adjustment points
AnalysisBeyond capabilitySearch alternatives → Combine capabilities → Partial implementation
PlanningCircular dependencyBreak weakest link → Merge tasks
SearchSkill not foundExpand keywords → Online search → Auto-create
InstallInstallation failedSwitch registry → Manual clone → Inline implementation
ExecutionAuth failureRefresh → Re-auth → Degrade to public data
ExecutionRate limitedBackoff → Switch account → Use cache
ExecutionTimeoutIncrease timeout → Reduce batch → Skip and continue
ValidationResult mismatchRetry with adjusted params → Relax validation → Mark for review

Best Practices

PhasePrinciples
UnderstandingMulti-layer analysis, proactive assumptions, complexity assessment
PlanningArchitecture first, clear dependencies, upfront risk identification
ExecutionNEVER STOP, try multiple solutions, graceful degradation, incremental verification
IterationFast feedback, continuous optimization, knowledge accumulation

Resources

  • CLI: npx skills --help
  • Browse: https://skills.sh/
  • Capabilities: references/capability_types.md
  • Template: assets/skill_template.md

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

task-decomposer

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

workflow-automation

When to use this skill

Repository Source
Automation

workflow-automation

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

task-decomposition

No summary provided by upstream source.

Repository SourceNeeds Review
191-jwynia