A long low machined bench where one steel ribbon runs from a flared inlet past a comb of feeler pins and a sprung roller pair, then crosses a diagonal cut into a bone-grey outline drawing of a balance beam, a fine needle probe and a tapered wedge needle; a blue line follows the ribbon's channel the whole way into the wedge's notch.
Creative

DetectAI

Detects AI-generated writing: heuristic audit against known AI patterns, statistical signals (entropy, burstiness), an empirical Pangram score, and a keyless scan for watermark or steganography signatures (invisible characters, homoglyphs, bidi)

03
Workflows
00
Tools
01
Reference
11
Triggers

Key Points

Not for rewriting prose (a writing skill), plagiarism, judging quality

Inside the Skill

The thinking, frameworks, and architecture that distinguish this skill from a generic version of the same task.

Ideal State

  • Every answer rests on measures that actually ran (the pattern catalog, StatSignals.ts, a recorded Pangram run, WatermarkScan.ts), and the report names which ran and which did not.
  • A plain "is this AI?" with a key configured gets the heuristic audit and the Pangram score side by side, and where they disagree the report says what the gap means.
  • No report treats one signal as proof of authorship: scores carry their length and baseline caveats, and a clean watermark scan is never read as "human-written".
  • The text under review is reported on, never rewritten.

Intent Routing

Intent Trigger File
Detect "scan for AI tells", "flag AI patterns", "does this sound like AI", "audit this for AI-isms", "statistical signals", "burstiness", "entropy" — heuristic + deterministic statistical pass, no key needed Intents/Detect.md
Score "score this for AI", "is this AI generated", "AI detection score", "pangram", "compare these drafts" — empirical, needs key Intents/Score.md
Watermark "is this watermarked", "detect a watermark", "scan for hidden/invisible characters", "steganography", "zero-width chars" — keyless byte-level signature scan, no key needed Intents/Watermark.md

"Is this watermarked?" routes to Watermark, which answers a different question: whether a covert channel is embedded in the bytes, not whether the prose reads as AI. For "is this AI and is it marked?", run Score plus Watermark.

File Read when
Setup.md getting or storing the Pangram key, credits and rates, troubleshooting 401/402/429 or a stalled task

Data & Config

Detect and Watermark need no setup. Score needs PANGRAM_API_KEY in ~/.claude/.env (prepaid credits, about $0.05 per 1,000 words); key, credits, verification and troubleshooting are in Setup.md.

Gotchas

  • Never degrade writing to beat a detector. Injected typos, broken sentences, and "humanizer" laundering damage the prose and don't fix the underlying problem. If text must read human, the fix is a human in the loop.

Examples

  • "Scan this post for AI tells, don't change it" → Detect: tiered P0/P1/P2 flag report, each marked clear-problem vs judgment-call, no edits.
  • "Is this AI generated?" → Score: single Pangram run, headline verdict plus AI/AI-assisted/human percentages, with the length caveat stated if the sample is short.
  • "Which of these three drafts reads most human?" → Score in batch-compare mode: one call per draft, ranked table, relative comparison foregrounded over absolute numbers.
  • "Did my rewrite actually help?" → Score before and after, with two known-human passages scored in the same batch as calibration.

Workflows & Routing · 3

Each workflow is one job the skill runs. The trigger phrases route your request to the right one — this is the skill's routing table.

  1. 01
    Detect Intents/Detect.md

    scan for AI tells, flag AI patterns, does this sound like AI, audit this for AI-isms, statistical signals, burstiness, entropy — heuristic + deterministic statistical pass, no key needed

  2. 02
    Score Intents/Score.md

    score this for AI, is this AI generated, AI detection score, pangram, compare these drafts — empirical, needs key

  3. 03
    Watermark Intents/Watermark.md

    is this watermarked, detect a watermark, scan for hidden/invisible characters, steganography, zero-width chars — keyless byte-level signature scan, no key needed

How to Invoke

Say any of these to your DA and LifeOS activates the DetectAI skill automatically:

  • "detect AI writing"
  • "is this AI"
  • "AI detection"
  • "AI detector"
  • "did an AI write this"
  • "does this sound like AI"
  • "pangram"
  • "scan for AI tells"
  • "AI-isms"
  • "burstiness"
  • "is this watermarked"

Or invoke explicitly:

Skill("DetectAI")

References · 1

Auxiliary files the skill loads at runtime — frameworks, guides, configs.

  • Setup

Want LifeOS to do this for you?

Install LifeOS on your machine — your DA gets the DetectAI skill plus 96 others, all hooked into one Life OS.