Token导航 LogoToken导航

Agent Skill · 研究检索

ai-writing-detection(AI 书写检测)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

ai-writing-detection 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 28,131。

总安装 3,269周安装 139GitHub Stars 16下载 1,145核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ai-writing-detection(AI 书写检测)
来源仓库:https://github.com/mike-coulbourn/claude-vibes
仓库路径:skills/ai-writing-detection
安装命令:
npx skills add https://github.com/mike-coulbourn/claude-vibes --skill ai-writing-detection
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/mike-coulbourn/claude-vibes --skill ai-writing-detection

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

提供 AI 生成文本的专业级检测知识库和信号参考。包含词汇特征、句式模式和语义异常等识别指标。适用于学术诚信、内容审核和原创性验证等场景。需结合上下文综合判断,避免单一信号误判。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

ai-writing-detection 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/ai-writing-detection

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/mike-coulbourn/claude-vibes --skill ai-writing…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

ai-writing-detection 怎么安装?

在终端执行 npx skills add https://github.com/mike-coulbourn/claude-vibes --skill ai-writing-detection。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ai-writing-detection 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

ai-writing-detection 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

ai-writing-detection 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

ai-writing-detection 用的人多吗?

公开数据是累计安装 3,269 次,近一周安装 139 次,下载 1,145 次,GitHub 16 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

ai-writing-detection 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
ai-writing-detection

AI 书写检测 · 本页

3,26916需要联网MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

AI Writing Detection Reference

Expert-level knowledge base for detecting AI-generated text, compiled from academic research, commercial detection tools, and empirical analysis.

Quick Reference: High-Confidence Signals

These indicators strongly suggest AI authorship when found together:

Vocabulary Red Flags

High-signal words (50-700x more common in AI text):

  • "delve", "tapestry", "nuanced", "multifaceted", "underscore"
  • "intricate interplay", "played a crucial role", "complex and multifaceted"
  • "paramount", "pivotal", "meticulous", "holistic", "robust"
  • "stands/serves as", "marking a pivotal moment", "underscores its importance"

Overused phrases:

  • "It's important to note that..."
  • "In today's fast-paced world..."
  • "At its core..."
  • "Without further ado..."
  • "Let me explain..."

See reference/vocabulary-patterns.md for complete lists.

Structural Red Flags

  • Uniform sentence lengths: 12-18 words consistently (low burstiness)
  • Tricolon structures: "research, collaboration, and problem-solving"
  • Em dash overuse: AI uses em dashes in a formulaic way to mimic "punched up" sales writing, especially in parallelisms ("it's not X — it's Y"); swapping punctuation doesn't fix the underlying emphasis pattern
  • Perfect paragraph uniformity: All paragraphs same approximate length
  • Template conclusions: "In summary...", "In conclusion..."
  • Negative parallelisms: "It's not about X; it's about Y"
  • Elegant variation: Cycling through synonyms to avoid repetition
  • False ranges: "From X to Y" with incoherent endpoints

See reference/structural-patterns.md for details.

Content Red Flags

  • Importance puffery: "marking a pivotal moment in history"
  • Ecosystem/conservation claims without citations
  • "Challenges and Future" sections following rigid formula
  • Promotional language: "nestled in", "stunning natural beauty", "boasts"
  • Superficial analyses: "-ing" phrases attributing significance to facts

See reference/content-patterns.md for details.

Formatting Red Flags

  • Title Case in all section headings
  • Excessive boldface (every key term bolded)
  • Inline-header lists: **Bold Header**: description pattern
  • Emojis in formal content or headings
  • Subject lines in non-email contexts

See reference/formatting-patterns.md for details.

Markup Red Flags (Definitive)

  • turn0search0, turn0image0: ChatGPT reference markers
  • contentReference[oaicite:]: ChatGPT reference bugs
  • utm_source=chatgpt.com: URL tracking (definitive)
  • Markdown in wikitext: ## headers, bold, text
  • grok_card XML tags: Grok/X specific

See reference/markup-artifacts.md for details.

Citation Red Flags

  • Broken external links that never existed (no archive)
  • Invalid DOIs/ISBNs: Checksum failures
  • Declared but unused references: Cite errors
  • Placeholder values: url=URL, date=2025-XX-XX

See reference/citation-patterns.md for details.

Tone Red Flags

  • Passive and detached voice throughout
  • Absence of first-person pronouns where expected
  • Consistent formality with no stylistic variation
  • Over-politeness and excessive hedging

Detection Methodology

Multi-Layer Analysis Approach

Layer 1: Technical Artifact Scan (Definitive)

  • Check for turn0search/oaicite markers (ChatGPT)
  • Check for utm_source=chatgpt.com in URLs
  • Check for grok_card tags (Grok)
  • Check for Markdown in non-Markdown contexts
  • If found: Definitive AI involvement

