Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Lylll9436/Paper-Polish-Workflow-skill --skill ppw-logicgit clone --depth 1 https://github.com/Lylll9436/Paper-Polish-Workflow-skillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/lylll9436/paper-polish-workflow-skill/ppw-logic)<a href="https://agentmods.dev/skills/lylll9436/paper-polish-workflow-skill/ppw-logic"><img src="https://agentmods.dev/badge/skills/lylll9436/paper-polish-workflow-skill/ppw-logic/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lylll9436/paper-polish-workflow-skill/ppw-logic"><img src="https://agentmods.dev/badge/skills/lylll9436/paper-polish-workflow-skill/ppw-logic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00060 | $0.03525 |
| Opus 5 | $0.00030 | $0.01762 |
| Sonnet 5 | $0.00012 | $0.00705 |
| Haiku 4.5 | $0.00006 | $0.00352 |
Grade A, and why
ppw:logic scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
This Skill reads a full academic paper and verifies logical consistency across its sections. It identifies four types of issues — argument chain gaps (AC-), unsupported claims (UC-), terminology inconsistencies (TI-), and number contradictions (NC-) — and produces a two-part bilingual report. Part 1 maps each section's primary claim as an Argument Chain View table, showing how claims connect (or fail to connect) from Introduction through Conclusion. Part 2 categorizes every identified issue with a problem description, an impact statement, and a one-sentence directional suggestion, each followed by an inline Chinese translation. The Skill never rewrites text; it identifies and suggests only.
Core Prompt
Source: awesome-ai-research-writing — 逻辑检查
# Role
你是一位负责论文终稿校对的学术助手。你的任务是进行"红线审查",确保论文没有致命错误。
# Task
请对我提供的【英文 LaTeX 代码片段】进行最后的一致性与逻辑核对。
# Constraints
1. 审查阈值(高容忍度):
- 默认假设:请预设当前的草稿已经经过了多轮修改与校正,质量较高。
- 仅报错原则:只有在遇到阻碍读者理解的逻辑断层、引起歧义的术语混乱、或严重的语法错误时才提出意见。
- 严禁优化:对于"可改可不改"的风格问题、或者仅仅是"换个词听起来更高级"的建议,请直接忽略,不要通过挑刺来体现你的存在感。
2. 审查维度:
- 致命逻辑:是否存在前后完全矛盾的陈述?
- 术语一致性:核心概念是否在没有说明的情况下换了名字?
- 严重语病:是否存在导致句意不清的中式英语(Chinglish)或语法结构错误。
3. 输出格式:
- 如果没有上述"必须修改"的错误,请直接输出中文:[检测通过,无实质性问题]。
- 如果有问题,请使用中文分点简要指出,不要长篇大论。
Trigger
Activates when the user asks to:
- Check, verify, or find logical problems in their paper
- 检查论文逻辑、验证论证链、帮我找逻辑问题
Example invocations:
- "Check the logic of my paper" / "检查我的论文逻辑"
- "Verify argument chain across sections" / "验证论文各章节论证是否自洽"
- "Find logical inconsistencies in my draft" / "帮我找论文里的逻辑问题"
Modes
| Mode | Default | Behavior |
|---|---|---|
direct |
Yes | Single-pass full-paper analysis, no intermediate confirmation steps |
batch |
Not supported — cross-section logic verification requires full-paper context |
Default mode: direct. User provides the paper and receives a complete two-part logic report.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 317 lines · 60 tokens per session scan A e76a5941e34b
ppw:logic is a skill published in the GitHub repository Lylll9436/Paper-Polish-Workflow-skill (386 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 3,525 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…