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

73%

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

This is a highly actionable, exceptionally well-sequenced workflow with strong validation and feedback loops, but it is bloated: roughly 690 lines with significant redundancy (rules restated, venue rules repeated three times) and background material Claude already knows. It also functions as a monolith, inlining scripts and templates that belong in bundle files while pointing at external references that do not resolve within the bundle.

Suggestions

Deduplicate the Key Rules section against the CONFIDENT PROSE, HONEST LIMITS block and state the venue citation-style and page-limit rules once (in Constants), removing the three repetitions of each; this alone should cut substantial length.

Move the inline 70-line BibTeX hygiene validation script to scripts/validate_bib.py (invoked with a one-line command) and the venue LaTeX setups to templates/ files, keeping SKILL.md an overview with well-signaled one-level-deep references.

Trim Pass 1's cluttered-phrase replacement table and AI-isms list to a single sentence of intent — Claude already knows 'due to the fact that' means 'because' and that 'delge/pivotal/landscape' are filler — keeping only the non-obvious Banana Rule and venue-specific guidance.

DimensionReasoningScore

Conciseness

There are several padded or redundant sections beyond 'some unnecessary explanation': the 12-rule CONFIDENT PROSE block is restated in Key Rules ("rules 9-12 above"), venue citation-style and page-limit rules appear three times (Constants, Step 3, Key Rules), related-work >=1 page appears three times, and Pass 1 teaches Claude things it already knows (a "Due to the fact that -> Because" table, "In order to -> To", and an AI-isms list of delve/pivotal/landscape). It is not a 1 because most content is genuinely task-specific and non-obvious (venue templates, DBLP/CrossRef chain, IEEE-vs-ML rules).

2 / 5

Actionability

The body is overwhelmingly copy-paste ready: executable curl commands for DBLP/CrossRef, a fully runnable 70-line Python validation script, concrete LaTeX template snippets, an exact project tree, and a complete reviewer MCP prompt payload. The small gap is the 'Automated bib cleaning' block, which is a comment skeleton rather than executable code ("# 1. Grep all \citep{...} ... # 4. Write the filtered bib"), so it falls just short of the fully-executable 5 anchor.

4 / 5

Workflow Clarity

Steps 0-8 are clearly sequenced with explicit validation checkpoints and feedback loops: backup before overwrite, stale-file cleanup, a mandatory bib hygiene validation run immediately after writing references.bib with explicit DEAD/VERIFY/MISMATCH remediation paths, a theory restatement audit before Step 4, and a final 16-item checklist. This matches the anchor for clear sequence, explicit validation, error-recovery loops, and checklists; even destructive operations (overwriting paper/) have a backup gate.

5 / 5

Progressive Disclosure

References are clearly signaled and purpose-scoped ("Read ../shared-references/writing-principles.md before drafting the Abstract... only when prose feels generic"), which is good, but none of the referenced files (../shared-references/*.md, templates/, tools/extract_paper_style.py) exist in the provided bundle, and heavy content that clearly belongs in separate files is inlined — the 70-line validation script, the venue template listings, and the 12-rule prose block inside a 690-line monolithic SKILL.md. This sits between the 2 anchor (content that belongs in separate files is inlined) and the 4 anchor (most content appropriately placed), with structure present but organization improvable.

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 concise, well-formed description that explicitly covers both what the skill does and when to use it, with natural bilingual trigger phrases. Its main gap is that the 'what' undersells the skill's actual capabilities (venue templating, citation verification, review passes), leaving specificity at the 1-2-action level.

DimensionReasoningScore

Specificity

"Draft LaTeX paper section by section from an outline" names the domain and one core concrete action with its manner (section-by-section, from an outline), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It does not list several specific actions (venue-specific formatting, DBLP-verified bibliography, review passes) that the skill actually performs, so it is not a 4.

3 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: the 'what' is "Draft LaTeX paper section by section from an outline" and the 'when' is "Use when user says ... or wants to generate LaTeX content from a paper plan". This directly matches the anchor for clearly and explicitly answering both what and when with concrete trigger phrases; the 'when' clause is already explicit, so 4's caveat ('when' could be more explicit) does not apply.

5 / 5

Trigger Term Quality

"写论文", "write paper", "draft LaTeX", "开始写" give good natural keyword coverage including bilingual synonyms, plus the fallback condition "wants to generate LaTeX content from a paper plan". A few natural phrasings users would say are missing (e.g., "write my paper", "draft the method/introduction section", venue-name triggers), which keeps it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The LaTeX-paper-drafting niche with triggers like "draft LaTeX" and the paper-plan dependency is mostly distinct, but "write paper" / "写论文" are broad enough to overlap with sibling paper skills (e.g., /paper-plan, /paper-figure) and general writing skills. Minor overlap risk with closely related skills matches the 4 anchor; the 5 anchor requires a clearer niche with minimal conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

68%

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

Validation — 11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (699 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: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

11

/

16

Passed

Repository

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

Path

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