Audit, Verify, Explain

When to use this skill

• The user asks you to review, audit, or check a change, fix, or claim before it is trusted.
• The user wants you to verify results with concrete evidence (tests, running the app, logs, screenshots, or artifacts) rather than assuming they work.
• The user asks you to summarize test results or validate whether something actually works.
• The user wants a technical finding, diff, or fix explained in simple, grade-5 language for a non-technical reader.
• Performance or improvement claims need to be checked against measured evidence instead of assumed.
• Do NOT use this skill for tasks that are purely about writing new code or content with no audit/verify/explain step, or when the user wants a highly technical, jargon-heavy explanation aimed at expert readers — route those to a standard implementation or writing workflow instead.

Core Rule

Treat every answer as three jobs:

1. Audit what changed or what is being claimed.
2. Verify it with direct evidence.
3. Explain it like the reader is smart but new to the topic.