agentleFS
joshua-zyyjoshua-zyy/academic-paper-writer/skills/academic-polishing/SKILL.md

academic-polishing

Skill111 starsChanged 5 months agoMITView on GitHub

Polish academic prose, de-AI-ify text, control claim strength, or rewrite method sections for CS/AI/ML papers. Executes Prose Quality Gate, Claim Strength Audit, and de-AI pass. Use when: removing AI writing patterns from paper text, adjusting claim strength to match evidence level, rewriting method sections with proper narrative flow, improving academic writing quality, checking for overclaiming. Triggers on: 润色, polish, improve writing, 去AI, de-AI, claim strength, 改写, rewrite method, prose quality, 降级表述, remove AI patterns, academic writing polish, 学术润色, 去AI化, 降级结论, improve prose.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. zieang88888/zhskills★ 1same 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 repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read manifest.yaml. It declares always_load files, axes, and references.on_demand.

    line 12
  2. Very specific:

    Read every file listed under always_load.

    line 13
  3. Very specific:

    Structural debt is not language debt: If section_contract_debt = open, only apply local safe edits and return the diagnosis.

    line 23

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

Academic Polishing

将此 skill 视为"学术文体打磨代理"——不是简单润色,而是执行 prose 质量闸门、去AI化改写、claim 强度控制和 Method 专项叙事强化。

Router Protocol

  1. Read manifest.yaml. It declares always_load files, axes, and references.on_demand.
  2. Read every file listed under always_load. These are the skill's binding rules — not reference material.
  3. Apply the loaded material as constraints:
    • stance.md defines non-negotiable rules, AI Traffic Light, claim strength, evidence-aware boundary, and scope.
    • red-lines.md defines absolute prohibitions. Do not negotiate these.
    • output-contract.md defines deliverables and completion criteria per mode.
    • anti-patterns.md defines known failure modes and their correct alternatives.
  4. Detect the mode using the manifest's mode axis. If ambiguous, ask one concise question.
  5. Echo the selected mode to the user before executing.
  6. Reach for references/ only when the manifest's references.on_demand condition is satisfied.

Structural debt is not language debt. If section_contract_debt = open, only apply local safe edits and return the diagnosis.

Modes

ModeUse when
prose-quality-gateGeneral prose quality check + rewrite
method-prose-rewriteMethod section narrative: 问题→设计→机制→收益/边界
de-ai-passRemove AI writing patterns only
claim-strength-auditAudit and adjust claim strength

Execution

Called internally by academic-paper-writer orchestrator at Step 9.6. The main agent reads this file and references/ to execute polishing in-process (no subagent dispatch). Polishing must not modify project source code, configuration, or data files. Max 2 rewrite rounds.

Independent Use

InputModePriorityBehavior
"润色一下", "改改语言"prose-quality-gate2 (fuzzy)Quality gate + rewrite, max 2 rounds
"去掉 AI 味", "不像人类写的"de-ai-pass2 (fuzzy)AI pattern removal only
"claim 太强了", "降级结论"claim-strength-audit2 (fuzzy)All claims audited, zero-tolerance check
"改写 Method", "Method 写得太潦草"method-prose-rewrite2 (fuzzy)Method narrative: problem→design→mechanism→benefit/boundary
Explicit mode nameas specified1 (explicit)Skip inference, use specified mode
ScenarioRecommended
Just polish/de-AI textThis skill (standalone)
Auto-polish during draftingacademic-paper-writer orchestrator (Step 9.6)
After revision reviewacademic-reviser → this skill

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.