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

74%

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

Fix and improve this skill with Tessl

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

Quality

Content

62%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 rigorously sequenced, highly actionable orchestration skill whose verification and feedback machinery is exemplary. Its weaknesses are token efficiency — the same assurance/gating logic is explained two to three times across 759 lines — and progressive disclosure, with heavy inline policy content and externalized references that are not part of the bundle.

Suggestions

State the assurance-level derivation once (Phase 0) and have Phase 6.0 reference it ('re-derive per Phase 0; on disagreement overwrite and warn') instead of restating the full 5-step rule, cutting ~60 lines of duplication.

Move the Phase 6.0 verifier-resolution bash, the pre-flight checklist, and the audit emission rules into a shared-references file (or a bundled references/audit-gates.md) and link to it, leaving SKILL.md a lean phase-by-phase overview.

Trim the 'Empirical motivation' and 'Why this is the most diagnostic' narrative paragraphs to one-line rationale notes; the failure modes they describe can be carried by the audit sub-skills themselves.

DimensionReasoningScore

Conciseness

The 759-line body restates the assurance-level derivation in full in both Phase 0 and Phase 6.0, and describes the audit gates in Phases 4.5/4.7/5.5/5.8 and again in the Phase 6.0 pre-flight checklist, 'Invoking the four audits', and the remediation list, plus multi-paragraph 'Empirical motivation' narratives. It is operationally dense rather than padded with basics Claude already knows, so it sits above anchor 1 but clearly matches 'several unnecessary explanations or padded sections'.

2 / 5

Actionability

Phases give exact invocations ('/paper-plan "$ARGUMENTS"', '/paper-compile "paper/"'), copy-paste bash (numeric-claim rg detector, verifier resolution chain), and concrete checkpoint templates. Falls short of 5 because some snippets leave placeholders unresolved locally ($GATE_HELPER, $ANTI_AR_COMMIT, <ARIS_REPO>) or use pseudo-if blocks, deferring full contracts to external files.

4 / 5

Workflow Clarity

The pipeline is an explicitly sequenced Phase 0–6 chain with per-phase skip conditions, checkpoints, an itemized submission pre-flight checklist, verifier exit codes as the source of truth, and feedback loops everywhere (fix-then-rerun verifier, max-3-round contract negotiation with fallback, 3 compile attempts, STALE/MISSING remediation paths). This matches the anchor for clear sequencing with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

References like '../shared-references/integration-contract.md' and 'review-scope-limits.md' are clearly signaled but live outside the skill directory and no bundle files (references/, scripts/, assets/) exist in this skill, while large gate/contract logic that belongs in those shared files is inlined (and duplicated) in the body. Structure exists but content that should be separate is inline, matching anchor 3 rather than 4.

3 / 5

Total

14

/

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 with an explicit 'Use when' trigger clause, concrete quoted trigger phrases in two languages, and a clear input→output statement of what the skill produces. Its main gaps are limited enumeration of the pipeline's concrete capabilities and a few missing natural synonyms.

DimensionReasoningScore

Specificity

'Full paper writing pipeline that goes from a narrative report to a polished, submission-ready PDF' names a concrete input→output action, but only that one — it never enumerates the pipeline's actions (plan, figures, LaTeX, compile, review loop). This matches 'names domain and 1-2 concrete actions, but not comprehensive', below anchor 4's 'lists several specific actions'.

3 / 5

Completeness

Explicitly answers both questions: the 'what' ('goes from a narrative report to a polished, submission-ready PDF') and the 'when' ('Use when user says "写论文全流程", "write paper pipeline", "从报告到PDF", "paper writing", or wants the complete paper generation workflow') with concrete quoted trigger phrases, matching the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — 'write paper pipeline', 'paper writing', 'complete paper generation workflow' — plus Chinese variants ('写论文全流程', '从报告到PDF'). Good coverage, but common synonyms like 'manuscript', 'draft my paper', or 'LaTeX' are missing, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

'Paper writing pipeline' / 'paper generation workflow' carves a clear niche distinct from idea-discovery or experiment workflows. Only minor overlap risk with its own sub-skills (e.g. a user asking for help 'writing a paper section' might want /paper-write rather than this full pipeline), keeping it below anchor 5.

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 (760 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: 6 suspicious

Warning

Total

12

/

16

Passed

Repository

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

Path

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