What problem does it solve? Improving an existing skill without a clear problem statement leads to unfocused edits, broken evals, and regressions. This Skill enforces a disciplined workflow for updating skills in the IC Skills repo (skills.internetcomputer.org): understand the specific issue first, change precisely, and verify only what changed. ## Core Features & Use Cases - Problem-first gating: Refuses to start work until a specific issue is identified, preventing blind edits that risk breaking working content. - Targeted improvement areas: Guides updates to pitfalls, canister IDs, code examples, descriptions, and required frontmatter, with special handling for upstream-tracked skills like motoko and mops-cli. - Eval management: Seeds new eval files for skills lacking them, updates cases affected by changes, and runs only relevant eval subsets with baseline comparisons. - Use Case: A maintainer reports that the ckbtc skill's description never triggers. Use this Skill to diagnose the description, rewrite it with trigger keywords, add trigger evals, and run them with baseline before opening a PR. ## Quick Start Ask the assistant to improve a specific skill in the IC Skills repo by stating the exact problem, such as fixing a stale canister ID or adding a missing pitfall to the motoko skill.
