False-Positive Reviewer answers questions such as does this detector score prove the text was written by AI. It separates deterministic detector hits, model-only observations and facts the user supplied, explains plausible human causes for each signal, and declines to turn a score into a verdict about cheating, fraud or hiring suitability.
It suggests more useful evidence for consequential decisions, such as drafts, revision history and a conversation with the writer.
What You Get
- A breakdown of which observations came from executed tooling, model-only review or user-supplied context
- An explanation of why each signal may have a human cause
- A statement of what the text shows, what it may suggest and what it cannot establish
- A list of more probative evidence, such as source history, drafts and revision logs
- A return-to-router request when new signal collection or a rewrite is wanted
Common Use Cases
- A teacher asks whether a high detector score shows a student used AI
- A hiring manager wants to know how much weight a flagged cover letter deserves
- An editor questions why a human-written article trips many flags
- A writer working in a second language wants to understand false positives
- A team writes a policy on how detector results may be used
What Makes It Unique
The skill is built to resist the pull toward a verdict. It keeps score and label as noisy evidence, refuses to invent confidence values or a probability of authorship, and points to process evidence for decisions with consequences. Its place in the skill graph is terminal, which prevents a loop between reviewer and detector.
Under The Hood
This is an instructions-only skill with no scripts. It loads one instruction file and reads the rulebook and routing files of the sibling skills as references. It does not run commands, call APIs or write files. When more evidence is needed it hands control back to the router, which may run the detector.