CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

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.

The body is a thorough, actionable, well-structured workflow with concrete templates and an explicit reviewer feedback loop. The main weaknesses are minor conciseness padding and the absence of an explicit output-write verification checkpoint.

Suggestions

Add an explicit final verification step (e.g., confirm PAPER_PLAN.md exists and contains all required sections) at the end of Step 7 to close the workflow_clarity checkpoint gap.

Trim non-essential prose such as the Codex overlay blockquote and acknowledgements, or move them to a separate reference file, to improve conciseness.

Consider extracting the detailed section templates (Step 3) and Figure/Citation plan tables into a reference file referenced one level deep to strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but includes a few padding sections (the Codex overlay blockquote, the acknowledgements, and explanatory notes like "Theory papers often need 7 sections...") that could be trimmed slightly.

4 / 5

Actionability

It provides concrete, copy-paste-ready templates (Claims-Evidence Matrix, section-by-section planning blocks, Figure Plan table, Citation Plan) and a concrete MCP tool call with a ready prompt, covering the common cases.

5 / 5

Workflow Clarity

A clear 7-step sequence is present with an explicit reviewer feedback loop in Step 6 ("Apply feedback before finalizing"), but there is no explicit verification that the final PAPER_PLAN.md was written correctly, leaving a minor checkpoint gap.

4 / 5

Progressive Disclosure

The content is well-organized into clear sections (Constants, Inputs, Workflow, Output Protocols, Key Rules) with clearly signaled one-level-deep references to shared-references/*.md; however the body is a single ~265-line file rather than splitting detailed templates into reference files.

4 / 5

Total

17

/

20

Passed

Description

95%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-crafted: it states a concrete capability, provides explicit and comprehensive trigger guidance in both languages, and clearly answers both what and when. It is a strong, distinctive description with only minor room to enumerate multiple discrete actions.

DimensionReasoningScore

Specificity

The phrase "Generate a structured paper outline from review conclusions and experiment results" names the domain and a concrete action with specific inputs; it is specific and actionable but describes essentially one main action rather than multiple distinct operations.

4 / 5

Completeness

It explicitly states both what it does ("Generate a structured paper outline from review conclusions and experiment results") and when to use it (the "Use when user says..." clause with concrete triggers).

5 / 5

Trigger Term Quality

The "Use when user says \"写大纲\", \"paper outline\", \"plan the paper\", \"论文规划\"" clause provides comprehensive natural trigger phrases including bilingual synonyms and the command form.

5 / 5

Distinctiveness Conflict Risk

The niche (paper planning from review conclusions) and distinctive triggers ("写大纲", "plan the paper", "论文规划") make it clearly distinguishable from other skills with minimal overlap risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
wanshuiyin/Auto-claude-code-research-in-sleep
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.