CtrlK
BlogDocsLog inGet started
Tessl Logo

grant-mock-reviewer

Simulate structured grant peer review for biomedical proposals; use when stress-testing significance, innovation, approach, feasibility, and reviewer-facing weaknesses before submission.

53

Quality

60%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/grant-mock-reviewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is over-long and padded with generic boilerplate and redundant sections, with a broken templated 'When to Use' line. It offers concrete CLI commands and real one-level-deep references, but the core review workflow is delegated to a script rather than explained, and reference-worthy content is duplicated inline.

Suggestions

Remove generic boilerplate Claude already knows (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Response Template, User Checkpoints) and merge the redundant Error Handling / Failure Handling / When Not to Use / Input Validation sections into one concise block.

Move the inline NIH Scoring System tables and Common Weaknesses Detected lists into the existing reference files, keeping SKILL.md a lean overview that links to them.

Fix the broken 'When to Use' line ('Use this skill when the task needs Simulates NIH study section peer review for grant proposals. Triggers.') and replace the generic Workflow with a concrete, sequenced review procedure with explicit validation checkpoints.

DimensionReasoningScore

Conciseness

The ~350-line body is padded with generic boilerplate Claude already knows (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Response Template, User Checkpoints) and overlapping sections (Error Handling / Failure Handling / When Not to Use / Input Validation), plus a broken templated line ('Use this skill when the task needs Simulates NIH study section peer review for grant proposals. Triggers.'). This matches the verbose/padded anchor rather than the mostly-efficient level above.

1 / 3

Actionability

Provides concrete, copy-paste CLI commands ('python3 scripts/main.py --input proposal.pdf --format pdf --output review.md'), a parameters table, and a library example, but large portions are descriptive reference material rather than executable instruction, and no concrete procedure lets Claude perform a review without delegating to the bundled script. Not a 3 because guidance is incomplete as standalone instruction.

2 / 3

Workflow Clarity

A 5-step Workflow and a Quick Validation section are present with some checkpoints, but the steps are generic process boilerplate ('confirm objective', 'validate scope', 'use the script') rather than a sequenced review procedure, and validation is implicit. Not a 3 because checkpoints are not explicit feedback loops tied to the core task.

2 / 3

Progressive Disclosure

Five real reference files are listed one level deep with clear signals in a References section, but the body inlines large duplicated content (NIH Scoring System tables, Common Weaknesses Detected) that belongs in those references, making the SKILL.md itself a monolithic wall of text. Not a 3 because content that should be separate is inline alongside the references.

2 / 3

Total

7

/

12

Passed

Description

85%

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 strong: it concisely states a concrete capability, includes an explicit 'use when' trigger, and occupies a clear niche. The main gap is trigger-term coverage, which misses the most common user phrasings (NIH, R01, study section, grant scoring).

DimensionReasoningScore

Specificity

Names the domain ('structured grant peer review for biomedical proposals') and lists multiple concrete actions via 'stress-testing significance, innovation, approach, feasibility, and reviewer-facing weaknesses'. This matches the anchor listing several specific concrete actions, not the single-action level below.

3 / 3

Completeness

Explicitly states what it does ('Simulate structured grant peer review for biomedical proposals') and when to use it via an explicit 'use when stress-testing ... before submission' clause, satisfying both what and when. Clearly above the level where 'when' is only implied.

3 / 3

Trigger Term Quality

Includes relevant natural terms ('grant peer review', 'biomedical proposals', 'before submission', named review criteria), but omits common variations a user would actually say such as 'NIH', 'R01', 'study section', or 'score my grant'. Not the top level because coverage of natural phrasings is incomplete.

2 / 3

Distinctiveness Conflict Risk

The biomedical grant peer-review niche with criterion-specific triggers is clearly distinct from general writing or document skills and unlikely to fire for the wrong skill. Not a 2 because the trigger scope is specific rather than broadly overlapping.

3 / 3

Total

11

/

12

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.

Validation15 / 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
aipoch/medical-research-skills
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.