agent-practice-audit
Agent Practice Audit
Answer one question with evidence: how far is this person's coding-agent usage from what the vendors officially recommend? Two modes share one practice list, references/practices.json.
| Mode | Input | Output |
|---|---|---|
| audit | Local session logs (last N days, default 60) and agent config | report.html + report-data.json under $AGENT_PRACTICE_AUDIT_DIR/reports/YYYY-MM-DD/ |
| refresh | Official pages on the allowlist | Diff to references/practices.json + a section in references/changelog.md |
Pick the mode from what the user wants to know. "How am I doing / score me / check-up / what should I change" is audit. "Update the practice list / are the sources still valid / add what vendors published recently" is refresh. A request that only checks links (no new practices) is check_practices.py --fetch alone: it writes nothing; report the link status and the gate line, and change files only if the user then asks. When unsure, ask in one line; when the run is scheduled or headless, nobody can answer, so do the mode named in the invocation and never stop to ask.
Reply in the user's language; set lang in judgments.json to match.
Related: dev-environment-roi-audit answers "is this tool, MCP or skill worth keeping?" with ablations. This skill answers "how far is my usage from official practice?". When a finding is really about cost or startup tax of a component, point to that skill instead of judging it here.