CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/skills-codex/paper-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 strong, workflow-driven skill body: concrete templates, venue-aware budgets, explicit gates, and a built-in review feedback loop. The main costs are token redundancy — venue/citation rules stated twice and an opaque opening blockquote — and inline templates that inflate SKILL.md length.

Suggestions

State the MAX_PAGES counting and citation-style rules once (Constants or Key Rules, not both) and cross-reference the other section, saving ~10 lines of duplicated guidance.

Move the dense opening reviewer-backend blockquote into the referenced reviewer-backends.md (or Step 6) — it front-loads resolver mechanics before the user-facing task statement.

Consider relocating the reusable section-by-section and figure/citation plan templates to a reference file so SKILL.md stays a lean overview with well-signaled pointers.

DimensionReasoningScore

Conciseness

Mostly efficient, instructional content, but there is real duplication: the MAX_PAGES venue-counting rules and IEEE-vs-ML citation-style rules appear nearly verbatim in both "Constants" and "Key Rules", and the opening reviewer-backend blockquote is dense and partially repeats Step 6's resolver note. Fits anchor 3 ("mostly efficient but... could be tightened") rather than anchor 4, since the redundancy is more than minor.

3 / 5

Actionability

Highly actionable throughout: copy-paste templates for the claims-evidence matrix, section-by-section plan, figure plan table, and final PAPER_PLAN.md, plus concrete per-venue page budgets and an explicit spawn_agent review prompt. It falls short of anchor 5 only because the cross-review invocation ("spawn_agent:", reviewer_route.py) is a pseudo-DSL whose actual mechanics live in external references rather than here.

4 / 5

Workflow Clarity

Steps 1-7 are clearly sequenced with explicit validation checkpoints: input fallback logic (fall back to ./AUTO_REVIEW.md, ask the user if nothing exists), a STOP/rerun gate when claims are unadjudicated under assurance:submission, and a reviewer feedback loop ("Apply feedback before finalizing") in Step 6. This matches anchor 5's "explicit validation steps; feedback loops"; anchor 4 would require missing checkpoints, which is not the case.

5 / 5

Progressive Disclosure

Good structure with clearly signaled, conditionally loaded one-level-deep references ("Read ../shared-references/writing-principles.md when framing the Abstract...", venue-checklists before freezing, output protocols at the end), and no bundle files exist to nest. It is not anchor 5 because the ~290-line body inlines large template blocks (section skeleton, figure/citation plans) that could partly live in reference files, and the referenced shared-references are external to the bundle rather than organized under it.

4 / 5

Total

16

/

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 what-and-when structure and good bilingual trigger coverage. Its main weakness is thin capability coverage — it advertises only the headline action while the skill also builds a claims-evidence matrix, figure/citation plans, and runs an external review loop.

Suggestions

List 2-3 more of the skill's concrete outputs in the description (e.g., "builds a claims-evidence matrix, figure and citation plans, and a venue-aware page budget") to lift specificity from one action to several.

Add one or two natural trigger variants such as "outline the paper" or "paper structure" to round out keyword coverage.

DimensionReasoningScore

Specificity

"Generate a structured paper outline from review conclusions and experiment results" names the domain and deliverable plus two concrete input sources, but stops at one action — it never mentions the claims-evidence matrix, figure/citation planning, or reviewer cross-check the skill actually performs. This matches anchor 3 ("names domain and 1-2 concrete actions, but not comprehensive"), not anchor 4, which requires several specific actions listed.

3 / 5

Completeness

It explicitly answers both questions: the "what" is "Generate a structured paper outline from review conclusions and experiment results" and the "when" is a concrete "Use when user says..." clause listing trigger phrases. This is a direct match for anchor 5; anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Triggers include natural phrases in two languages — "写大纲", "paper outline", "plan the paper", "论文规划", "wants to create a paper plan before writing" — giving good coverage of how users would phrase the request. A few natural variants are missing (e.g., "outline the paper", "paper structure"), so it fits anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Paper outline" / "plan the paper" / "论文规划" carve out a clear planning niche distinct from writing or figure-generation skills, but the skill family it belongs to (paper-write, paper-figure, paper-compile) shares the "paper" keyword space, creating minor overlap risk. Fits anchor 4 ("mostly distinct; minor overlap risk with closely related skills") better than anchor 5's minimal-conflict bar.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 4 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

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