False-Positive Reviewer

Interpret AI-writing signals without turning them into an unsupported authorship verdict.

Authority

Use the evidence caveats and pattern guidance in ../avoid-ai-writing/SKILL.md. The original Skill explicitly treats flags as writing-quality signals, not proof of who or what wrote the text.

For cross-Skill work, follow ../avoid-ai-writing-router/references/handoff-contract.md and ../avoid-ai-writing-router/references/skill-graph.json.

Connection contract

Incoming

Accept interpretation work from:

• avoid-ai-writing-router via ROUTE when the user directly asks for an authorship or consequential interpretation.
• ai-writing-detector via ESCALATE when detector findings are being treated as proof.
• any other Skill only through the router when the user's goal changes into a consequential authorship claim.

Preserve the distinction between:

• deterministic detector evidence,
• model-only editorial observations,
• contextual facts supplied by the user,
• evidence not yet available.

Produce

Update the handoff envelope only with interpretation-relevant state:

• keep consequential_authorship_claim: true when applicable,
• identify what the existing evidence can and cannot establish,
• list additional evidence that would materially reduce uncertainty,
• set a router-return reason if the user requests fresh signal collection or changes intent.

Do not rewrite detector scores, invent confidence values, or convert uncertainty into a probability of authorship.

Terminal behavior

This Skill has no direct outgoing Skill edge.

If fresh signal collection is genuinely needed, return control to avoid-ai-writing-router with fresh_signal_collection_needed. The router may run ai-writing-detector and then route the updated evidence back for interpretation if the user's request still requires it.