skill-optimizer
Skill Optimizer trains existing SKILL.md files through iterative improvement cycles inspired by machine learning optimization, analyzing accumulated learn-rule corrections to propose bounded patches that are validated against past user feedback before acceptance. Use when a skill has gathered eight or more learning trajectories and needs consolidation or refinement rather than expansion, with available API budget and offline processing time.
git clone --depth 1 https://github.com/rohitg00/pro-workflow /tmp/skill-optimizer && cp -r /tmp/skill-optimizer/skills/skill-optimizer ~/.claude/skills/skill-optimizerSKILL.md
# Skill Optimizer Train an existing SKILL.md the way a deep-learning optimizer trains weights: via rollouts, gradient-like reflections, validation-gated acceptance. No model retraining; only the skill markdown changes. ## When to use Use this skill when: - A pro-workflow skill has accumulated 8+ learn-rule rows for it - The user reports the skill is "getting bloated" or "rules keep being repeated" - The user wants offline, budget-capped improvement over multiple sessions Do not use when: - Skill has fewer than 8 trajectories (nothing to learn from) - The user wants real-time edits (this is offline, single-shot) - No `ANTHROPIC_API_KEY` (or equivalent provider key) is available ## Architecture (mirrors SkillOpt's six-stage loop) ```text rollout pull recent learnings from SQLite (existing learn-rule rows) reflect optimizer LLM analyzes a minibatch, proposes add/delete/replace patches aggregate vote-merge patches across minibatches select clip by LR budget (default: 3 adds, 2 deletes, 3 replaces per step) update apply selected patches to a candidate skill content evaluate evaluator LLM scores candidate against held-out validation items gate accept candidate only if weighted score >= current + acceptThreshold slow update at epoch boundary, consolidate accepted edits into a coherent rewrite ``` Failed candidates are stored in a rejection buffer and fed back to the next reflect step so the optimizer doesn't propose the same patch twice. ## Run it ```bash /skill-optimize <slug> [options] ``` Options (all optional; sensible defaults shown): | Flag | Default | Notes | |---|---|---| | `--epochs N` | 3 | Outer loop count | | `--batch-size N` | 8 | Trajectories per minibatch | | `--minibatches N` | 2 | Minibatches per epoch | | `--holdout N` | 6 | Validation items reserved (max ~25% of trajectories) | | `--budget-usd X` | 0.50 | Hard cap; loop aborts when spent | | `--optimizer-model M` | `claude-sonnet-4-6` | Reflect + slow-update model | | `--evaluator-model M` | `claude-haiku-4-5-20251001` | Gate model (cheaper) | | `--max-adds N` | 3 | LR budget per step | | `--max-deletes N` | 2 | | | `--max-replaces N` | 3 | | | `--accept-threshold X` | 0.0 | Minimum score delta to accept candidate | | `--max-skill-tokens N` | 2000 | Hard cap on candidate length | | `--slow-every N` | 2 | Epochs between consolidation passes | | `--json` | off | Machine-readable output | Kill switch: `touch ~/.pro-workflow/STOP` aborts the loop between steps. ## Output - Candidate accepted → SKILL.md overwritten, hash stamp appended in HTML comment - Run details persist in `optimization_runs`, `optimization_candidates`, `optimization_patches`, `optimization_rejections` - Validation set persists in `optimization_validation` (reusable across runs) Inspect after: ```bash sqlite3 ~/.pro-workflow/data.db "SELECT id, skill_slug, initial_score, best_score, accepted_steps, rejected_steps, spent_usd FROM optimization_runs ORDER BY id DESC LIMIT 5" ``` ## Rules - Validation set is frozen at run start. Never re-derive from new corrections mid-run. - One candidate per step. No parallel branches. - Slow-update output is itself a candidate; it must pass the gate to replace the best. - The optimizer LLM and evaluator LLM may be different models. Mixing a strong optimizer with a cheap evaluator is the SkillOpt-recommended config. - If `spent_usd >= budget_usd` at any step boundary, the loop ends with `stopped_reason="budget exhausted"`. - Patches whose anchor is no longer present in the skill (because a prior patch in the same step removed it) are recorded as rejected with reason `anchor_missing`. ## Provenance Inspired by Microsoft SkillOpt (arXiv:2605.23904). The six-stage rollout/reflect/aggregate/select/update/evaluate pipeline, LR budget, rejection buffer, and slow / meta update mechanics are adapted to pro-workflow's existing SQLite + learn-rule data plane. No SkillOpt code is reused. "ReflACT" is not a SkillOpt term and is not used here; the loop is referred to by stage names only.
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
Auto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".
Smart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual compact or when auto-compact triggers.
Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.
Master the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.
Optimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.