Layer 2: Vocabulary Pattern Matching

  • Scan for overused AI words/phrases
  • Count frequency of flagged terms
  • Look for clusters of high-signal vocabulary
  • Check for importance/symbolism phrases

Layer 3: Structural Analysis

  • Observe sentence length variation (uniform = AI signal)
  • Check paragraph uniformity
  • Identify repetitive syntactic templates (tricolons, negative parallelisms)
  • Look for elegant variation (synonym cycling)
  • Check for false ranges

Layer 4: Content Pattern Analysis

  • Check for importance puffery and promotional language
  • Look for "Challenges and Future" formula
  • Check for ecosystem/conservation claims without citations
  • Identify superficial analyses with "-ing" attributions

Layer 5: Citation Verification

  • Test external links - do they exist?
  • Verify DOI/ISBN checksums
  • Check for declared but unused references
  • Look for placeholder values

Layer 6: Formatting Analysis

  • Check heading capitalization (Title Case = signal)
  • Count bold phrases per paragraph
  • Look for inline-header list patterns
  • Check for emojis in formal content

Layer 7: Stylometric Observation

  • Pronoun usage patterns (missing first-person?)
  • Tone consistency (too uniform = AI signal)
  • Punctuation patterns (em dash overuse? curly quotes?)

Layer 8: Coherence Check

  • Do paragraphs build a coherent argument?
  • Are concepts repeated with different words?
  • Do transitions actually connect ideas?

Layer 9: Confidence Scoring

  • Weight multiple signals together
  • Require corroborating evidence (3+ signals minimum)
  • Apply context-specific adjustments
  • Check for mitigating factors (human signals)
  • Consider ineffective indicators (don't use them)

Model-Specific Patterns

Different AI models have distinct "fingerprints":

ModelKey TellsTechnical Artifacts
ChatGPT/GPT-4"delve" (pre-2025), "tapestry", tricolons, em dashes, curly quotesturn0search, oaicite, utm_source=chatgpt.com
ClaudeAnalytical structure, extended analogies, cautious qualificationsNone (uses straight quotes, no tracking)
GeminiConversational synthesis, fact-dense paragraphsNone (uses straight quotes, no tracking)
DeepSeekSimilar to ChatGPT, curly quotesCurly quotation marks
GrokX/Twitter integration<grok_card> XML tags
PerplexitySource-focused output[attached_file:1], [web:1] tags

Important dates:

  • ChatGPT launched: November 30, 2022 (text before this is almost certainly human)
  • "delve" usage dropped: 2025 (still signals pre-2025 ChatGPT)

See reference/model-fingerprints.md for detailed model patterns.

False Positive Prevention

Critical requirements:

  • Minimum 200 words for reliable analysis
  • Never flag on single indicators alone
  • Use ensemble scoring (multiple signals required)

High false-positive risk groups:

  • Non-native English speakers (61% false positive rate in research)
  • Technical/formal writing
  • Neurodivergent writers
  • Content using grammar correction tools

Ineffective indicators (do NOT rely on these):

  • Perfect grammar alone
  • "Bland" or "robotic" prose
  • "Fancy" or unusual vocabulary
  • Letter-like formatting alone
  • Conjunctions starting sentences

Signs of human writing:

  • Text from before November 30, 2022
  • Ability to explain editorial choices
  • Personal anecdotes with verifiable details
  • Minor errors and natural quirks

See reference/false-positive-prevention.md for detailed guidance.

Analysis Output Format

Structure findings as:

**Overall Assessment**: [Likely AI / Possibly AI / Likely Human / Inconclusive]
**Confidence**: [Low / Medium / High]

**Summary**: 2-3 sentence overview

**Evidence Found**:
- [Category]: [Specific indicator] - "[Quote from text]"
- [Category]: [Specific indicator] - "[Quote from text]"

**Mitigating Factors**: [Elements suggesting human authorship]

**Caveats**: [Limitations, alternative explanations]

Key Principles

  1. No certainty claims - AI detection is probabilistic
  2. Multiple signals required - Single indicators prove nothing
  3. Context matters - Academic writing differs from blogs
  4. Stakes awareness - False accusations cause real harm
  5. Evolving field - Detection methods require constant updates

Reference Files

Sources

This knowledge base synthesizes research from:

  • Stanford HAI (DetectGPT, bias studies)
  • GPTZero, Originality.ai, Turnitin, Pangram methodologies
  • Academic papers on stylometry and discourse analysis
  • Empirical studies on detection accuracy and limitations
  • Wikipedia:WikiProject AI Cleanup field guide (2025)
  • Community-documented patterns from Wikipedia editing

平台分布

Claude Code

28.73%
按下载量换算329

OpenCode

24.89%
按下载量换算285

Gemini CLI

16.11%
按下载量换算184

Codex

11.59%
按下载量换算133

Antigravity

8.38%
按下载量换算96

Cursor

3.18%
按下载量换算36

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills