skill-maintenancelisted

# Maintain Meteor agent skills Create focused, verifiable skills for Meteor application developers. Preserve the repository contract and avoid turning the catalog into a copy of the documentation. ## Scope Published skills live under `skills/`. Maintainer workflows live under `.github/skills/` and are not release artifacts. Before editing: 1. Read `AGENTS.md` completely. 2. Read `templates/SKILL.template.md` for a new skill. 3. Read the target skill, its references, and its evaluation cases for an update. 4. Inspect neighboring skills before changing routing or scope. Do not copy maintainer skills from a Meteor source checkout into the public catalog. They describe framework contributor workflows, while this repository serves application developers. ## Resolve a Meteor checkout Resolve a checkout only when factual verification needs Meteor documentation, source, or tests. 1. Prefer a path supplied by the user or task. 2. Otherwise, use `METEOR_CHECKOUT` when it is set. 3. Otherwise, inspect accessible workspace roots and direct sibling directories for candidates. 4. Validate a candidate with `git -C <path> rev-parse --show-toplevel`. Confirm that `v3-docs/`, `packages/`, and `tools/` exist. Prefer a Git remote that points to `meteor/meteor`; allow a fork when its upstream or structure is clear. 5. Use an automatically discovered path only when exactly one candidate is credible. Report the resolved path. 6. If no candidate or multiple candidates remain, ask the user f