Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计未展示

ppw%3ade-aippw%3ade 艾

Agent Skill

ppw%3ade-ai 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

465

周安装

19

GitHub Stars

280

下载量

150
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:ppw%3ade-ai(ppw%3ade 艾)
来源仓库:https://github.com/lylll9436/paper-polish-workflow-skill
仓库路径:skills/ppw%3Ade-ai
安装命令:
npx skills add https://github.com/lylll9436/paper-polish-workflow-skill --skill ppw:de-ai
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/lylll9436/paper-polish-workflow-skill --skill ppw:de-ai

简介

ppw%3ade-ai 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 适用于研究检索类任务,可能与 AI 相关的内容分析或文献调研有关。
  • 可通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前建议确认权限范围和维护状态,避免触发联网或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Purpose

This Skill detects AI-generated patterns in English academic text and rewrites flagged passages with explainable, risk-tagged results. It scans text against three pattern dimensions (vocabulary inflation, sentence overclaims, transition smoothing) from the anti-AI patterns library, presents detections grouped by risk level (High Risk / Medium Risk / Optional), and lets users batch-select which items to rewrite. Rewrites restructure expressions rather than just swapping synonyms, preserving academic meaning and quality. For file input, edits are made in-place with LaTeX comment annotations for traceability; for pasted text, results appear in conversation.

Core Prompt

Source: awesome-ai-research-writing — 去 AI 味(LaTeX 英文)
# Role
你是一位计算机科学领域的资深学术编辑,专注于提升论文的自然度与可读性。你的任务是将大模型生成的机械化文本重写为符合顶级会议(如 ACL, NeurIPS)标准的自然学术表达。

# Task
请对我提供的【英文 LaTeX 代码片段】进行"去 AI 化"重写,使其语言风格接近人类母语研究者。

# Constraints
1. 词汇规范化:
   - 优先使用朴实、精准的学术词汇。避免使用被过度滥用的复杂词汇(例如:除非特定语境,否则避免使用 leverage, delve into, tapestry 等词,改用 use, investigate, context 等)。
   - 只有在必须表达特定技术含义时才使用术语,避免为了形式上的"高级感"而堆砌辞藻。

2. 结构自然化:
   - 严禁使用列表格式:必须将所有的 item 内容转化为逻辑连贯的普通段落。
   - 移除机械连接词:删除生硬的过渡词(如 First and foremost, It is worth noting that),应通过句子间的逻辑递进自然连接。
   - 减少插入符号:尽量减少破折号(—)的使用,建议使用逗号、括号或从句结构替代。

3. 排版规范:
   - 禁用强调格式:严禁在正文中使用加粗或斜体进行强调。学术写作应通过句式结构来体现重点。
   - 保持 LaTeX 纯净:不要引入无关的格式指令。

4. 修改阈值(关键):
   - 宁缺毋滥:如果输入的文本已经非常自然、地道且没有明显的 AI 特征,请保留原文,不要为了修改而修改。
   - 正向反馈:对于高质量的输入,应在 Part 3 中给予明确的肯定和正向评价。

5. 输出格式:
   - Part 1 [LaTeX]:输出重写后的代码(如果原文已足够好,则输出原文)。
     * 语言要求:必须是全英文。
     * 必须对特殊字符进行转义(例如:`%`、`_`、`&`)。
     * 保持数学公式原样(保留 `$` 符号)。
   - Part 2 [Translation]:对应的中文直译。
   - Part 3 [Modification Log]:
     * 如果进行了修改:简要说明调整了哪些机械化表达。
     * 如果未修改:请直接输出中文评价:"[检测通过] 原文表达地道自然,无明显 AI 味,建议保留。"
   - 除以上三部分外,不要输出任何多余的对话。

# Execution Protocol
在输出前,请自查:
1. 拟人度检查:确认文本语气自然。
2. 必要性检查:当前的修改是否真的提升了可读性?如果是为了换词而换词,请撤销修改并判定为"检测通过"。

AI 味高频词汇参考表:

Accentuate, Ador, Amass, Ameliorate, Amplify, Alleviate, Ascertain, Advocate, Articulate, Bear, Bolster,
Bustling, Cherish, Conceptualize, Conjecture, Consolidate, Convey, Culminate, Decipher, Demonstrate,
Depict, Devise, Delineate, Delve, Delve Into, Diverge, Disseminate, Elucidate, Endeavor, Engage, Enumerate,
Envision, Enduring, Exacerbate, Expedite, Foster, Galvanize, Harmonize, Hone, Innovate, Inscription,
Integrate, Interpolate, Intricate, Lasting, Leverage, Manifest, Mediate, Nurture, Nuance, Nuanced, Obscure,
Opt, Originates, Perceive, Perpetuate, Permeate, Pivotal, Ponder, Prescribe, Prevailing, Profound, Recapitulate,
Reconcile, Rectify, Rekindle, Reimagine, Scrutinize, Substantiate, Tailor, Testament, Transcend, Traverse,
Underscore, Unveil, Vibrant

