What problem does it solve? Authoring and reviewing .agent.md and .prompt.md files for different model vendors requires tracking divergent prompting conventions (Claude XML structuring vs GPT-5.5 outcome-first skeletons), and manual reviews are inconsistent without a canonical, machine-readable rule set. ## Core Features & Use Cases - Vendor rule catalog: A rules.json source of truth maps every rule to an ID, severity, source citation, and validator check, covering Claude XML blocks, GPT-5.5 skeleton sections, handoff enrichment, and frontmatter model style. - Six-step audit procedure: Read frontmatter, classify the model family, load the matching checklist, run validate-agents.mjs, perform a manual pass, and produce a verdict report (APPROVED / NEEDS_REVISION / REJECTED) using the audit template. - Model-family detection: Mirrors the validator's classifyModel() logic to assign families (claude-opus, claude-sonnet, gpt-5.5, etc.) with per-family severity statuses. - Use Case: A reviewer investigating an npm run lint:vendor-prompting finding loads this skill, maps the ruleId to its rule and vendor source, then follows the checklist to confirm or remediate the violation. ## Quick Start Ask the agent to audit a specific .agent.md file against vendor prompting best practices and produce a verdict report.