SK

skill-tuning

Diagnostic tool to fix performance, context, and execution failures in agent skills.

Install

mkdir -p .claude/skills/skill-tuning && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6305" && unzip -o skill.zip -d .claude/skills/skill-tuning && rm skill.zip

Installs to .claude/skills/skill-tuning

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Universal skill diagnosis and optimization tool. Detect and fix skill execution issues including context explosion, long-tail forgetting, data flow disruption, and agent coordination failures. Supports Gemini CLI for deep analysis. Triggers on "skill tuning", "tune skill", "skill diagnosis", "optimize skill", "skill debug".
325 charsno explicit “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Advanced

Key capabilities

  • Diagnose skill execution issues
  • Analyze context and memory
  • Perform deep analysis via Gemini CLI
  • Apply verified fixes
  • Verify fix effectiveness

How it works

It orchestrates a diagnosis phase followed by fix application and verification to resolve issues like context explosion or data flow disruption.

Inputs & outputs

You give it
Failing skill or issue description
You get back
Diagnosis report and applied fixes

When to use skill-tuning

  • Debug failing agent skills
  • Fix context explosion issues
  • Optimize skill data flow
  • Diagnose agent coordination failures

About this skill

Skill Tuning

Autonomous diagnosis and optimization for skill execution issues.

Architecture

┌─────────────────────────────────────────────────────┐
│  Phase 0: Read Specs (mandatory)                    │
│  → problem-taxonomy.md, tuning-strategies.md         │
└─────────────────────────────────────────────────────┘
                        ↓
┌─────────────────────────────────────────────────────┐
│  Orchestrator (state-driven)                         │
│  Read state → Select action → Execute → Update → ✓ │
└─────────────────────────────────────────────────────┘
        ↓                           ↓
┌──────────────────────┐   ┌──────────────────┐
│  Diagnosis Phase     │   │ Gemini CLI       │
│  • Context          │   │ Deep analysis    │
│  • Memory           │   │ (on-demand)      │
│  • DataFlow         │   │                  │
│  • Agent            │   │ Complex issues   │
│  • Docs             │   │ Architecture     │
│  • Token Usage      │   │ Performance      │
└──────────────────────┘   └──────────────────┘
                ↓
        ┌───────────────────┐
        │  Fix & Verify     │
        │  Apply → Re-test  │
        └───────────────────┘

Core Issues Detected

PriorityProblemRoot CauseFix Strategy
P0Authoring ViolationIntermediate files, state bloat, file relayeliminate_intermediate, minimize_state
P1Data Flow DisruptionScattered state, inconsistent formatsstate_centralization, schema_enforcement
P2Agent CoordinationFragile chains, no error handlingerror_wrapping, result_validation
P3Context ExplosionUnbounded history, full content passingsliding_window, path_reference
P4Long-tail ForgettingEarly constraint lossconstraint_injection, checkpoint_restore
P5Token ConsumptionVerbose prompts, state bloatprompt_compression, lazy_loading

Problem Categories (Detailed Specs)

See specs/problem-taxonomy.md for:

  • Detection patterns (regex/checks)
  • Severity calculations
  • Impact assessments

Tuning Strategies (Detailed Specs)

See specs/tuning-strategies.md for:

  • 10+ strategies per category
  • Implementation patterns
  • Verification methods

Workflow

StepActionOrchestrator DecisionOutput
1action-initstatus='pending'Backup, session created
2action-analyze-requirementsAfter initRequired dimensions + coverage
3Diagnosis (6 types)Focus areasstate.diagnosis.{type}
4action-gemini-analysisCritical issues OR user requestDeep findings
5action-generate-reportAll diagnosis completestate.final_report
6action-propose-fixesIssues foundstate.proposed_fixes[]
7action-apply-fixPending fixesApplied + verified
8action-completeQuality gates passsession.status='completed'

Action Reference

