WritingScientific Writing & PublishingLylll9436/Paper-Polish-Workflow-skillPaper Writing & Submission

ppw:cover-letter

Maintainer Lylll9436 · Last updated April 1, 2026

Generate submission-ready cover letters from paper content and target journal requirements. Includes contribution statement, data availability, conflict of interest, and contact block. 生成投稿信，包含贡献声明、数据可用性、利益冲突声明和联系方式。.

Claude CodeWritingSubmissionppw-cover-letterpaper-polishwritingsubmission

Original source

Lylll9436/Paper-Polish-Workflow-skill

https://github.com/Lylll9436/Paper-Polish-Workflow-skill/tree/main/skills/ppw-cover-letter

Maintainer: Lylll9436
License: See upstream repo
Last updated: April 1, 2026

Skill Snapshot

Key Details From SKILL.md

2 min

Key Notes

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.
Default mode: direct. User provides a paper and journal; Skill collects any missing details and generates the complete letter in one pass.

Source Doc

Excerpt From SKILL.md

Leaf Hints (loaded conditionally)

File	When to Load
`references/journals/ceus.md`	When user targets CEUS; provides Aims & Scope, scope keywords for contribution alignment

Ask Strategy

The Skill needs four inputs. If already provided in trigger or paper content, skip the corresponding question.

Target journal — required; determines which template to load. Ask if not specified.
Paper file or text — required; for extracting paper title and key contribution. Ask for file path or paste if not provided.
Correspondence author details (name, email, institution) — required; ask as a single grouped question if not provided.
Data/code availability — optional; are datasets or code publicly available? If yes, ask for repository URLs. Default to "Data are not publicly available" if user declines or does not know.

Rules:

Ask at most 3 questions before proceeding.
Use Structured Interaction when available; fall back to plain-text questions otherwise.
If correspondence details not provided and user declines: use [Corresponding Author Name], [Email], [Institution] placeholders.

Step 0: Workflow Memory Check

Read .planning/workflow-memory.json. If file missing or empty, skip to Step 1.
Check if the last 1-2 log entries form a recognized pattern with ppw:cover-letter 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:cover-letter？"
- 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.