CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rebuttal

Workflow 4: Submission rebuttal pipeline. Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds. Use when user says "rebuttal", "reply to reviewers", "ICML rebuttal", "OpenReview response", or wants to answer external reviews safely.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 well-engineered workflow document: the phase sequence, validation lints, and feedback loops are exemplary, and commands/artifact specs are largely executable. It is held back by rule duplication across sections and by a bundle whose body links point to shared-reference files that are not actually shipped with the skill.

Suggestions

Consolidate repeated safety rules into a single section: 'Never fabricate/overpromise', 'Answer friendly reviewers too', and the structural_distinction pattern are each stated 2-3 times across Phase 2, Phase 4, and Key Rules.

Ship or inline the referenced bundle files: all shared-references links (reviewer-backends.md, reviewer-routing.md, review-tracing.md, integration-contract.md) plus save_trace.sh and reviewer_route.py are dangling in this skill directory, leaving reviewer routing and trace-saving steps unverifiable.

Move long artifact specifications (the REVISION_PLAN.md structure with its example checklist, and the reviewer-defensive moves heuristics) into a references/ file so the SKILL.md body stays a navigable overview.

DimensionReasoningScore

Conciseness

Mostly efficient operational content, but several rules are stated two or three times ('NEVER invent experiments, numbers, derivations, citations, or links' in Phase 4 repeats 'Never fabricate' in Key Rules; 'Answer friendly reviewers too' and the structural_distinction pattern also appear twice), and the Phase 3 manual-identity paragraph is convoluted — matching the 'could be tightened' anchor rather than the padded one below.

3 / 5

Actionability

Largely executable guidance: an exact MCP stress-test call with config and a full prompt template, concrete commands like '/experiment-bridge "rebuttal/REBUTTAL_EXPERIMENT_PLAN.md"' and '/render-html "rebuttal/REBUTTAL_DRAFT_rich.md"', and a worked checklist example. Minor gaps remain — trace saving is delegated to a chain in an external file and reviewer_route.py resolution is never concretely specified — so it sits just below the fully copy-paste-ready top anchor.

4 / 5

Workflow Clarity

Ten explicitly sequenced phases with resume support ('If rebuttal/REBUTTAL_STATE.md exists → resume from recorded phase'), a dedicated validation phase enumerating eight lints, and explicit feedback loops ('If any hard safety blocker remains → revise before finalizing', re-run lints in Phase 8, hard iteration caps) — matching the top anchor with checkpoints and error-recovery loops throughout.

5 / 5

Progressive Disclosure

The body is well-sectioned and signals references, but none of the referenced files exist in this bundle ('../shared-references/reviewer-backends.md', 'shared-references/reviewer-routing.md', 'shared-references/review-tracing.md', 'save_trace.sh', 'reviewer_route.py' are all dangling), and long specs that belong in reference files (the full REVISION_PLAN.md structure, reviewer calling conventions, defensive-move heuristics) are inlined — matching the 'some structure but could be better organized' anchor rather than the minimal-structure one below.

3 / 5

Total

15

/

20

Passed

Description

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

An excellent description: it states what the skill does through specific concrete actions, when to use it through quoted natural trigger phrases, and occupies a distinct niche. Third-person voice and tight phrasing with no padding.

DimensionReasoningScore

Specificity

The description lists four concrete actions spanning the full lifecycle — 'Parses external reviews', 'enforces coverage and grounding', 'drafts a safe text-only rebuttal under venue limits', 'manages follow-up rounds' — which matches the comprehensive-coverage anchor rather than the minor-gaps level below.

5 / 5

Completeness

Both questions are explicitly answered: the 'what' is the four concrete pipeline actions plus 'Submission rebuttal pipeline', and the 'when' is an explicit 'Use when user says...' clause with quoted trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Trigger phrases are natural user utterances with synonym coverage: 'rebuttal', 'reply to reviewers', 'ICML rebuttal', 'OpenReview response', 'answer external reviews' — users would literally say these; only near-duplicate variants like 'author response' are missing, keeping it above the mid-level anchor.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (post-submission rebuttal under venue limits) with distinct triggers ('ICML rebuttal', 'OpenReview response') that would not plausibly fire for other skills, matching the minimal-conflict-risk anchor.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository

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

Path

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