CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

72%

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/aris-paper-write/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 strong, highly actionable workflow skill: concrete commands, venue-specific templates, explicit anti-hallucination gates, and genuine validation loops (reviewer-model pass, reverse outline, final checklist). Its weaknesses are redundancy — reference pointers and several rules are repeated across sections — and dependency on unverifiable sibling-skill paths for its templates and writing guides.

Suggestions

Consolidate the three sections that point to ../ml-paper-writing references (Orchestra-Guided Writing Overlay, Step 5 pointer, and Writing Quality Reference) into one, and state each rule (natbib-vs-cite, IEEE page limits, backup) once in Key Rules only.

Replace the comment-only Python bib-filtering block with a runnable script, and add an explicit final step to compile (e.g., `latexmk -pdf main.tex`) and fix errors until the build is clean, closing the workflow's feedback loop.

Vendor the referenced writing-guide/checklist/citation-workflow material into this skill's own references/ directory (or ship the templates alongside it) so the skill is self-contained and its referenced paths are verifiable.

DimensionReasoningScore

Conciseness

Mostly efficient, instruction-dense prose with little explanation of concepts Claude already knows, but it could be tightened: the ../ml-paper-writing reference pointers are repeated across three separate sections (Orchestra-Guided Writing Overlay, Step 5, and Writing Quality Reference), and the natbib-vs-cite rule, IEEE page-limit rule, and backup rule are each restated 2-3 times (Step 3/Step 4/Key Rules/Final Checks). This matches anchor 3's "some unnecessary explanation or could be tightened"; not 4 because the cross-section repetition is more than minor.

3 / 5

Actionability

Largely executable guidance: exact curl commands for DBLP and CrossRef, copy-paste LaTeX preambles per venue, a concrete file tree, an exact MCP codex call with model and reasoning-effort config, and word/page targets per section. Not 5 because the Python bib-filtering block is comment-only pseudocode ("import re" followed by # steps) rather than runnable code, and the compile expectation names latexmk without giving the command.

4 / 5

Workflow Clarity

Steps 0-8 are clearly sequenced with real checkpoints: backup-before-overwrite of paper/, the verified BibTeX fallback chain ending in a [VERIFY] no-fabrication gate, a reviewer-model pass with severity levels and "Apply CRITICAL and MAJOR fixes", a reverse-outline test, and a final checklist. Not 5 because there is no explicit compile-and-fix-errors feedback loop — the skill requires latexmk-clean output and checks \ref/\label matching but never instructs running latexmk and iterating on errors.

4 / 5

Progressive Disclosure

Structure is good: well-organized sections with one-level-deep, purpose-conditioned references ("Read … before drafting the Abstract", "only when the built-in DBLP/CrossRef workflow is insufficient"). Not 5 because no bundle files exist in this skill's directory — all references point into a sibling skill (../ml-paper-writing/) that is not part of this bundle and cannot be verified — and a fair amount of detail (venue preamble snippets, per-section writing guidelines, citation rules) is inlined in the ~370-line body rather than split out.

4 / 5

Total

15

/

20

Passed

Description

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

The description is well-formed: third-person, concise, with a clear what and an explicit bilingual "Use when" trigger clause. Its main weakness is a thin capability statement — one action where a fuller summary of the skill's scope (venue-specific formatting, verified bibliography, review pass) would improve specificity and completeness.

Suggestions

Expand the what-clause to enumerate 2-3 more concrete capabilities, e.g., "Draft LaTeX paper sections from an outline, apply venue-specific templates (ICLR/NeurIPS/IEEE), build a verified bibliography, and run a reviewer-model polish pass."

Add natural trigger variants users might say, such as "draft the paper", "write up the paper", venue-specific phrases like "ICLR submission", or file-oriented terms like ".tex".

DimensionReasoningScore

Specificity

"Draft LaTeX paper section by section from an outline" names the domain and 1-2 concrete actions (section-by-section drafting from an outline) but lists no further capabilities such as venue formatting, bibliography building, or review passes. It matches anchor 3; not 4 because it does not list several specific actions, and not 2 because the action given is concrete rather than generic.

3 / 5

Completeness

Both parts are present: a clear what ("Draft LaTeX paper section by section from an outline") and an explicit when ("Use when user says…") with concrete trigger phrases, so the anchor-3/2 "when missing or weak" cases are ruled out. Not 5 because the what is a single thin action compared to the anchor-5 example's multi-action capability summary — it omits the venue formatting, bibliography, and review work the skill performs.

4 / 5

Trigger Term Quality

Triggers "写论文", "write paper", "draft LaTeX", "开始写", and "generate LaTeX content from a paper plan" are natural phrases users would say, covering two languages. Not 5 because common variations like "draft the paper", venue names (e.g., "ICLR submission"), or file extensions (.tex) are missing.

4 / 5

Distinctiveness Conflict Risk

"Draft LaTeX paper section by section from an outline" with paper/LaTeX triggers carves a clear niche distinct from generic document or code skills. Not 5 because "write paper" is broad enough to overlap with closely related sibling writing/plan skills in the same pack (e.g., ml-paper-writing, aris-paper-plan).

4 / 5

Total

15

/

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

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

12

/

16

Passed

Repository

OpenLAIR/dr-claw

Path

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