CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ds-rebuttal

Use when a quest already has a paper, draft, or review package and the task is to map reviewer feedback into experiments, manuscript deltas, and a durable rebuttal / revision response.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ds-rebuttal/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 a genuinely actionable, well-sequenced rebuttal workflow with concrete paths, tool calls, and honesty rules, but it is held back by significant redundancy and weak separation from its own reference files. Roughly a third of the content — duplicated contracts, repeated route taxonomies, and drafting rules copied from the response-letter template — could be cut or pushed into references/ without losing guidance.

Suggestions

Remove the 'Drafting style rules' section from the body and keep it solely in references/response-letter-template.md, which already contains a near-verbatim 'Drafting rules' section — leaving it in both places doubles the token cost and risks divergence.

Merge 'Atomic reviewer-item contract' into Workflow step 1 ('Normalize the review package'), since both specify the same item fields (stable id, faithful wording, explicit/inferred, evidence anchor, route), and consolidate the four overlapping route taxonomies into a single canonical list.

Cut or drastically compress the 'Interaction discipline' section (tool-call counts, update cadence, 'Message templates are references only') — it reads as system-prompt material and references message templates that do not exist in the bundle.

DimensionReasoningScore

Conciseness

The 482-line body is noticeably verbose: the "Atomic reviewer-item contract" section duplicates the field list of Workflow step 1, the ~20-bullet "Drafting style rules" section duplicates the "Drafting rules" in references/response-letter-template.md nearly verbatim, the route taxonomy appears in four overlapping forms, and "Interaction discipline" covers progress-update cadence plus "Message templates" that do not exist in the bundle. It is above level 1 because it rarely explains concepts Claude already knows and the bulk is genuine domain guidance, but the several padded/duplicated sections place it below the mostly-efficient level 3.

2 / 5

Actionability

Guidance is mostly executable: exact output paths (paper/rebuttal/review_matrix.md, paper/rebuttal/action_plan.md), concrete tool calls (memory.list_recent(scope='quest', limit=5), artifact.record_analysis_slice(...), artifact.resolve_runtime_refs(...)), and stable id conventions (R1-C1, R1-C2). It falls short of level 5 because calls like artifact.record(payload={'kind': 'decision', ...}) use ellipsis placeholders, and some steps defer to judgment rather than exact commands.

4 / 5

Workflow Clarity

The six-step workflow (normalize, decide, route experiments, route manuscript changes, assemble response, handoff) is clearly sequenced with explicit gating ("Do not finalize the rebuttal package while reviewer-critical and currently feasible matrix rows remain unresolved without an explicit blocker note") and per-slice feedback loops ("after each slice finishes, immediately artifact.record_analysis_slice(...)"). It misses level 5 because the four competing route taxonomies (atomic-contract routes, preliminary routes, step-2 answers, experiment taxonomy) introduce ambiguity about which governs, and validation is expressed as do-not gates rather than verify-and-recover steps.

4 / 5

Progressive Disclosure

The four references/ templates are real, clearly signaled by path, and one level deep, but substantial content that belongs in those files is inlined in the body: the drafting style rules duplicate response-letter-template.md's Drafting rules, and the comment-class guide duplicates the class guide in review-matrix-template.md. This matches 'content that should be separate is inline' at level 3; it stays above level 2 because the references are well signaled and used at the correct workflow points.

3 / 5

Total

13

/

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 that clearly and explicitly states both the capability (mapping reviewer feedback into experiments, manuscript deltas, and a rebuttal/revision response) and the concrete conditions for use. Its main weakness is action specificity — one abstract verb ("map") rather than an enumeration of the concrete operations the skill performs.

DimensionReasoningScore

Specificity

The description names the domain and concrete deliverables ("map reviewer feedback into experiments, manuscript deltas, and a durable rebuttal / revision response") but relies on a single action verb rather than listing several distinct actions, matching the anchor for 1-2 concrete actions without comprehensive coverage. It is above level 2 because the outputs (experiments, manuscript deltas, response) are concrete, but below level 4 because it does not enumerate multiple specific actions like parse, classify, route, and draft.

3 / 5

Completeness

It explicitly answers both what ("map reviewer feedback into experiments, manuscript deltas, and a durable rebuttal / revision response") and when ("Use when a quest already has a paper, draft, or review package and the task is to...") with concrete trigger conditions. The level-4 anchor's deficiency ('when' could be more explicit or specific) does not apply, since the when-clause states two precise conditions.

5 / 5

Trigger Term Quality

Natural academic terms are present — "reviewer feedback", "rebuttal", "revision response", "paper, draft, or review package" — giving good keyword coverage. It falls short of level 5 because common variations such as "reviewer comments", "reviews", or "response to reviewers" are absent.

4 / 5

Distinctiveness Conflict Risk

The rebuttal/revision niche anchored by "review package" and "reviewer feedback" triggers is mostly distinct from ordinary drafting skills. Minor overlap risk remains with closely related ecosystem skills (write, analysis-campaign) because "experiments" and "manuscript deltas" touch their domains, keeping it below level 5.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

OpenLAIR/dr-claw

Path

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