agentleFS
lynote-ailynote-ai/ai-text-detector/SKILL.md

ai-text-detector-github

Skill549 starsChanged 6 months agoMITView on GitHub

Detect whether a passage shows AI-like writing signals and return an explainable risk estimate with confidence, caveats, and next steps.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    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
  1. Distinctive:

    Use this skill when:

    line 25
  2. Distinctive:

    Never present the score as proof.

    line 34
  3. Distinctive:

    Never accuse a named person of cheating, fraud, or misconduct.

    line 35
  4. Distinctive:

    Ask for a longer sample when the text is under about 80 words.

    line 36
  5. Distinctive:

    Prefer "AI-like signals are present" over "This was written by AI".

    line 37
  6. Distinctive:

    If the sample is under about 80 words, explain that the detector will be noisy and ask for a longer sample when possible.

    line 43
  7. Distinctive:

    Run the local detector:

    line 45
  8. Distinctive:

    Keep the analyzer explainable and lightweight.

    line 104
  9. Distinctive:

    Prefer local heuristics over hidden network calls.

    line 105
  10. Distinctive:

    Update this file whenever behavior or output changes.

    line 106

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AI Text Detector Skill

Overview

This skill wraps the local ai-detector-skill analyzer into a reusable open source Codex-style skill.

It is designed for:

  • essays
  • emails
  • articles
  • reviews
  • forum posts
  • other prose where a user asks whether the writing may be AI-generated

This skill returns a risk estimate, not proof of authorship.

Trigger Conditions

Use this skill when:

  • the user asks "is this AI-written?"
  • the user asks to detect AI-generated text
  • the user pastes a passage and asks whether it sounds machine-written
  • the user wants a cautious AI-likeness review for a document or message

Required Behavior

  • 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.

Execution Flow

  1. Receive the candidate text and check length.
  2. If the sample is under about 80 words, explain that the detector will be noisy and ask for a longer sample when possible.
  3. Save the text to a file or pipe it through stdin.
  4. Run the local detector:
ai-detect path/to/text.txt --json

or:

python -m aidetect.cli path/to/text.txt --json

or from the repository helper:

python scripts/detect.py path/to/text.txt --json
  1. Parse the JSON result and validate that it includes:
  • score
  • confidence
  • verdict
  • conclusion
  • signals
  • caveats
  1. Respond in this order:
  2. One-sentence conclusion with uncertainty.
  3. Score and confidence.
  4. Strongest evidence signals.
  5. Caveats.
  6. Next steps only when useful.

Output Guidance

Good phrasing:

  • "AI-like signals are present, but this is not proof."
  • "The result is uncertain because the sample is short."
  • "This should be reviewed against known writing samples."

Avoid:

  • "This was definitely written by AI."
  • "The detector proves misconduct."
  • Any accusation against a named person.

Repository Layout

  • SKILL.md: skill contract and usage rules
  • scripts/detect.py: repository-local wrapper for the detector
  • scripts/setup.sh: local environment bootstrap
  • references/api-reference.md: response contract and CLI reference
  • assets/templates/report.md: reusable response template

Development Notes

  • Keep the analyzer explainable and lightweight.
  • Prefer local heuristics over hidden network calls.
  • Update this file whenever behavior or output changes.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.