false-positive-reviewer

Interpret AI-writing detector flags without converting them into unsupported authorship verdicts.

5.0k|441|Updated Mar 6, 2026
Ready to run
npx skills add https://github.com/conorbronsdon/avoid-ai-writing --skill false-positive-reviewer-conorbronsdon
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: false-positive-reviewer
Source: https://github.com/conorbronsdon/avoid-ai-writing/tree/main/skills/false-positive-reviewer
Command: npx skills add https://github.com/conorbronsdon/avoid-ai-writing --skill false-positive-reviewer-conorbronsdon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-writing detector output is often misread as proof of AI authorship, which can lead to unfair academic, hiring, publication, or disciplinary decisions. This Skill explains what detector flags actually mean, separates real signals from plausible false positives, and prevents scores from being turned into definitive authorship claims. ## Core Features & Use Cases - Evidence Classification: Distinguishes deterministic detector hits, model-only editorial observations, user-supplied context, and unavailable evidence. - False-Positive Analysis: Considers genre, second-language writing, technical register, editing tools, deadline pressure, and the writer's baseline style before interpreting flags. - Consequential-Decision Guardrails: Refuses to convert scores into claims of cheating, fraud, or dishonesty, and suggests more probative evidence such as drafts, revision logs, and source history. - Use Case: A hiring manager receives a detector report flagging a candidate's writing sample. Use this Skill to get a careful interpretation of what the flags do and do not establish, plus a list of evidence that would materially reduce uncertainty. ## Quick Start Review these AI-writing detector flags for plausible false positives and explain what they do and do not establish about authorship.

Frequently Asked Questions about false-positive-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I interpret AI-writing detector results fairly?▼

Treat detector output as noisy writing-quality signals, not proof of authorship. Classify each finding as a deterministic detector hit, a model-only observation, or user-supplied context, then consider genre, second-language writing, technical register, and editing tools before drawing conclusions.

Can AI detector scores prove someone used AI to write text?▼

No. Detector scores and pattern lists cannot establish definitive AI use, cheating, or dishonesty. This Skill explicitly refuses to convert uncertainty into a probability of authorship and instead suggests probative evidence like drafts, revision logs, and source history.

What causes false positives in AI-writing detection?▼

Common causes include second-language writing, technical or formulaic registers, genre conventions, deadline pressure, editing software, and typography tools. A writer's known baseline style also matters when evaluating whether flagged patterns are unusual.

What evidence is better than AI detectors for authorship decisions?▼

Process evidence is more probative for consequential decisions: source history, drafts, revision logs, direct discussion with the writer, and task-specific process artifacts. These reduce uncertainty far more than pattern-based detector scores.

When should I not rely on AI-writing detector output?▼

Avoid relying on detector output alone for academic, hiring, publication, or disciplinary decisions. Flags indicate writing-quality patterns that can appear in human text, so consequential claims require additional corroborating evidence.