CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-writing

Workflow 3: Full paper writing pipeline. Orchestrates paper-plan → paper-figure → paper-write → paper-compile → auto-paper-improvement-loop to go from a narrative report to a polished, submission-ready PDF. Use when user says \"写论文全流程\", \"write paper pipeline\", \"从报告到PDF\", \"paper writing\", or wants the complete paper generation workflow.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured orchestrator skill: the six-phase pipeline is unambiguous, every phase has a concrete invocation and output, and validation gates and feedback loops are explicit. The main costs are token weight (timeline, workflow-composition, and Phase 5.9 prose) and references that point outside the bundle without verifiable targets.

Suggestions

Cut or compress the lowest-value sections — "Typical Timeline" and "Composing with Other Workflows" — and tighten the Phase 5.9 prose into a short bulleted contract to reduce token load without losing actionability.

Fix progressive-disclosure navigation: the "../../shared-references/*.md" links point outside the skill bundle and cannot be verified; either ship those files inside the skill (e.g., references/) or inline the three-line protocol summaries they encode.

Replace ellipsized guidance with concrete lists, e.g., enumerate the "De-AI polish" banned-words list or point to a dedicated reference file, so every instruction is executable as written.

DimensionReasoningScore

Conciseness

The phase descriptions, constants, and Key Rules are dense and mostly earn their tokens, but "Typical Timeline" (with a "Can sleep?" column), "Composing with Other Workflows", and the sprawling Phase 5.9 / writing-invariant passages include content Claude could infer or that adds little actionable value. Mostly efficient with some unnecessary sections — anchor 3, not 4, because multiple padded sections could simply be cut.

3 / 5

Actionability

Every phase gives a literal invocation ("/paper-plan \"$ARGUMENTS\"", "/paper-compile \"paper/\""), named output artifacts (PAPER_PLAN.md, figures/latex_includes.tex, paper/main.pdf), concrete constants, and specific failure handling ("latexmk -pdf", "Up to 3 compilation attempts", gate "exit 0"). Minor gaps — e.g., "De-AI polish (remove \"delve\", \"pivotal\", \"landscape\"...)" ellipses the actual list — keep it at anchor 4 rather than fully copy-paste-ready 5.

4 / 5

Workflow Clarity

A clear six-phase sequence with an explicit checkpoint after every phase, hard validation gates ("Compilation must succeed before entering the improvement loop. Fix all errors first."), and review→fix→recompile feedback loops in Phase 5 plus the mandatory gate in Phase 5.9. This matches anchor 5: clear sequence, explicit validation, feedback loops for error recovery.

5 / 5

Progressive Disclosure

Sections are well organized and detail is appropriately delegated to the sub-skills; "Output Protocols" clearly signals one-level-deep references. However, those references point to "../../shared-references/output-versioning.md" (and siblings) that are not part of this skill's bundle and cannot be verified to exist, and no references/, scripts/, or assets/ directories ship with the skill — good structure with a real navigation gap, so anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete pipeline orchestration stated, explicit bilingual trigger phrases, and a clear niche. Its only weaknesses are a trigger list missing a few common English variations and slight overlap with the /paper-write sub-skill on generic 'paper writing' phrasing.

DimensionReasoningScore

Specificity

"Orchestrates paper-plan → paper-figure → paper-write → paper-compile → auto-paper-improvement-loop to go from a narrative report to a polished, submission-ready PDF" names the domain, several concrete chained actions, and a concrete deliverable. Not a 5 because the sub-skills' individual actions are asserted rather than enumerated; clearly above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers "what" (orchestrates the five named sub-skills from narrative report to submission-ready PDF) and "when" with concrete quoted trigger phrases ("Use when user says ..."). This matches the anchor-5 example structure; it is not a 4 because the "when" clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Includes natural user phrases — "write paper pipeline", "paper writing", "complete paper generation workflow" — plus bilingual variants ("写论文全流程", "从报告到PDF"). A few common terms are missing (e.g., "write my paper", "draft the paper", "LaTeX"), matching anchor 4 rather than the comprehensive synonym/file-extension coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Workflow 3: Full paper writing pipeline" carves a clear niche — the complete end-to-end orchestration — with distinct trigger phrases unlikely to fire for other skills. Minor overlap risk with the /paper-write sub-skill on the bare phrase "paper writing" keeps it from clearly matching the anchor-5 example's fully disjoint trigger set; anchor 4 (mostly distinct, minor overlap with closely related skills) is the best fit.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex-gemini-review/paper-writing/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.