CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-writing

Workflow 3: Full paper writing pipeline that goes 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

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/paper-writing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 highly actionable, well-sequenced orchestration skill with excellent validation gates and feedback loops, undermined by significant token bloat from repeated policy text and heavy inlining of content that belongs in reference files. Workflow and actionability are exemplary; conciseness and file structure are the clear weak points.

Suggestions

State the style-ref forwarding rule (writer-side phases get it, reviewer/auditor phases never do) once in a single table near the top and reference it from Phases 1, 2, 2b, 3, and 5 instead of repeating the full instruction at each phase.

Replace the two near-identical ~15-line helper-resolver bash blocks (style helper and audit verifier) with one canonical snippet cited via the existing integration-contract §2 link, or move both into a shared reference file.

Extract the Phase 1.5 reviewer prompt (including its long SCOPE LIMITS section) and the complete Phase 6.1 final-report template into reference files (e.g., references/contract-reviewer-prompt.md, references/final-report-template.md) to cut the body's inline bulk.

DimensionReasoningScore

Conciseness

The ~946-line body repeats the style-ref forwarding rule in six places (header note, Phases 1, 2, 2b, 3, 5), restates the assurance-level derivation rule three times (Phases 0, 5.9, 6.0), and pastes two near-identical ~15-line resolver bash blocks. It is dense operational content rather than tutorials of concepts Claude already knows, so it sits above anchor 1 but clearly below the 'mostly efficient' anchor 3.

2 / 5

Actionability

Guidance is copy-paste ready throughout: exact sub-skill invocations ('/paper-plan "$ARGUMENTS"'), complete resolver and detector bash scripts with exit-code handling (rg/jq numeric-claim detection, style-helper and audit-verifier resolution chains), a fully specified reviewer prompt, and complete checkpoint/report templates. The few conditional blocks (Phase 4.5/4.7 'if paper contains...') wrap concrete commands, so this does not fall to anchor 4.

5 / 5

Workflow Clarity

Phases 0 through 6.1 are explicitly sequenced with checkpoints between each, a verbatim submission pre-flight checklist, verifier exit codes as the source of truth, per-verdict remediation (MISSING/STALE/BLOCKING_VERDICT/SCHEMA_INVALID), and feedback loops (max-3-round adversarial contract negotiation, 2 improvement rounds, re-validate after fixes). This matches the anchor-5 example pattern of sequence + explicit validation + error-recovery loops.

5 / 5

Progressive Disclosure

The body is well-sectioned and signals one-level references clearly ('../shared-references/reviewer-backends.md', 'integration-contract.md', 'output-versioning.md'), but ~946 lines inline substantial content that belongs in separate files: the full Phase 1.5 reviewer prompt with its SCOPE LIMITS section, two duplicated resolver scripts, and the complete final-report template. No references/, scripts/, or assets/ bundle files exist, and the referenced ../shared-references/* paths do not resolve within this bundle, so this sits at anchor 3 rather than 4.

3 / 5

Total

15

/

20

Passed

Description

78%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 that explicitly covers both capability and trigger conditions with natural bilingual trigger phrases and a clear niche. Its only real gap is specificity: the pipeline's concrete stages (figures, LaTeX, compilation, review) are absent from the description itself.

DimensionReasoningScore

Specificity

'Full paper writing pipeline that goes from a narrative report to a polished, submission-ready PDF' names the domain and one concrete transformation, but lists none of the pipeline's constituent actions (outline, figures, LaTeX, compilation, review rounds). It matches anchor 3 (domain + 1-2 concrete actions, not comprehensive) rather than anchor 4, which requires several specific actions enumerated.

3 / 5

Completeness

It explicitly answers both 'what' (full pipeline from narrative report to polished, submission-ready PDF) and 'when' ('Use when user says...' followed by concrete quoted trigger phrases), mirroring the anchor-5 example structure. It is not anchor 4 because the 'when' clause is already fully explicit with specific trigger phrases.

5 / 5

Trigger Term Quality

Triggers include natural phrases in both English and Chinese — '写论文全流程', 'write paper pipeline', '从报告到PDF', 'paper writing' — giving good keyword coverage, but common variations such as 'write my paper', 'manuscript', or 'LaTeX' are missing. This is anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (end-to-end paper generation from a narrative report), and triggers like 'write paper pipeline' and 'complete paper generation workflow' are distinctive. However, the generic phrase 'paper writing' has minor overlap risk with closely related sibling sub-skills (/paper-write, /auto-paper-improvement-loop), placing it at anchor 4 rather than 5's minimal-conflict profile.

4 / 5

Total

16

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (946 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 8 suspicious

Warning

Total

12

/

16

Passed

Repository

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

Path

skills/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.