Trigger

Activates when the user asks to:

  • Detect, scan, or check for AI-generated patterns in academic text
  • Rewrite or reduce AI traces in English writing
  • 降AI、检测AI痕迹、降低AI检测分数

Example invocations:

  • "De-AI this paragraph" / "降AI这段论文"
  • "Check my paper for AI patterns" / "AI检测并改写"
  • "Scan only -- just show detections" / "只扫描不改写"

Modes

ModeDefaultBehavior
directYesFull detect-then-rewrite two-phase workflow with batch selection
batchSame operation across multiple files with same settings

Default mode: direct. User says "de-AI this" and gets detect + rewrite.

Mode inference: "scan only", "just check", or "只检测" triggers detect-only (skip rewrite phase). "De-AI all sections" or "batch" switches to batch.

References

Required (always loaded)

FilePurpose
references/anti-ai-patterns.mdRisk model, category map, retrieval contract
references/expression-patterns.mdAcademic expression patterns for rewrite quality

Leaf Hints (loaded proactively for detection)

FileWhen to Load
references/anti-ai-patterns/vocabulary.mdAlways -- loaded proactively for full-text scan
references/anti-ai-patterns/sentence-patterns.mdAlways -- loaded proactively for full-text scan
references/anti-ai-patterns/transitions-and-tone.mdAlways -- loaded proactively for full-text scan

Leaf Hints (loaded during rewrite phase)

FileWhen to Load
references/expression-patterns/introduction-and-gap.mdRewriting introduction or background content
references/expression-patterns/methods-and-data.mdRewriting methods or data content
references/expression-patterns/results-and-discussion.mdRewriting results or discussion content
references/expression-patterns/conclusions-and-claims.mdRewriting conclusion content

Loading Rules

  • Load ALL three anti-AI pattern leaves proactively at the start for full-text scanning.
  • Load expression patterns overview at the start; load section-specific leaves during rewrite phase based on detected section type.
  • When a target journal is specified, also load references/journals/[journal].md. If template missing, refuse with message: "Journal template for [X] not found. Available: CEUS."
  • If an anti-AI pattern leaf is missing, warn the user and proceed with reduced detection coverage.

Ask Strategy

Before starting, ask about:

  1. Target journal (if not specified) -- determines style consideration during rewrite
  2. Scope: full paper or specific section (if ambiguous)

Rules:

  • In direct mode, skip pre-questions when the user provides enough context.
  • Never ask more than 2 questions before scanning.
  • Use Structured Interaction when available; fall back to plain-text questions otherwise.

Workflow

Step 0: Workflow Memory Check

  • Read .planning/workflow-memory.json. If file missing or empty, skip to Phase 1.
  • Check if the last 1-2 log entries form a recognized pattern with ppw:de-ai that has appeared >= threshold times in the log. See skill-conventions.md > Workflow Memory > Pattern Detection for the full algorithm.
  • If a pattern is found, present recommendation via AskUserQuestion:

- Question: "检测到常用流程:[pattern](已出现 N 次)。是否直接以 direct 模式运行 ppw:de-ai?" - Options: "Yes, proceed" / "No, continue normally"

  • If user accepts: set mode to direct, skip Ask Strategy questions.
  • If user declines or AskUserQuestion unavailable: continue in normal mode.

Phase 1: Detect

Step 1 -- Prepare:

  • Load all three anti-AI pattern leaves (vocabulary, sentence-patterns, transitions-and-tone).
  • If target journal specified, load journal template; if missing, refuse.
  • Read user input (file via Read tool, or pasted text from conversation).
  • Opt-out check: Scan the user's trigger prompt for any of these phrases (case-insensitive, exact phrase match): english only, no bilingual, only english, 不要中文. Store result as bilingual_mode (true/false). This flag governs Phase 2 bilingual output below.
  • Record workflow: Append {"skill": "ppw:de-ai", "ts": "<ISO timestamp>"} to .planning/workflow-memory.json. Create file as [] if missing. Drop oldest entry if log length >= 50.

Step 2 -- Scan:

  • Follow the Core Prompt constraints above as the primary instruction set for detection and rewrite.
  • Scan full text against all three pattern dimensions in a single pass.
  • For each match, check domain term protection: if the flagged term is standard domain terminology used in context (e.g., "landscape" in a geography paper, "robust" in a statistics paper), mark as SKIPPED with reason.
  • For Optional-tier matches: only flag if the pattern appears 3+ times in the text. Single occurrences are suppressed to reduce noise.

Step 3 -- Present Detection Report:

  • Summary line: "Found N AI patterns (X High Risk / Y Medium Risk / Z Optional)" plus count of skipped domain terms.
  • Detailed list grouped by risk level (High first, then Medium, then Optional). Each item shows:
