CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ds-write

Use when a quest has enough evidence to draft or refine a paper, report, or research summary without inventing missing support.

Quality

68%

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/ds-write/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 delivers an unusually rigorous, well-sequenced writing workflow with genuine validation gates and concrete tool/file contracts, but it is severely overlong for a SKILL.md, repeats key rules multiple times, inlines content that belongs in its own reference files, and directs the agent to a templates/ bundle that is absent. Workflow clarity is excellent; token efficiency and file structure are the weak points.

Suggestions

Cut the body to an overview and move the memory rules, citation resource stack, writing-craft heuristics, and the full matrix row field enumeration into new files under references/, linked with purpose-stated 'read X when Y' pointers.

Deduplicate repeated rules — the AutoFigure-Edit caption sentence, the 30-50 references target, and the outline-folder sync procedure each appear two or more times; state each once and cross-reference.

Fix or remove the templates/ guidance: the skill claims ten venue template directories plus templates/README.md and templates/DEEPSCIENTIST_NOTES.md are bundled 'inside this skill', but none exist in the bundle, so the instruction currently dead-ends.

DimensionReasoningScore

Conciseness

The body runs ~1320 lines with substantial padding: the AutoFigure-Edit caption mandate appears twice (interaction discipline and Phase 6), the 30-50 verified-references target is stated twice (Phase 0 and Phase 5), outline-folder sync rules repeat across at least four sections, and long operating-contract material (milestone reporting cadence, QQ messaging, memory taxonomies) competes with writing craft. This fits 'Noticeably verbose; several unnecessary explanations or padded sections' — it is not level 1 (it does not explain concepts Claude already knows, and the guidance is domain-specific) but it is well below level 3's 'mostly efficient'.

2 / 5

Actionability

Concrete, executable guidance dominates: exact tool calls ("artifact.submit_paper_outline(mode='candidate'|'select'|'revise', ...)"), specific paths (paper/outline/manifest.json, paper/evidence_ledger.json), a full matrix row schema, and complete JSON shapes for claim_evidence_map.json, figure_catalog.json, and submission_checklist.json. As an instruction-only skill, absence of code is acceptable per the scoring note, but some guidance stays abstract ('run a harsh self-review', 'adversarial mindset') without a concrete recipe, which keeps it at level 4 rather than the copy-paste-ready level 5.

4 / 5

Workflow Clarity

Phases 0-9 are explicitly ordered with validation checkpoints throughout: a preconditions gate ('Before writing seriously, confirm:...'), a hard order for outline/ledger sync, a main-text drafting gate with row-status rules, a five-pass revision loop with recorded deltas, a submission gate, and exit criteria. Feedback loops for error recovery are explicit ('If any of those checks fails, stop drafting and repair the paper contract first', route back to experiment/analysis-campaign). This matches the level-5 anchor of clear sequencing, explicit validation, feedback loops, and checklists.

5 / 5

Progressive Disclosure

References are real, one level deep, and clearly signalized with purpose ('read references/outline-evidence-contract-example.md before drafting further') — all seven referenced files exist in the bundle. But the SKILL.md is not an overview: ~1300 lines of material that belongs in reference files is inlined (memory rules, citation resource stack, drafting style heuristics, the full matrix field enumeration), and the claimed bundled templates directory ('Bundled templates live under templates/ inside this skill', ten template paths plus DEEPSCIENTIST_NOTES.md and README.md) does not exist in the bundle. This sits between level 2 ('content that clearly belongs in separate files is inlined') and level 3 ('some structure but could be better organized'); real, correct references and clear navigation lift it to 3.

3 / 5

Total

14

/

20

Passed

Description

62%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 compact, honest about its trigger condition, and avoids buzzwords, but it is trigger-first with only a thin statement of capabilities. Its keywords are domain-relevant yet miss common synonyms users would naturally say, and 'quest' is internal jargon.

Suggestions

Lead with a third-person capability statement naming 3-4 concrete actions (e.g., 'Builds an outline contract, drafts sections from verified evidence, audits citations, and compiles a LaTeX paper bundle') before the 'Use when...' clause.

Add natural trigger synonyms such as 'write up', 'manuscript', 'publication', or 'LaTeX' so the description matches how users actually phrase the request.

Replace or gloss the internal term 'quest' with user-facing language like 'research project' or define it implicitly through natural phrasing.

DimensionReasoningScore

Specificity

The description names its domain and two concrete actions — "draft or refine a paper, report, or research summary" — but stops there. It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; a score of 4 would require several specific actions (e.g., outline selection, citation verification, LaTeX bundling), and 2 would mean only generic processing language.

3 / 5

Completeness

Both parts are present: what ("draft or refine a paper, report, or research summary") and when ("Use when a quest has enough evidence..."). It fits 'Has both what and when; when could be more explicit or specific' — the trigger is a single condition rather than the multiple concrete trigger phrases of a level-5 description, but goes beyond the what-only or weakly-implied-when patterns of level 3.

4 / 5

Trigger Term Quality

Relevant keywords exist ("paper", "report", "draft", "evidence", "research summary") but common variations are missing ("write up", "manuscript", "publication", "LaTeX", "thesis"), and "quest" is internal system jargon a user would not naturally say. This fits 'Some relevant keywords but missing common variations or synonyms' rather than level 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The drafting/refining niche and the evidence-sufficiency trigger ("has enough evidence") clearly separate it from upstream experimentation or analysis stages, giving 'Mostly distinct; minor overlap risk with closely related skills' — a finalize/analysis stage could still plausibly fire on similar phrasing, which keeps it below the clear-niche level 5.

4 / 5

Total

14

/

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

skill_md_line_count

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

OpenLAIR/dr-claw

Path

skills/ds-write/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.