CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-review

Get a deep critical review of research from a selected reviewer (Codex by default, Gemini, Grok, Claude Code, or manual). Use when user says "review my research", "help me review", "get external review", or wants critical feedback on research ideas, papers, or experimental results.

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/research-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured, highly actionable workflow skill: the default Codex and manual reviewer routes are fully specified with copy-paste tool payloads, pinned models, and explicit convergence/validation checkpoints. The main costs are repetition of backend-routing rules across three sections, an inlined 40-line prompt block that could live in a reference file, and an empty '## Context: $ARGUMENTS' stub that adds noise without content.

Suggestions

Consolidate the reviewer-backend routing rules stated in 'Constants', 'Reviewer Calling Convention', and 'Key Rules' into a single section (or move fully to reviewer-backends.md) to remove the conciseness-draining repetition.

Move the 40-line SCOPE LIMITS prompt block and the prompt templates into a referenced file (e.g. references/review-prompt.md) so the core SKILL.md stays a lean overview, and add a references/ directory with the currently external shared files where possible.

Fill in or delete the empty '## Context: $ARGUMENTS' section and add explicit recovery guidance (what to do when the MCP is unavailable or a threadId is lost) to close the remaining workflow-clarity gaps.

DimensionReasoningScore

Conciseness

The body is dense and operational rather than padded with concepts Claude already knows, but it could be tightened: reviewer-backend routing rules are stated three times across 'Constants', 'Reviewer Calling Convention', and 'Key Rules'; the ~40-line SCOPE LIMITS block is inlined in the Step 2 prompt; and composed-mode rules plus tracing policy are summarized inline before linking out. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened'); it is not 4 because the redundancy across routing sections is more than minor trimming.

3 / 5

Actionability

The default and manual routes are fully concrete and copy-paste ready — exact tool names (mcp__codex__codex / mcp__codex__codex-reply), pinned model and config ("model: gpt-6-astra", "config: {\"model_reasoning_effort\": \"ultra\"}"), exact manual config JSON, a runnable 'claude mcp add' command, and complete prompt blocks. It falls short of anchor 5 because the antigravity/grok/claude-code call syntax is delegated to reviewer-backends.md, which is not part of this bundle, leaving minor gaps for those routes.

4 / 5

Workflow Clarity

A clear 5-step sequence (gather context → initial review → iterative dialogue → convergence → document) with explicit checkpoints: a convergence checklist ('Stop iterating when: both sides agree on the core claims...'), completion validation ('Check successful completion and actual file coverage before interpreting the response'), per-round tracing, and an explicit error path (emit REVIEW_UNAVAILABLE rather than guessing). It is not 5 because the '## Context: $ARGUMENTS' section is an empty stub and some recovery paths (e.g., a lost threadId or unavailable MCP) are only implied.

4 / 5

Progressive Disclosure

Good structure with clear sections (Constants, Calling Convention, Prerequisites, Workflow, Key Rules, Prompt Templates, Review Tracing) and well-signaled, one-level-deep links to shared-references files for backend contracts, tracing, cadence, and output composition. Minor gaps keep it at anchor 4 rather than 5: 'reviewer-routing.md' is referenced without a path, and the referenced ../shared-references/ files are not part of this skill's bundle, so navigation cannot be fully verified; the skill has no references/, scripts/, or assets/ directory of its own.

4 / 5

Total

15

/

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 strong description that clearly and explicitly states both what the skill does and when to use it, with natural quoted trigger phrases and a well-defined reviewer-backend niche. Its main weakness is under-representing the skill's concrete deliverables (multi-round review, experiment plans, claims matrices, mock reviews), which leaves the capability list thinner than the body warrants.

Suggestions

Mention 1-2 concrete deliverables in the description, e.g. 'runs multi-round adversarial review and produces experiment plans, claims matrices, and mock NeurIPS/ICML reviews' to raise specificity from domain-plus-one-action to several specific actions.

Add common trigger synonyms such as 'review my paper' or 'critique my draft' to broaden natural keyword coverage.

Narrow the generic 'help me review' trigger to 'help me review my research' to reduce overlap with code-review or document-review skills.

DimensionReasoningScore

Specificity

The description names the domain and one core action — "Get a deep critical review of research from a selected reviewer" — with backend enumeration ("Codex by default, Gemini, Grok, Claude Code, or manual"), but never surfaces the skill's other concrete capabilities (multi-round dialogue, experiment plans, claims matrices, mock reviews). This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); it is not 4 because listing reviewer backends parameterizes a single action rather than enumerating several distinct actions.

3 / 5

Completeness

It explicitly answers both questions: what ("Get a deep critical review of research from a selected reviewer") and when ("Use when user says 'review my research', 'help me review', 'get external review', or wants critical feedback on research ideas, papers, or experimental results") with concrete quoted trigger phrases. This directly matches the anchor-5 example structure; it is not 4 because the 'when' clause is already fully explicit with specific triggers.

5 / 5

Trigger Term Quality

Quoted triggers "review my research", "help me review", "get external review", and "critical feedback on research ideas, papers, or experimental results" are natural phrases a user would actually say, with some synonym coverage across idea/paper/result types. Good but not comprehensive — common variants like "review my paper", "critique my draft", or "get feedback on my manuscript" are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Research-qualified triggers and named external reviewer backends (Codex, Gemini, Grok, Claude Code, manual) carve a distinct niche with minimal conflict risk, matching anchor 4 (mostly distinct, minor overlap). It is not 5 because the bare trigger "help me review" is generic enough to overlap with code-review or general document-review skills.

4 / 5

Total

16

/

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: 3 suspicious

Warning

Total

13

/

16

Passed

Repository

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

Path

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