aris-paper-writing

Workflow 3: Full paper writing pipeline. Orchestrates paper-plan → paper-figure → paper-write → paper-compile → auto-paper-improvement-loop to go 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

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

92%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 well-organized orchestration skill with a clear phased workflow, explicit validation checkpoints and feedback loops, and concrete copy-paste sub-skill invocations. The only minor weakness is conciseness, where the full final-report template and timeline table add length that could be deferred to a reference.

Suggestions

Move the full Phase 6 final-report markdown template into a reference file (e.g. references/REPORT_TEMPLATE.md) and keep only a one-line pointer in SKILL.md to reduce body length.

Consider condensing the Typical Timeline table or folding its "Can sleep?" guidance into the per-phase Checkpoint blocks, since the duration estimates are approximate and not essential to execution.

Dimension	Reasoning	Score
Conciseness	The body is efficient and avoids explaining concepts Claude already knows (no "what is LaTeX/PDF" padding), but the full ~38-line Phase 6 report template and the Typical Timeline table are minor instances that could be trimmed or moved to a reference without losing operational value.	4 / 5
Actionability	Each phase gives copy-paste-ready slash commands with concrete arguments (e.g. `/aris-paper-plan "$ARGUMENTS"`), explicit expected outputs (PAPER_PLAN.md, figures/, paper/main.pdf), named constants with override syntax, and checkpoint templates covering common cases (ICLR default, NeurIPS/IEEE overrides) — actionable even though it delegates internals to sub-skills.	5 / 5
Workflow Clarity	A clear 6-phase sequence with explicit per-phase checkpoints and approval gates, plus feedback loops: Phase 4 retries compilation up to 3 attempts with auto-fix and post-compile validation (undefined refs, page count), and Phase 5 runs review→fix→recompile over 2 rounds; validation is present so no destructive-cap applies.	5 / 5
Progressive Disclosure	It is a well-structured overview (Overview, Constants, Inputs, Pipeline, Key Rules, Composing, Timeline) with clearly signaled one-level-deep references to sibling sub-skills ("See `/aris-paper-figure` SKILL.md for details"), keeping deep detail appropriately split into the sub-skills rather than inlined here.	5 / 5
	Total	19 / 20 Passed

Description

100%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 that explicitly covers what the skill does and when to use it, with concrete pipeline stages and natural bilingual trigger phrases. It uses third-person voice and avoids vague fluff.

Dimension	Reasoning	Score
Specificity	It names the domain and lists multiple concrete orchestration actions — "paper-plan → paper-figure → paper-write → paper-compile → auto-paper-improvement-loop" — plus the concrete transformation "from a narrative report to a polished, submission-ready PDF", giving comprehensive coverage of the pipeline's stages.	5 / 5
Completeness	It explicitly answers both what ("Full paper writing pipeline. Orchestrates ... to go from a narrative report to a polished, submission-ready PDF") and when ("Use when user says ... or wants the complete paper generation workflow") with concrete trigger phrases, matching the anchor-5 example pattern.	5 / 5
Trigger Term Quality	It provides comprehensive natural trigger phrases a user would actually say, including bilingual synonyms ("写论文全流程", "write paper pipeline", "从报告到PDF", "paper writing") plus the descriptive "complete paper generation workflow".	5 / 5
Distinctiveness Conflict Risk	It occupies a clear niche ("Workflow 3: Full paper writing pipeline") with highly specific bilingual triggers unlikely to clash with other skills, giving minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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

	Total	14 / 16 Passed

Repository: OpenLAIR/dr-claw
Path: skills/aris-paper-writing/SKILL.md
Commit: 4b35756

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.