CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-write

Draft LaTeX paper section by section from an outline. Use when user says \"写论文\", \"write paper\", \"draft LaTeX\", \"开始写\", or wants to generate LaTeX content from a paper plan.

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

The body is a highly actionable, well-sequenced workflow for a genuinely complex task: nearly every step has executable commands, explicit validation gates, or concrete output specs, and the venue-specific rules are exactly the kind of detail Claude cannot infer. Its weaknesses are redundancy (duplicated watch-word lists, clarity rules, and prose-contract restatements) and a monolithic structure where the detailed writing-quality material belongs in the reference files it already points to.

Suggestions

Deduplicate the writing-quality guidance: the sentence-level clarity rules and AI watch-word lists each appear twice (Step 5 passes and again in the trailing 'Writing Quality Reference' section) — keep one copy and point to writing-principles.md for the rest.

Move the 12-rule 'CONFIDENT PROSE, HONEST LIMITS' block and the five detailed audit passes into a reference file (e.g., writing-principles.md or a new quality-pass reference), keeping SKILL.md as an overview that states the contract and links out.

Replace the comment-only 'Automated bib cleaning' pseudocode block with an executable script in scripts/ (the citation-filtering task it describes is fully mechanizable), or with real Python inline.

DimensionReasoningScore

Conciseness

The bulk is genuinely non-obvious domain guidance (venue-specific preambles, IEEE page-limit rules, the DBLP/CrossRef fetch chain), but several sections are duplicated: the AI watch words appear in Step 5 ("Replace: delve, pivotal, landscape, tapestry, underscore") and again in the trailing "De-AI patterns" section, the sentence-clarity rules are listed twice within Step 5, and the 12-rule "CONFIDENT PROSE, HONEST LIMITS" block is restated in two Key Rules bullets. This is 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than clearly verbose.

3 / 5

Actionability

Concrete, executable guidance dominates: copy-paste curl commands for DBLP/CrossRef ("curl -s \"https://dblp.org/rec/{key}.bib\""), venue-specific LaTeX preambles, a ready spawn_agent message block, and an explicit project file tree. Not 5 because the "Automated bib cleaning" Python block is comment-only pseudocode with no executable code, which is exactly the anchor-3 defect, though it is the sole instance.

4 / 5

Workflow Clarity

Steps 0-8 are clearly sequenced with explicit validation gates throughout: backup before the destructive overwrite ("Never silently destroy existing work"), the Step 3.5 audit requiring "Resolve all mismatches before Step 4", a review-fix loop ("Apply CRITICAL and MAJOR fixes. Document MINOR issues for the user"), and a 15-item final checklist. This matches the anchor for clear sequence, explicit validation steps, feedback loops, and checklists for complex processes.

5 / 5

Progressive Disclosure

References to shared files are well-signaled with load conditions ("Read ../shared-references/writing-principles.md before drafting the Abstract...", "only when the built-in DBLP/CrossRef workflow is insufficient"), but no bundle files exist in references/, scripts/, or assets/, the referenced templates/ directory is not part of the bundle, and large blocks that belong in reference files (the ~65-line 12-rule prose contract, the five detailed audit passes) are fully inlined. This lands between 'content that should be separate is inline' (3) and 'most content appropriately placed' (4) — the inlining and unverifiable bundle paths keep it at 3.

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: it states a clear, concrete capability and pairs it with an explicit 'Use when' clause containing natural trigger phrases in both English and Chinese, with no voice or padding issues. Its main weakness is that the 'what' undersells the skill's actual scope, listing only the drafting action while the body also covers venue formatting, bibliography verification, and multi-pass review.

DimensionReasoningScore

Specificity

"Draft LaTeX paper section by section from an outline" names the domain and one concrete action, but does not enumerate the skill's other capabilities (bibliography building, venue formatting, review passes) that the body actually performs. It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than 4, which expects several listed actions.

3 / 5

Completeness

It clearly answers both questions: the what is "Draft LaTeX paper section by section from an outline" and the when is an explicit "Use when user says..." clause with five concrete trigger phrases. This matches the anchor for explicitly answering both what AND when with concrete trigger phrases; it is above 4 because the 'when' is fully explicit rather than vague.

5 / 5

Trigger Term Quality

The trigger list '"写论文", "write paper", "draft LaTeX", "开始写"' plus "wants to generate LaTeX content from a paper plan" gives good natural keyword coverage including bilingual synonyms. Not 5 because common English variations like "manuscript", "write-up", or "draft the paper" are missing.

4 / 5

Distinctiveness Conflict Risk

The niche (LaTeX paper generation from a plan) and triggers like "draft LaTeX" are mostly distinct with only minor overlap risk against closely related sibling skills such as /paper-plan or /paper-figure. Not 5 because the fairly broad phrases "write paper" and "写论文" could plausibly fire for a general paper-writing skill.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

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

Path

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