SkillAgentSearch skills...

ai-check

Use when someone asks "does this sound AI?", "check if this is AI-written", "what gives this away as AI", "run ai-check on this", or "score this text".

Install / Use

npx skills add harshaneel/humanize --skill ai-check

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Category

Marketing

Supported Platforms

Universal

Our assessment of ai-check

ai-check scores 88/100 on our quality scale, 336th of 645 Marketing skills we index.

Its SKILL.md is 26 KB long, well organised into 17 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

It has 496 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
17/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so ai-check is actively maintained.
  • Our last check on 2026-11-01 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

ai-check compared with similar skills

All 4 of these similar skills score higher than ai-check; compare them before choosing.

SkillScoreStarsUpdatedFormat
ai-check (this skill)by harshaneel8849656d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md
prospectingby coreyhaines3110060.1k6d agoSKILL.md
ad-creativeby coreyhaines3110060.1k6d agoSKILL.md

Frequently asked questions

How do I install ai-check?
Run npx skills add harshaneel/humanize --skill ai-check. The install tabs above show the steps for each supported agent.
Which AI agents does ai-check work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is ai-check safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is ai-check still maintained?
The repository was last updated about 2 months ago, so ai-check is actively maintained.

name: ai-check description: > Use when someone asks "does this sound AI?", "check if this is AI-written", "what gives this away as AI", "run ai-check on this", or "score this text". Also use when reviewing a draft for AI tells before publishing, or when a piece of text reads as suspiciously polished, generic, or pattern-y and the user wants a forensic breakdown of why.

AI-Check Skill

Forensic analysis of text for AI-generation signals. Grounded in the published detection literature (Wu et al. 2025, Mitchell et al. 2023, Kujur 2025, AAAI 2025 shared task).

The output is a structured report, not a vague judgment. Every fired signal cites evidence.


The nine signal categories

Score each category 0–3:

  • 0 = No signal detected (human-consistent)
  • 1 = Weak signal (possible AI, could be human)
  • 2 = Moderate signal (likely AI pattern)
  • 3 = Strong signal (near-certain AI pattern)

Severity-to-score mapping (use for every category):

| Evidence in category | Score | |---|---| | No flagged instances | 0 | | One weak instance, or vague unease without a specific quote | 1 | | One moderate instance, or two or more weak instances | 2 | | One strong instance, or two or more moderate instances, or four or more weak instances | 3 |

Double-counting policy: a single phrase can fire at most two distinct signals when the phrase is genuinely diagnostic for both. Example: "it is important to note that" is both Signal A (banned vocabulary) and Signal C (institutional hedge). Log it under both, but the same phrase cannot count as two separate weak instances inside the same category.

Total score cap: 9 categories × 3 = 27 maximum.

Signal A: Perplexity (word predictability)

Look for vocabulary that is maximally safe and expected — words that are technically correct but never the most precise or interesting choice a knowledgeable human would make.

Flags:

  • Generic verbs where domain-specific ones belong ("address" instead of "untangle", "implement" instead of "wire up")
  • Adjectives that describe without adding information ("significant improvements", "notable progress", "key challenges")
  • Hedged assertions that swap specificity for safety ("can often lead to", "may result in", "tends to")
  • Any of the canonical AI vocabulary list: delve, leverage (verb), utilize, robust, comprehensive, streamline, foster, facilitate, pivotal, nuanced, notable, notably, enduring, garner, it is worth noting, it is important to note, multifaceted, in the realm of, the landscape of, a myriad of, a plethora of

Cite the exact word or phrase that fired.

Signal B: Burstiness deficit (sentence uniformity)

Measure the variation in sentence length across the text.

Flags:

  • Three or more consecutive sentences within 5 words of the same length
  • No sentence shorter than 8 words in any 150-word block
  • Metronomic rhythm — reading the passage aloud produces a steady pulse rather than natural variation
  • No fragments used for emphasis

Report: list the sentence lengths in sequence (e.g. "14, 16, 13, 15, 17 — five consecutive sentences within 4 words of each other").

