CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auto-paper-improvement-loop

Autonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds. Use when user says "改论文", "improve paper", "论文润色循环", "auto improve", or wants to iteratively polish a generated paper.

Quality

76%

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/auto-paper-improvement-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An operationally rich, highly actionable workflow with genuinely strong validation checkpoints, empirical justifications, and failure-mode handling. Its main costs are length-driven: duplicated prompt templates, a large inlined whitelist spec that belongs in a reference file, and disordered step numbering (duplicate Step 9s, 5.5 before 5b) that slightly muddies an otherwise clear sequence.

Suggestions

Factor the ~50-line reviewer prompt template out of Steps 2 and 5: state it once (e.g. in a shared reference or a single 'Reviewer prompt template' section) and have Step 5 reference it plus the fresh-context preamble — this removes the largest duplication and roughly 50 lines.

Move the edit-whitelist specification (schema, resolution rules, glob semantics, ~105 lines) into a dedicated reference file (e.g. references/edit-whitelist.md), keeping only the parameter definition, default-OFF note, and a pointer in SKILL.md.

Fix step numbering: rename the second 'Step 9: Summary' (and reconcile 'Step 9: Document Results'), and reorder so Step 5b (Human Checkpoint, which follows the Round 2 review) is not listed after Step 5.5 (Kill Argument) — or renumber the interleaved checkpoints (2b, 4.5, 5.5, 5b) into a consistent scheme.

DimensionReasoningScore

Conciseness

The ~50-line reviewer prompt template is duplicated nearly verbatim in Steps 2 and 5, and the ~105-line edit-whitelist specification (schema, glob semantics, resolution rules) is fully inlined — both clear tightening targets. It stays at 3 rather than 2 because the material is dense operational knowledge (calibration rules, overfull thresholds, empirical motivations), not padded explanation of things Claude already knows.

3 / 5

Actionability

Provides executable bash (latexmk/pdfinfo/grep pipelines), a concrete YAML whitelist schema, a regex detector table, and exact reviewer prompt templates. Below 5 because the Step 4.5 regression-check Python block is a skeleton whose core comparison is a comment ("# Compare normalized theorem blocks...") and prompts carry unfilled [VENUE]/[list figure files] placeholders.

4 / 5

Workflow Clarity

Steps 0–9 are clearly sequenced with strong explicit validation ("Verify: 0 undefined references, 0 undefined citations", the restatement regression test, hard-block stop criteria, an auto-fix pattern table) and recovery loops. Held below 5 by numbering incoherence: two distinct 'Step 9' headings and a confusing order where Step 5.5 (Kill Argument) precedes Step 5b (Human Checkpoint).

4 / 5

Progressive Disclosure

Section headers are consistent and the three external shared-references links (reviewer-backends.md, writing-principles.md, review-tracing.md) are clearly signaled, but no bundle files exist to carry the load — the whitelist spec and the two duplicated reviewer prompt templates are exactly the kind of content that clearly belongs in separate reference files yet is inlined in SKILL.md. More than the 'minor organization gaps' of anchor 4.

3 / 5

Total

14

/

20

Passed

Description

83%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: concrete three-stage action pipeline with round count and reviewer model, plus an explicit 'Use when' clause carrying natural trigger phrases in both English and Chinese. The only weaknesses are minor — a few missing trigger variants and slight overlap risk with sibling paper-improvement skills.

DimensionReasoningScore

Specificity

Names the concrete pipeline actions — 'GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds' — including the reviewer model and round count. Not 5 because supporting capabilities (format check, edit whitelist, kill-argument merge) are uncovered; well above 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both: 'what' ("Autonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds") and 'when' with concrete quoted trigger phrases ("Use when user says ..."). Matches the top anchor exactly; anchor 4's caveat that the 'when' could be more explicit does not apply.

5 / 5

Trigger Term Quality

Includes natural user phrasings in two languages with synonyms: "改论文", "improve paper", "论文润色循环", "auto improve", "iteratively polish a generated paper". A few natural variants (e.g. "revise paper") are missing, keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (iterative polishing of a generated paper via an external-reviewer loop), but generic triggers like "improve paper" and "auto improve" carry minor overlap risk with closely related paper/review-loop skills that the description itself does not distinguish. Not 5's 'minimal conflict risk'.

4 / 5

Total

17

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (637 lines); consider splitting into references/ and linking

Warning

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

12

/

16

Passed

Repository

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

Path

skills/skills-codex/auto-paper-improvement-loop/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.