What problem does it solve? When operating Intendant, agents occasionally hit wrong or missing capabilities, forced workarounds, or avoidable tool calls and latency. This Skill channels those exceptional observations into one concise, deduplicated report instead of losing the signal or flooding the team with noise. ## Core Features & Use Cases - Exception-only reporting: Submit feedback only when Intendant behavior was wrong, misleading, missing, or clearly inefficient; routine successful use produces no report. - Structured report shape: Classify reports with kind (issue or efficiency), a short product surface, a one-line summary, reproduction details, a concrete recommendation, and optional impact and avoidable_calls fields. - Privacy guardrails: Never include transcripts, prompts, environment dumps, tool arguments, credentials, or secrets; use only short scrubbed opaque references in evidence_ref. - Use Case: While using Intendant's facade, you discover a needed verb is missing and must work around it with extra calls. You file one kind: issue report naming the surface, the workaround, and the simpler shape, then continue the user's task. ## Quick Start Ask the agent to report the Intendant friction you just hit through the report MCP tool with a short surface, summary, and recommendation.
