CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-writing

Workflow 3: Full paper writing pipeline that goes from a narrative report to a polished, submission-ready PDF. Use when user says "写论文全流程", "write paper pipeline", "从报告到PDF", "paper writing", or wants the complete paper generation workflow.

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 orchestration skill with strong validation gates, weakened mainly by length and rationale prose that could be split into reference files.

Suggestions

Move the Phase 1.5 contract negotiation, Phase 6.0 assurance/verifier resolution, and the 'Empirical motivation' rationale blocks into referenced files (e.g. acceptance-contract.md, assurance-gate.md) to lift progressive_disclosure and reduce conciseness cost.

Trim editorial rationale paragraphs ('Why this is the most diagnostic...', 'Empirical motivation') to one-line pointers or move them to the referenced audit SKILL.md files, keeping SKILL.md to operational guidance only.

DimensionReasoningScore

Conciseness

The body is operationally dense and mostly efficient, but ~690 lines include rationale prose ('Empirical motivation', 'Why this is the most diagnostic of the four audit layers') and repeated assurance-derivation blocks that could be tightened, so it does not reach the lean/efficient anchor.

2 / 3

Actionability

Guidance is fully executable: concrete slash commands per phase, real bash with exit-code handling, file paths, and named JSON artifacts — copy-paste ready and matching the top anchor.

3 / 3

Workflow Clarity

Phases 0–6 are clearly sequenced with explicit checkpoints, a submission pre-flight checklist, verifier gates with exit-code remediation, and review→fix→recompile feedback loops, satisfying the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

References to ../shared-references/*.md are well signaled and one level deep, but the SKILL.md itself is a monolithic ~690-line wall with inline contract/verifier detail that belongs in separate files, and no bundle files exist to offload it.

2 / 3

Total

10

/

12

Passed

Description

82%

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 with explicit what/when coverage and natural multilingual triggers, held back only by high-level action phrasing and mild overlap with sibling paper-* skills.

Suggestions

Add one or two concrete downstream actions to the description (e.g. 'generate figures, write LaTeX, compile to PDF, and run review/fix improvement loops') to lift specificity from 2 to 3.

Qualify the bare 'paper writing' trigger (e.g. 'paper writing pipeline' / 'full paper generation') to reduce overlap with /paper-write and improve distinctiveness.

DimensionReasoningScore

Specificity

It names the domain and a concrete transformation ('goes from a narrative report to a polished, submission-ready PDF') but does not enumerate multiple specific actions, so it sits at the 'names domain and some actions, not comprehensive' anchor rather than 3.

2 / 3

Completeness

It explicitly answers both 'what' (full paper writing pipeline, narrative report to submission-ready PDF) and 'when' via an explicit 'Use when user says...' clause, hitting the top anchor.

3 / 3

Trigger Term Quality

Natural triggers a user would actually say are well covered: 'write paper pipeline', 'paper writing', 'complete paper generation workflow', plus Chinese equivalents, matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

The pipeline-orienting triggers are distinctive, but the bare phrase 'paper writing' overlaps with the sibling sub-skills it orchestrates (e.g. /paper-write), so it could still trigger the wrong skill.

2 / 3

Total

10

/

12

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.

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (695 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: 4 suspicious

Warning

Total

12

/

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.