Generic Agent Updater

After verification, take corrective action:

• Stale file/path references: Update to the correct current path, or remove if the resource no longer exists.
• Broken URLs: Remove or flag for the user if a replacement is unclear.
• Outdated factual content: Update the content to match current reality (read the relevant source files to confirm).
• Missing sections: Flag to the user but do not invent content — ask what should go there.
• Agents that are entirely obsolete: Flag for removal and explain why, but do not delete without user confirmation.

Steps

1. Read the agents/ directory in the project root and collect all .md files (skip .gitkeep and non-agent files).
2. For each agent file found, spawn a parallel verification agent (using the Agent tool) that: a. Reads the full agent file. b. Validates frontmatter fields (name, description) and checks the filename matches. c. Extracts all file paths, local paths, and URLs referenced in the agent content. d. Verifies each file path exists by attempting to read or glob it. e. Verifies each URL is reachable (HEAD request via WebFetch when possible). f. Cross-references factual claims against the current codebase (e.g., if the agent describes a project structure, verify it matches). g. Returns a structured report: agent name, status (healthy / needs-update / obsolete), list of issues found, and suggested fixes.
3. Collect all parallel verification reports.
4. For agents marked needs-update: apply the suggested fixes directly to the agent file. Show the user a summary of what changed.
5. For agents marked obsolete: present the reasoning to the user and ask for confirmation before deleting.
6. For agents marked healthy: report them as passing with no action needed.
7. Output a final summary table listing every agent, its status, and what actions were taken.

Constraints

• Never delete an agent file without explicit user confirmation.
• Never invent content for missing sections — flag them and ask the user.
• Run all agent verifications in parallel to minimize wall-clock time.
• Do not modify agents that pass all checks — leave healthy agents untouched.
• Only verify agents in the agents/ folder of the current project root — do not scan other plugin directories or external paths.
• If the agents/ folder is empty or contains no .md files, report that clearly and exit without error.
• Do not attempt to run or execute agent logic — this skill only validates the static content of agent definition files.
• Respect the project's naming conventions: agent filenames must be kebab-case and match their name frontmatter field.