skill-improverlisted

# Skill Improver — Autoresearch for SKILL.md > **Core Philosophy:** The human programs the researcher, not the research. > Apply Karpathy's autoresearch methodology — greedy hill climbing with > keep/discard against a scalar metric — to autonomously improve Claude Code > skills. ## Invocation Argument grammar: ``` /skill-improver <mode> <target> [--opts] ``` - `<mode>` — `improve` (default) | `score` | `freshen` | `trigger` | `philosophy` | `batch` - `<target>` — skill name (e.g. `gh-cli`), absolute SKILL.md path, `--all`, or glob (e.g. `vllm-*`) - `[--opts]` — mode-specific flags (e.g. `--iterations 15`, `--probe-budget 30`, `--runs-per-query 5`) Examples: ``` /skill-improver freshen autoresearch /skill-improver score gh-cli /skill-improver improve ~/.claude/skills/helm /skill-improver trigger vllm-caching /skill-improver trigger gh-cli --missed "find issue with label X" /skill-improver batch freshen --all /skill-improver freshen --group 'vllm-*' ``` If `<mode>` is omitted, default to `improve`. If `<target>` is omitted and mode is not `batch`, prompt the user. For `batch`, the target after `batch` selects the sub-mode (`freshen`, `improve`, or `trigger`, default `improve`); the target list comes from `scripts/scan-skills.sh`. The `--missed "<phrase>"` flag (trigger mode only, repeatable) seeds the eval set with user-reported failures as gold should-trigger queries. ## The Improvement Loop ### Phase 0: Setup 1. Identify the target skill. Accept a path, or run `scr