agentskills-doctorlisted

# Agent Skills Doctor Validate an existing Agent Skill against the agentskills.io specification and best practices, report every finding with its check ID, and — when the user asks — fix the findings and re-verify. Read-only by default: never modify a skill unless the user explicitly asks for fixes. ## Workflow - [ ] Step 1: Gather input — the path to the skill to validate. - [ ] Step 2: Detect — run skillscheck and skills-ref when available, then the manual checklist. - [ ] Step 3: Report — present findings grouped by severity with suggested fixes. - [ ] Step 4: Fix — only when the user asks; auto-apply safe fixes, confirm judgment fixes. - [ ] Step 5: Re-verify — re-run the linters and confirm findings are gone. ### Step 1: Gather input You need one input: the **path to a skill directory** (or a `SKILL.md` file). If the user has not provided one, ask. Do not guess which skill to validate when several exist. ### Step 2: Detect Run every check that is available, collecting findings with their check IDs: 1. **skillscheck** — primary linter. If `uvx` is installed, run `uvx skillscheck <skills-parent-dir>` (e.g. `uvx skillscheck skills` for `skills/<name>/`); otherwise run a `skillscheck` binary on `PATH`. Use `--format json` when you need to parse output programmatically. Exit code 0 = no errors, 1 = errors. If neither is available, note the skip. 2. **skills-ref** — second automated check. If installed, run `skills-ref validate ./<name>