skill-optimizer MCP — Use Cases, Install & Live Demo

Why use it

Key features

Combines runtime evidence with static checks
Works on Claude Code, Codex, and any skill-compatible agent
Outputs a SKILL.md patch, not vague advice
Flags over-eager descriptions that cause mis-activation
Calls out duplicated capability across multiple skills

Live Demo

What it looks like in practice

skill-optimizer-skill.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "skill-optimizer-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/hqhq1025/skill-optimizer",
        "~/.claude/skills/skill-optimizer"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "skill-optimizer-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/hqhq1025/skill-optimizer",
        "~/.claude/skills/skill-optimizer"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "skill-optimizer-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/hqhq1025/skill-optimizer",
        "~/.claude/skills/skill-optimizer"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "skill-optimizer-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/hqhq1025/skill-optimizer",
        "~/.claude/skills/skill-optimizer"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "skill-optimizer-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/hqhq1025/skill-optimizer",
        "~/.claude/skills/skill-optimizer"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "skill-optimizer-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/hqhq1025/skill-optimizer",
          "~/.claude/skills/skill-optimizer"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add skill-optimizer-skill -- git clone https://github.com/hqhq1025/skill-optimizer ~/.claude/skills/skill-optimizer

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use skill-optimizer

How to diagnose and fix one underperforming skill

👤 Skill authors iterating on a specific skill ⏱ ~30 min intermediate

When to use: You notice one skill never activates, or activates wrongly.

Prerequisites

Session logs or transcripts — Claude Code stores traces locally; skill-optimizer reads them
Skill cloned — git clone https://github.com/hqhq1025/skill-optimizer ~/.claude/skills/skill-optimizer

Flow

Point it at the skill

Analyze ~/.claude/skills/my-skill/SKILL.md using my last 2 weeks of session logs.✓ Copied

→ Static + runtime findings
Review the patch

Show me the proposed SKILL.md diff.✓ Copied

→ Minimal, reviewable diff
Apply and validate

Apply the patch and tell me what to watch for this week.✓ Copied

→ Validation checklist

Outcome: A targeted improvement with an accountability plan.

Pitfalls

Optimizing for activation rate but breaking scope — Include a 'false positive rate' acceptance metric

Combine with: skillcompass-skill

Polish your first SKILL.md before publishing

👤 First-time skill authors ⏱ ~20 min beginner

When to use: You wrote a SKILL.md and want expert review before shipping.

Flow

Ask for a review

Review my SKILL.md against skill-optimizer's static checks.✓ Copied

→ Checklist with pass/fail + rationale
Fix issues

Apply the fixes and show me the final version.✓ Copied

→ Clean SKILL.md

Outcome: A ship-ready SKILL.md.

Pitfalls

Over-promising in the description — Be specific about what the skill does; Claude uses it to decide activation

Combinations

Pair with other MCPs for X10 leverage

skill-optimizer-skill + skillcompass-skill

SkillCompass ranks the bundle; skill-optimizer dives into the worst offender

Use SkillCompass to pick the weakest skill, then optimize its SKILL.md.✓ Copied

skill-optimizer-skill + filesystem

Apply SKILL.md patches directly

Apply the proposed diff to ~/.claude/skills/my-skill/SKILL.md.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
static-analysis	SKILL.md path	Before publishing or during iteration
log-based-analysis	logs + skill path	Post-use tuning
patch-generation	findings	After analysis

Cost & Limits

What this costs to run

API quota: none beyond LLM
Tokens per call: 2–10k per skill analysis
Monetary: free
Tip: Static analysis is nearly free; log analysis costs more — run it only when iterating

Security

Permissions, secrets, blast radius

Credential storage: none; logs may contain sensitive prompts — treat their path carefully

Data egress: none

Session logs can contain secrets — redact before sharing

Troubleshooting

Common errors and fixes

No logs found

Confirm Claude Code trace path; pass the path explicitly if non-default.

Suggestions conflict with intended scope

Tell the optimizer your scope constraints; it can respect non-goals

Alternatives

skill-optimizer vs others

Alternative	When to use it instead	Tradeoff
skillcompass-skill	You need bundle-level ranking, not single-skill depth	Breadth over depth

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills