What problem does it solve? When a shipped Intendant skill misleads you, lacks a needed recipe, or forces costly workarounds, there is no ad-hoc channel to capture that friction. This dev-fleet overlay defines when and how to file one structured exception report so skill quality issues reach the product team with trusted provenance. ## Core Features & Use Cases - Exception-only reporting: Files reports only for wrong, missing, or confusing guidance, or concrete efficiency opportunities — never for routine successful use. - Structured report schema: Uses the Intendant report MCP tool with kind (issue or efficiency), surface (skill:<skill-name>), summary, details, recommendation, and an optional scrubbed evidence reference. - Built-in hygiene rules: Prohibits pasting prompts, transcripts, credentials, tokens, or machine names, and forbids creating feedback hubs or editing shipped skills directly. - Use Case: While using a shipped skill you discover its documented recipe is outdated and forces extra tool calls. You file one efficiency report via the report tool describing the smaller correct recipe, and the daemon deduplicates it against open reports. ## Quick Start Ask the agent to file a dogfood report through the Intendant report MCP tool describing the specific skill friction you hit, with kind, surface, summary, and a recommended fix.