[#N] [HIGH RISK] Vocabulary Inflation
  Original: "This groundbreaking approach transforms the analytical framework"
  Pattern: "groundbreaking" -- promotional, exaggerated vocabulary (vocabulary.md)
  Suggestion: "This useful approach improves the analytical framework"

Step 4 -- User Selection:

  • Ask which items to rewrite:

- "Fix all High Risk" - "Fix High + Medium" - "Fix all" - Specific items by number: "fix 1, 3, 7"

Phase 2: Rewrite

Step 1 -- Group and Rewrite:

  • Group selected items by paragraph. When multiple items appear in the same paragraph, rewrite them together in one pass to maintain coherence.
  • Load relevant expression pattern leaves based on section type for higher quality alternatives beyond the anti-AI replacement column.
  • Restructure expressions -- do not just swap synonyms. Preserve academic meaning and quality.
  • If target journal specified, consider journal style preferences during rewrite.

Step 2 -- Apply Changes:

  • File input: Use Edit tool for in-place modifications. Add % [De-AI] Original: <original text> LaTeX comment on the line immediately before each rewritten passage.

- Multi-line originals: each line gets its own % [De-AI] Original: prefix. - If existing % [De-AI] Original: annotations found, clean them up before adding new ones.

  • Pasted text: Present rewritten version in conversation with before/after comparison for each changed passage.

Step 3 -- Rewrite Report:

FieldContent
Total rewritesApplied N of M detected items
By categoryVocabulary inflation: count, Sentence overclaim: count, Transition smoothing: count
Skipped itemsOptional below threshold, domain terms protected
Word count delta+/- N words

Step 4 -- Bilingual Display:

  • If bilingual_mode is true and input was a file: for each paragraph that was rewritten in Step 1, display a > **[Chinese]**... blockquote in conversation showing the Chinese translation of the rewritten English text.
  • Use a section header in conversation: "双语对照 / Bilingual Comparison:" before the first blockquote.
  • Format per paragraph: [Chinese] [Chinese translation of the rewritten paragraph]
  • Do not insert Chinese into the.tex file. The file remains English-only and submission-ready.
  • If bilingual_mode is false (opt-out detected): skip this step entirely.
  • Pasted text input: if bilingual_mode is true, append the > **[Chinese]**... blockquote immediately after each rewritten paragraph in the conversation diff output.

Step 5 -- Summary:

  • If further polishing is needed, recommend: "Consider running the Polish Skill for additional refinement."

LaTeX Annotation Format

  • Format: % [De-AI] Original: <original text> on the line immediately before the replacement.
  • Multi-line originals: each line gets its own % [De-AI] Original: prefix.
  • Annotations are valid LaTeX comments -- the file compiles with them present.
  • Cleanup: after user confirms acceptance, remove all lines matching ^% \[De-AI\] Original:.
  • If existing % [De-AI] Original: annotations are found, clean them up before adding new ones.

Output Contract

OutputFormatCondition
Detection reportStructured markdown (summary + detailed list)Always (Phase 1)
Rewritten textIn-place LaTeX with annotations (file) or conversation diff (pasted)Phase 2
Rewrite reportStructured markdown tableAfter Phase 2
Word count deltaIntegerAfter Phase 2
bilingual_conversation> **[Chinese]**... blockquotes in sessionPhase 2 rewritten paragraphs only. Skipped when opt-out detected.

Edge Cases

SituationHandling
No AI patterns detectedReport "No AI patterns detected" and exit; do not proceed to rewrite
Input too short (< 3 sentences)Warn detection may be unreliable on short text; proceed if user confirms
All detections are domain terms (all skipped)Report "N patterns matched but all identified as domain terminology -- no rewrites needed"
Existing % [De-AI] Original: annotationsClean up old annotations before running new scan
Input language is not EnglishWarn and suggest running Translation Skill first
Journal template missing when journal specifiedRefuse: "Journal template for [X] not found. Available: CEUS."
Very long input (10+ pages)Process in sections; maintain cross-section awareness

Fallbacks

ScenarioFallback
Structured Interaction unavailableAsk 1-2 plain-text questions (journal + scope)
Anti-AI pattern leaf missingWarn user, proceed with available modules (reduced detection coverage)
Expression pattern leaf missingUse overview entrypoint for general rewrite patterns
Target journal not specifiedAsk once; if declined, use general academic style for rewrites
File is read-only or Edit failsPresent changes as a diff in conversation; user applies manually

*Skill: de-ai-skill* *Conventions: references/skill-conventions.md*

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.77%
按下载量换算55

Claude

28.8%
按下载量换算43

Cursor

18.95%
按下载量换算28

Gemini CLI

9.23%
按下载量换算14

安全审计

暂无安全审计结果可展示。

权限和风险

需要联网

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills