CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aris-paper-plan

Generate a structured paper outline from review conclusions and experiment results. Use when user says "写大纲", "paper outline", "plan the paper", "论文规划", or wants to create a paper plan before writing.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-sequenced planning workflow that gives Claude everything needed to execute: exact filenames, fill-in templates, venue-specific rules, a reviewer-model cross-check, and a defined output artifact. The few weaknesses are redundancy in venue/page-budget rules, a single-pass reviewer loop, and reliance on external reference files that are not bundled with the skill.

DimensionReasoningScore

Conciseness

The body is almost entirely operational (templates, tables, exact filenames, tool configs) and assumes Claude's competence — no concept explanations. Not 5 because the venue page-count rules and IEEE inclusion caveat are stated twice (Constants and Key Rules), and the front-loading guidance repeats across the overlay section, Step 2, and Key Rules.

4 / 5

Actionability

Guidance is fully concrete and executable: exact input filenames, a fill-in Claims-Evidence Matrix, per-section planning templates with page budgets, a figure-plan table, a copy-paste MCP reviewer invocation (model, config, full prompt), and a complete PAPER_PLAN.md output template. Templates are fill-in-the-blank by design, appropriate for a generative planning skill, and cover the common paper types (empirical, theory, method).

5 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced with branching at Step 1 (use CLAIMS_FROM_RESULTS.md if present, else extract from scratch; ask the user if no inputs exist) and explicit constraints ("total page budget MUST sum to MAX_PAGES", section-count match). Not 5 because the Step 6 reviewer feedback is a single pass — "Apply feedback before finalizing" — with no re-review iteration or threshold for when the outline is good enough.

4 / 5

Progressive Disclosure

Clear section headers organize the body, and external references (writing-guide.md, checklists.md) are one level deep with explicit load-only-when-needed signaling. Not 5 because no bundle files ship with this skill — the referenced ../ml-paper-writing files live outside it and cannot be verified — and the dense per-section templates are all inlined in a ~275-line file rather than split out.

4 / 5

Total

17

/

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 well-formed description with an explicit 'Use when' clause and natural bilingual trigger phrases, cleanly separating what the skill does from when to invoke it. The main weakness is that it names only one action, underselling the concrete deliverables (claims-evidence matrix, figure/citation plans, reviewer cross-check) that make the skill distinctive.

Suggestions

List 2-3 concrete deliverables in the description, e.g. "Generate a structured paper outline with a claims-evidence matrix, figure plan, and citation plan from review conclusions and experiment results".

Add a few more trigger synonyms such as "论文大纲" or "outline the paper" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Generate a structured paper outline from review conclusions and experiment results" names one concrete action and its inputs, but does not enumerate what the outline production includes (claims-evidence matrix, figure plan, citation plan, cross-review). Not 4 because only a single action is listed rather than several specific actions; not 2 because the action is concrete rather than generic domain language.

3 / 5

Completeness

Explicitly answers what ("Generate a structured paper outline from review conclusions and experiment results") and when ("Use when user says '写大纲', 'paper outline', 'plan the paper', '论文规划', or wants to create a paper plan before writing") with concrete trigger phrases. This matches the top anchor exactly; nothing is merely implied.

5 / 5

Trigger Term Quality

Triggers "写大纲", "paper outline", "plan the paper", "论文规划" are natural phrases a user would say, with bilingual synonym coverage. Not 5 because common variations like "论文大纲", "paper structure", or "outline the paper" are missing; not 3 because coverage already spans both languages and multiple phrasings.

4 / 5

Distinctiveness Conflict Risk

The paper-planning niche is distinct — "paper outline"/"论文规划" plus "before writing" disambiguates it from drafting or figure-generation skills. Not 5 because "写大纲" (write outline) is generic in Chinese and could also fire for non-paper outlining tasks, creating minor overlap risk with closely related skills.

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

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

OpenLAIR/dr-claw

Path

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