Signal C: Hedge density

Count the softening and epistemic hedge words.

Flags:

  • "often", "generally", "typically", "in many cases", "it can be argued" appearing where direct assertion is warranted
  • "it is important to note that", "it is worth mentioning", "one might consider"
  • Diplomatic framing of obvious tradeoffs: "while X has benefits, it also presents challenges"
  • Uncertainty expressed as institutional hedging rather than personal ("results may vary") vs human ("I'm not sure this holds when...")

Report: quote each hedge and note whether it was warranted by genuine uncertainty or reflexive softening.

Signal D: Structural tells

Look for document architecture patterns AI imposes regardless of content.

Flags:

  • Bullet list where prose would serve better
  • Topic sentence + evidence + restatement of topic sentence (humans skip the restatement)
  • "In conclusion / To summarize / In summary" openers on closing paragraphs
  • "In this [post/article/section] I will..." openers
  • Numbered steps for content that isn't genuinely sequential
  • Three-part structure imposed on every paragraph (intro, body, conclusion at micro-scale)
  • Tricolon parallel structure: three examples or beats with identical grammatical shape e.g. "You X. Y. Does Z? You X. Y. Does Z? You X. Y. Does Z?" — perfectly symmetrical triplets in prose are AI-constructed. Real writers use two examples or vary the shape. Severity: strong.
  • Perfect paragraph-per-idea arc: every paragraph does exactly one narrative job and advances the arc cleanly (setup → tension → lesson → evidence → reflection). Real personal writing has a paragraph that meanders, does two jobs, or doesn't fully resolve. A piece where every paragraph lands cleanly is architecturally perfect in a way human writing isn't. Severity: moderate in isolation, strong combined with other signals.
  • Three-act Slack/update structure: for informal async messages, accomplishment → caveat → next steps maps directly to intro/body/conclusion. Real updates loop back, add a mid-message second thought, or end with something that doesn't fit the structure.
  • Strawman pivot: "The case for X isn't about Y, it's about Z" / "It's not about X, it's about Y." Leading with what something is NOT before saying what it IS. Real writers lead with the actual point. Severity: moderate.

Signal E: Specificity deficit

Measure whether claims are grounded in concrete detail.

Flags:

  • Abstract claim with no number, name, time reference, or example: "Many organizations have adopted..."
  • Passive constructions obscuring the actor: "it has been found that", "research suggests"
  • Universalist framing: "teams often find", "developers frequently encounter" (applicable to everyone, specific to no one)
  • Named examples that are suspiciously generic or perfectly illustrative (AI picks canonical examples: "Netflix", "Amazon", "Stripe" without context)

Report: quote each unanchored claim.

Signal F: Transition word fingerprint

Catalog the connective tissue between sentences and paragraphs.

Flags (strong AI signals):

  • "Furthermore," as paragraph opener
  • "Moreover," as paragraph opener
  • "Additionally," as paragraph opener
  • "It is clear that"
  • "This highlights / underscores / demonstrates the importance of"
  • "As previously mentioned"
  • "In addition to the above"
  • "It goes without saying"
  • "Needless to say"

Flags (moderate signals):

  • "However," used more than once per 200 words
  • "Therefore," used as a mechanical logical connector rather than earned conclusion
  • "Turns out" / "it turns out that" as a pivot or reveal. AI uses this to create the illusion of a discovery narrative. "Turns out the config had a lower timeout" → "The config had a lower timeout." Quote each instance. Severity: moderate.
  • Tutorial-voice transitions: "The standard fix is...", "The common approach is...", "Simple enough on paper" — these frame what follows as received wisdom, not personal experience. Strong signal in technical writing.
  • Announcement-colon patterns: "The rule I use:", "The key insight:", "The approach here:", "The other thing I'd say:" — announcing before revealing. Severity: moderate. Also fires without a colon: "What I didn't expect was...", "What surprised me was...", "The thing I realized was..." — these are announcement sentences even without the colon. The colon isn't the tell; the announcement structure is.
  • Pattern announcement: stating that a pattern exists before describing it. "The pattern is almost always the same" followed by the pattern. Real writers just describe the pattern.

