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-cover-lettergit 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-cover-letter)<a href="https://agentmods.dev/skills/lylll9436/paper-polish-workflow-skill/ppw-cover-letter"><img src="https://agentmods.dev/badge/skills/lylll9436/paper-polish-workflow-skill/ppw-cover-letter/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-cover-letter"><img src="https://agentmods.dev/badge/skills/lylll9436/paper-polish-workflow-skill/ppw-cover-letter.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.00055 | $0.02246 |
| Opus 5 | $0.00028 | $0.01123 |
| Sonnet 5 | $0.00011 | $0.00449 |
| Haiku 4.5 | $0.00006 | $0.00225 |
Grade A, and why
ppw:cover-letter 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
This Skill generates complete, submission-ready academic cover letters by loading the target journal's template to align the contribution statement with journal scope and aims, collecting correspondence author details via Ask Strategy, and reading the paper (file or pasted text) to extract the paper title, key contribution, and data availability information. Output is a full letter with all four required content blocks: (1) contribution statement — explicitly aligned with the journal's stated scope from the loaded template; (2) data/code availability statement; (3) conflict of interest declaration; (4) correspondence author contact block. If the journal template is not found, the Skill refuses immediately — it never falls back to generic academic prose, consistent with the journal-aware pattern used throughout this project.
Trigger
Activates when the user asks to:
- Write, generate, or draft a cover letter or submission letter for a paper
- 写投稿信、生成cover letter、帮我写投稿信
Example invocations:
- "Write a cover letter for my CEUS submission"
- "帮我写投稿信"
- "Generate a cover letter for my paper"
- "写一封投稿到CEUS的cover letter"
- "Help me draft a submission cover letter"
- "帮我生成这篇论文的投稿信"
Modes
| Mode | Default | Behavior |
|---|---|---|
direct |
Yes | Single-pass letter generation; all context collected upfront via Ask Strategy |
batch |
NOT supported — each letter requires specific paper context and author details |
Default mode: direct. User provides a paper and journal; Skill collects any missing details and generates the complete letter in one pass.
References
Required (always loaded)
None.
Leaf Hints (loaded conditionally)
| File | When to Load |
|---|---|
references/journals/ceus.md |
When user targets CEUS; provides Aims & Scope, scope keywords for contribution alignment |
Loading Rules
- When journal is specified, load
references/journals/[journal].md. - If template not found: refuse immediately with: "Journal template for [X] not found. Available: CEUS."
- Do NOT proceed with generic framing if template is missing.
- Extract the Aims & Scope section from the loaded template — the contribution statement must reference it directly.
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 · 231 lines · 55 tokens per session scan A 78a6a62cc67f
ppw:cover-letter is a skill published in the GitHub repository Lylll9436/Paper-Polish-Workflow-skill (386 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 2,246 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…