CategoryActionsPurpose
Setupaction-initInitialize backup, session state
Analysisaction-analyze-requirementsDecompose user request via Gemini CLI
Diagnosisaction-diagnose-{context,memory,dataflow,agent,docs,token_consumption}Detect category-specific issues
Deep Analysisaction-gemini-analysisGemini CLI: complex/critical issues
Reportingaction-generate-reportConsolidate findings → final_report
Fixingaction-propose-fixes, action-apply-fixGenerate + apply fixes
Verifyaction-verifyRe-run diagnosis, check gates
Exitaction-complete, action-abortFinalize or rollback

Full action details: phases/actions/

State Management

Single source of truth: .workflow/.scratchpad/skill-tuning-{ts}/state.json

{
  "status": "pending|running|completed|failed",
  "target_skill": { "name": "...", "path": "..." },
  "diagnosis": {
    "context": {...},
    "memory": {...},
    "dataflow": {...},
    "agent": {...},
    "docs": {...},
    "token_consumption": {...}
  },
  "issues": [{"id":"...", "severity":"...", "category":"...", "strategy":"..."}],
  "proposed_fixes": [...],
  "applied_fixes": [...],
  "quality_gate": "pass|fail",
  "final_report": "..."
}

See phases/state-schema.md for complete schema.

Orchestrator Logic

See phases/orchestrator.md for:

  • Decision logic (termination checks → action selection)
  • State transitions
  • Error recovery

Key Principles

  1. Problem-First: Diagnosis before any fix
  2. Data-Driven: Record traces, token counts, snapshots
  3. Iterative: Multiple rounds until quality gates pass
  4. Reversible: All changes with backup checkpoints
  5. Non-Invasive: Minimal changes, maximum clarity

Usage Examples

# Basic skill diagnosis
/skill-tuning "Fix memory leaks in my skill"

# Deep analysis with Gemini
/skill-tuning "Architecture issues in async workflow"

# Focus on specific areas
/skill-tuning "Optimize token consumption and fix agent coordination"

# Custom issue
/skill-tuning "My skill produces inconsistent outputs"

Output

After completion, review:

  • .workflow/.scratchpad/skill-tuning-{ts}/state.json - Full state with final_report
  • state.final_report - Markdown summary (in state.json)
  • state.applied_fixes - List of applied fixes with verification results

Reference Documents

DocumentPurpose
specs/problem-taxonomy.mdClassification + detection patterns
specs/tuning-strategies.mdFix implementation guide
specs/dimension-mapping.mdDimension ↔ Spec mapping
specs/quality-gates.mdQuality verification criteria
phases/orchestrator.mdWorkflow orchestration
phases/state-schema.mdState structure definition
phases/actions/Individual action implementations

When not to use it

  • For non-skill related code issues
  • Without initial diagnosis

Prerequisites

Gemini CLI

Limitations

  • Requires diagnosis before fixing
  • Requires Gemini CLI for deep analysis

How it compares

It uses a structured diagnosis-first approach compared to manual debugging.

Compared to similar skills

skill-tuning side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
skill-tuning (this skill)15moReviewAdvanced
chrome-devtools417moReviewIntermediate
python-performance-optimization272moNo flagsIntermediate
analyzing-logs1425dReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

chrome-devtools

mrgoonie

Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.

41157

python-performance-optimization

wshobson

Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.

27131

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

memory-mcp

d-o-hub

Use and troubleshoot the Memory MCP server for episodic memory retrieval and pattern analysis. Use this skill when working with MCP server tools (query_memory, analyze_patterns, advanced_pattern_analysis), validating the MCP implementation, or debugging MCP server issues.

6100

redis-inspect

civitai

Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache. Use for debugging cache issues, checking cached values, and monitoring cache state. Read-only by default.

646

obsidian-performance-tuning

jeremylongshore

Optimize Obsidian plugin performance for smooth operation. Use when experiencing lag, memory issues, or slow startup, or when optimizing plugin code for large vaults. Trigger with phrases like "obsidian performance", "obsidian slow", "optimize obsidian plugin", "obsidian memory usage".

640

Search skills

Search the agent skills registry