Signal G: Punctuation fingerprint

Count the three AI punctuation tells:

Em dashes: Count total em dashes. More than 1 per 300 words is a signal. Specific sub-patterns:

  • Double em dash wrapping (— like this —) is a near-certain AI pattern
  • Em dash as pivot ("not mid-sprint — and the on-call rotation") — list-joiner em dash connecting two items within a sentence
  • Em dash as dramatic aside ("X — which is worth noting — Y") Report exact count, location, and which sub-pattern.

Semicolons: Any semicolon linking two independent clauses in non-academic prose is a flag. Report exact count. Exception: comma-containing lists ("Austin, TX; Denver, CO").

Mid-sentence colons: A colon preceded by an incomplete clause ("The problem: nobody tests this" / "The answer: start earlier") is an AI structural pattern. Report each instance.

Signal H: Voice and register

Look for absence of human traces.

Flags:

  • No first-person perspective anywhere in a piece where first-person would be natural
  • No second-person direct address in instructional or opinionated content
  • Consistent "polished neutral tone" — no personality variance, no roughness, no informality spikes
  • No rhetorical questions used as transitions
  • No self-correction or mid-thought qualification ("actually, that's not quite right")
  • Opening sentence is a thesis, definition, or contextual framing rather than mid-thought or scene

Register collapse (Slack / informal writing): The most commonly missed signal in casual-register text. AI writes Slack messages that read like polished status reports with informal markers sprinkled in. Look for:

  • Complete, well-formed sentences throughout — real Slack has fragments
  • Topic-per-paragraph structure even in a short message
  • Formal vocabulary underneath casual markers (~60% and lmk but the sentences themselves are well-constructed prose)
  • No self-corrections mid-message ("oh also. just realized...")
  • Three-act arc (accomplishment / caveat / next steps) intact beneath the informality
  • Numbers written as words ("three incidents") rather than numerals with approximations ("~3 incidents", "<10min") Severity: strong when informal markers are present but prose structure is polished.

Templated closers in email/professional writing: "Happy to jump on a call if that's easier." "Let me know if you have any questions." "Feel free to reach out." These are the written equivalent of a throat-clearing opener. Real engineers end emails after the last substantive point, or with a specific ask, or with "lmk." Severity: weak in isolation, moderate when combined with other signals.

Signal I: Rhetorical scaffolding

Sentence and paragraph-level construction patterns that AI learned from polished writing and applies too consistently. These are the hardest signals to catch — they feel like good writing. Grammarly and live detectors flag these even when punctuation and vocabulary are clean.

Local coherence over-smooth (severity: moderate-strong, corpus-dependent) A pattern related to findings in recent research (DivEye, arXiv 2509.18880, TMLR 2026): every sentence connects too perfectly to the next, zero friction, zero cognitive-load artifacts. AI text often has no sentences that slightly misfire, no thoughts that shift direction mid-clause, no paragraph that doesn't close cleanly. Evidence: read each paragraph and check whether any sentence could be removed and the paragraph would still read perfectly. In human writing, removing a sentence often creates a noticeable gap. In AI writing, the paragraph usually flows better without it. Symptoms:

  • Every paragraph opens with a claim and closes with a confirmation of that claim
  • No sentence has a vocabulary mismatch with surrounding sentences
  • No abrupt topic shift within a paragraph
  • No sentence that slightly misfires before correcting

Calibration caveat (important). SHAP-based explainability analysis (arXiv 2603.23146) found that AI-text detectors rely on dataset-specific stylistic cues, not stable machine-authorship signals. Treat over-smoothness as a corpus-conditional indicator, not a universal authorship invariant. If the text is from a register that genuinely rewa

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars496
CategoryMarketing
Updated1mo ago
Forks51

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions