CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

80%

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

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

The body is a well-structured, actionable planning workflow with a clear 7-step sequence, a reviewer feedback loop, and concrete templates plus an executable Codex MCP call. It is token-efficient for a complex skill, though the repeated per-section template fields and inlined templates leave minor conciseness and progressive-disclosure trim opportunities.

Suggestions

Collapse the repeated per-section template boilerplate (e.g. 'Estimated length', 'Self-contained check', 'Front-loading check') into a single shared field legend to reduce token overhead across the §0–§5 templates.

Move the detailed section-by-section template block into a reference file (e.g. references/section-templates.md) and keep SKILL.md as an overview pointing to it, strengthening progressive disclosure.

Tighten Step 6 by making the review outcome an explicit pass/revise checkpoint (e.g. 'if any score < 7, revise and re-review') so the feedback loop has a concrete validation gate rather than a soft 'apply feedback before finalizing'.

DimensionReasoningScore

Conciseness

The body is dense instructional reference material (Claims-Evidence Matrix, section templates, figure/citation plans) that mostly earns its tokens without explaining concepts Claude already knows, matching 'Efficient; minor instances of over-explanation that could be trimmed'. Not a 5 because repeated fields like 'Estimated length' and self-checks ('Front-loading check', 'Self-contained check') on every section template, plus the trailing Acknowledgements, could be trimmed; not a 3 because there is no padded conceptual explanation of the kind the lower anchor penalizes.

4 / 5

Actionability

Quotes concrete executable guidance: the Codex MCP call block with model 'gpt-5.4' and config '{"model_reasoning_effort": "xhigh"}', plus fill-in templates for the matrix, figure plan table, and citation plan, matching 'Mostly executable guidance; concrete code or commands with minor gaps'. Not a 5 because the section templates are scaffolds with placeholders rather than copy-paste-ready output covering common cases; not a 3 because the MCP call and table formats are concrete and usable, not pseudocode.

4 / 5

Workflow Clarity

Quotes a clear 7-step sequence (Extract Claims → Determine Structure → Section Planning → Figure Plan → Citation Scaffolding → Cross-Review → Output) with a feedback loop in Step 6 ('Apply feedback before finalizing') and a Key Rules checklist, matching 'Clear sequence with most checkpoints present; minor validation gaps'. Not a 5 because the Step 6 review is a soft review-then-apply step rather than an explicit pass/fail validation with error-recovery retry; not a 3 because steps are well-sequenced with a real feedback loop. This is a planning (non-destructive, non-batch) skill so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

Quotes well-signaled one-level-deep references ('Read ../shared-references/writing-principles.md', 'Read ../shared-references/venue-checklists.md') with an explicit instruction to load only when needed, plus clear section headers, matching 'Good structure; most content is appropriately placed; references mostly clear'. Not a 5 because all the per-section templates are inlined in SKILL.md rather than split into a reference file, and no bundle files are present in the reviewed package to confirm the shared-references targets exist; not a 3 because the references that do exist are clearly signaled and exactly one level deep.

4 / 5

Total

16

/

20

Passed

Description

86%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 strong: it explicitly states what the skill does and gives concrete, natural (bilingual) trigger phrases for when to use it. Voice is correctly third-person/imperative with no first/second person. The only mild gap is specificity — it describes one composite action rather than enumerating several distinct capabilities.

DimensionReasoningScore

Specificity

Quotes 'Generate a structured paper outline from review conclusions and experiment results' — it names the domain and one composite action with two input sources, but does not list several distinct concrete actions, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. Not a 4 because it lacks the multiple separate actions (e.g. extract, fill, merge) that anchor requires; not a 2 because the action and inputs are concrete rather than minimal/generic.

3 / 5

Completeness

Quotes both the explicit 'what' ('Generate a structured paper outline from review conclusions and experiment results') and an explicit 'when' with concrete trigger phrases ('Use when user says...'), matching the anchor 'Clearly and explicitly answers both what AND when with concrete trigger phrases'. Not a 4 because the 'when' is fully explicit with enumerated triggers rather than only weakly specific.

5 / 5

Trigger Term Quality

Quotes 'Use when user says "写大纲", "paper outline", "plan the paper", "论文规划", or wants to create a paper plan before writing' — comprehensive natural trigger phrases including English synonyms and Chinese equivalents that users would actually say, matching the 'Comprehensive coverage of natural terms including synonyms' anchor. Not a 4 because no common natural terms are missing for this domain.

5 / 5

Distinctiveness Conflict Risk

Quotes 'structured paper outline from review conclusions and experiment results' with distinct bilingual triggers (写大纲, plan the paper) — a clear niche with minimal conflict risk, matching 'Mostly distinct; minor overlap risk with closely related skills'. Not a 5 because it could still slightly overlap with broader academic paper-writing skills; not a 3 because the triggers are specific enough to avoid broad overlap.

4 / 5

Total

17

/

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