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

75%

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-gemini-review/paper-write/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 thorough, well-sequenced workflow with genuinely strong validation checkpoints (backup, fallback chains, review triage, final checklist), but it is significantly over-long: writing-quality rules are stated two to three times, prose philosophy is inlined where a reference file belongs, and one helper code block is pseudocode. Consolidating the duplicated rule sets into a single reference file would improve both conciseness and progressive disclosure at once.

Suggestions

Merge the 'CONFIDENT PROSE, HONEST LIMITS' block, the 'Key Rules' bullets, and the 'Writing Quality Reference' section into one authoritative reference file (or one section) — the same rules are currently stated two to three times.

Replace the comment-only 'Automated bib cleaning' Python block with an actual executable filter script, or move it to scripts/ with the logic implemented.

Move the venue template listings and the 12-rule prose manifesto into references/ files (and ship the templates/ directory the body depends on) so SKILL.md reads as an overview with clearly signaled, one-level-deep references.

DimensionReasoningScore

Conciseness

The body is ~420 lines with systematic duplication: De-AI patterns appear in both Step 5 and the 'Writing Quality Reference' section; the 12-rule 'CONFIDENT PROSE, HONEST LIMITS' block is restated as 'Key Rules' bullets ("Calibrate, don't hedge — ... the CONFIDENT PROSE, HONEST LIMITS block above is the contract"), and rules 9-12 get a second summary; plus padding like the Codex/Gemini overlay blockquotes. This is 'noticeably verbose; several unnecessary explanations or padded sections' (anchor 2) rather than the occasional tightening opportunity of anchor 3.

2 / 5

Actionability

Most guidance is executable: venue documentclass snippets, concrete DBLP/CrossRef curl commands ("curl -s https://dblp.org/rec/{key}.bib"), an MCP review prompt with polling instructions, and a 13-item final checklist. Two gaps keep it from a 5: the 'Automated bib cleaning' Python block is comment-only pseudocode with no actual implementation, and the venue templates are referenced via a templates/ directory whose contents are not shown.

4 / 5

Workflow Clarity

Steps 0-8 are clearly sequenced with explicit validation and feedback loops: backup before overwrite ("never silently destroy existing work"), stale-file cleanup, the DBLP→CrossRef→[VERIFY] fallback chain, cross-review with CRITICAL/MAJOR/MINOR severity triage and fix application, a reverse-outline test, and a comprehensive final checklist. This matches the anchor for clear sequence with explicit validation steps, feedback loops, and checklists.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent, and the templates/ directory the body depends on is also missing), and the 423-line body inlines content that clearly belongs in separate reference files — the ~40-line prose rules manifesto, the venue template listings, and the section-specific guidelines — while duplicating writing-quality material across two sections. The shared-references links that do exist (output-versioning, output-manifest, output-language) are clearly signaled in a blockquote, and section headers are good, which lifts this above anchor 2's 'minimal structure'.

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 compact, well-formed description with an explicit what-and-when structure and natural bilingual trigger phrases. Its main weakness is that the capability statement covers only one action, leaving the skill's fuller scope (venue formatting, bibliography verification, review loop) undescribed.

Suggestions

Extend the capability sentence with 2-3 more concrete actions, e.g., 'build the bibliography from DBLP/CrossRef and format for ICLR/NeurIPS/ICML', to raise specificity.

Add common trigger synonyms such as 'manuscript', 'tex file', or '论文' to widen natural trigger coverage.

Consider replacing the very broad 'write paper' trigger with a more scoped phrase like 'write the paper from a completed plan' to reduce overlap with general writing skills.

DimensionReasoningScore

Specificity

"Draft LaTeX paper section by section from an outline" names the domain (LaTeX paper) and one concrete action (section-by-section drafting), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It does not list several distinct actions (bibliography building, venue formatting, review passes are body-only), so it is not a 4.

3 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: what ("Draft LaTeX paper section by section from an outline") and when ("Use when user says '写论文', 'write paper', 'draft LaTeX', '开始写'"). This matches the anchor-5 example shape exactly; anchor 4 would require the 'when' to be less explicit.

5 / 5

Trigger Term Quality

Triggers are natural and bilingual — "写论文", "write paper", "draft LaTeX", "开始写", "generate LaTeX content from a paper plan" — giving good keyword coverage. A few natural synonyms (e.g., "manuscript", "tex file", "论文") are missing, so it falls just short of the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The LaTeX/paper-plan scope carves a mostly distinct niche, but "write paper" is broad enough to plausibly fire general writing or paper-editing skills — minor overlap risk with closely related skills rather than the minimal risk of anchor 5.

4 / 5

Total

16

/

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