Paper Skill
AI skill for Claude Code providing prompt-based workflow for academic paper writing, polishing, reviewing, translating, and submitting to journals.
cLin-c · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add cLin-c/paper-skillAbout this skill
name: paper-skill description: End-to-end, Chinese-first academic research and publication workflow for reading papers, literature reviews, research framing, manuscript planning and writing, Chinese-English translation, LaTeX, figures, citation verification, reporting-guideline checks, journal selection, peer review, rebuttals, revisions, and submission packages. Use for SCI, IEEE, Nature-family, IJCAI, TRO, theses, systematic reviews, clinical/observational/animal studies, and any task where claims, evidence, references, manuscript files, or journal requirements must be checked rather than invented.
paper-skill
Turn research materials into evidence-calibrated academic outputs. Treat the manuscript as a traceable system of claims, evidence, citations, figures, and submission requirements—not as a free-form writing task.
Non-negotiable rules
- Never invent data, experiments, statistics, quotations, references, DOI values, journal policies, author contributions, ethics approvals, funding, or revision locations.
- Separate three states explicitly:
VERIFIED,UNVERIFIED, andAUTHOR_INPUT_NEEDED. - Preserve scientific meaning before improving style. Flag contradictions instead of silently repairing them.
- Map every material claim to evidence. Downgrade or remove unsupported claims.
- Verify time-sensitive journal policies and bibliographic metadata against primary sources when tools permit. Record source and access date.
- Never promise acceptance, impact factor outcomes, or detector evasion. Quality scores are internal triage, not publication predictions.
- Keep a change ledger for manuscript edits: location, original, revision, reason, evidence affected.
Read references/verification-policy.md whenever the task involves citations, journal policies, ethics, reporting standards, factual literature claims, or current information.
Route the task
First classify the request, then load only the indicated resources.
| Route | Typical requests | Required resources |
|---|---|---|
read | Read, summarize, critique, bilingual notes | references/paper-writing-prompts.md |
literature | Search strategy, review, gap map, related work | workflows/literature-review.md, citation-integrity.md |
write (plan-write) | Storyline, outline, draft, rewrite, polish, translate | Load the matching section guide below plus references/output-contracts.md |
figures | Method diagram, result figure, caption, figure audit | references/figure-prompts.md, workflows/figure-audit.md |
review | Pre-submission review, rejection risks, adversarial audit | quality-gates.md, references/output-contracts.md |
rebuttal | Reviewer response, R&R, rebuttal, revision verification | references/output-contracts.md, quality-gates.md |
citations | DOI audit, hallucination scan, claim-source match | citation-integrity.md, workflows/reference-tools.md |
journal | Venue selection, transfer, policy, formatting | journal-strategy.md, references/verification-policy.md |
submit (submission) | Cover letter, highlights, declarations, final package | workflows/submission-package.md, references/output-contracts.md |
reporting | CONSORT, PRISMA, STROBE, ARRIVE, CARE, SPIRIT | references/reporting-guidelines.md, references/verification-policy.md |
full-verify | DOI lookup, journal policy evidence, manuscript/rebuttal consistency | workflows/full-verification.md |
For IEEE Transactions on Robotics, also load references/venues/ieee-tro.md. Treat every venue profile as a dated starting point and re-check its official links before submission.
For a multi-route request, load the smallest combination that covers it. Do not load the general prompt bank unless the routed resources are insufficient; then use references/prompt-bank.md.
Section-writing selector
| Target | Load |
|---|---|
| Paragraph flow or full-section structure | references/section-guides/paragraph-architecture.md |
| Abstract | references/section-guides/abstract.md |
| Introduction | references/section-guides/introduction.md |
| Related Work | references/section-guides/related-work.md |
| Method | references/section-guides/method.md |
| Experiments/Results | references/section-guides/experiments.md |
| Discussion/Conclusion | references/section-guides/discussion-conclusion.md |
For worked patterns, load examples/section-rewrites.md. The examples are synthetic; reuse reasoning structure, never their facts.
Core workflow
1. Intake and provenance
Create a compact intake record:
- task and intended artifact;
- paper type and discipline;
- target venue and deadline, if supplied;
- authoritative source files and version order;
- available evidence: datasets, experiments, figures, tables, code, references;
- required output format;
- unresolved author decisions.
If several manuscript versions exist, ask which is authoritative only when it cannot be inferred safely. Never m
Read the complete source ↗