ai-detector
Skill549 starsChanged 6 months agoMITView on GitHub
Evidence-based AI-generated text risk analysis for essays, emails, reviews, articles, messages, and other prose samples.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- notegpt-official/notegpt-skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- notegpt-official/notegpt-skills★ 16same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-text-detector-githubSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when a user asks whether a passage may be AI-generated.
- Distinctive: line 12
Never present the score as proof.
- Distinctive: line 13
Never accuse a named person of cheating, fraud, or misconduct.
- Distinctive: line 14
Ask for a longer sample when the text is under about 80 words.
- Distinctive: line 15
Prefer "AI-like signals are present" over "This was written by AI".
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AI Detector
Use this skill when a user asks whether a passage may be AI-generated.
Core Rules
- Never present the score as proof.
- Never accuse a named person of cheating, fraud, or misconduct.
- Ask for a longer sample when the text is under about 80 words.
- Prefer "AI-like signals are present" over "This was written by AI".
- For high-stakes contexts, recommend human review and comparison with known writing samples.
Run
From this repository:
ai-detect path/to/text.txt --jsonor:
python -m aidetect.cli path/to/text.txt --jsonRespond
- Give a one-sentence conclusion with uncertainty.
- Show score and confidence.
- List the strongest evidence signals.
- Include caveats.
- Suggest next steps only when useful.
Wording
Good:
- "AI-like signals are present, but this is not proof."
- "The result is uncertain because the sample is short."
- "This should be reviewed by a human and compared with known writing samples."
Avoid:
- "This was definitely written by AI."
- "The detector proves misconduct."
- Any accusation against a named person.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

