CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

74%

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 ./scientific-skills/Academic Writing/grant-mock-reviewer/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 skill delivers strong actionability with executable commands, a parameter reference, and explicit error-handling and validation guidance, and its reference bundle is well-signaled and one level deep. However, it is held back by heavy inlining of content duplicated in its own reference files and by generic boilerplate sections that inflate token cost without adding skill-specific guidance.

Suggestions

Replace the inlined NIH Scoring System tables and Common Weaknesses Detected lists with brief pointers to references/nih_scoring_rubric.md and references/common_weaknesses_catalog.md, keeping only a short summary of the 1-9 scale and the five criteria.

Trim the generic template sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements/Contract boilerplate) down to only the items that carry skill-specific guidance.

Merge the Quick Check and Audit-Ready Commands sections into one validation block, remove the duplicated '--help' invocation, and either include the referenced requirements.txt or drop the pip install prerequisite.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: the NIH scoring tables and the ~60-line Common Weaknesses catalog duplicate content already shipped in references/nih_scoring_rubric.md and references/common_weaknesses_catalog.md, and generic boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Contract) pad the file without skill-specific value.

2 / 5

Actionability

Concrete, copy-paste-ready CLI commands cover the common cases (full review, section-only, focus, scores-only, compare) alongside a library usage example and a full parameter table. Minor gaps keep it below 5: the Prerequisites section references a requirements.txt that is not present in the bundle, and the Audit-Ready Commands block repeats 'python scripts/main.py --help' twice and duplicates the Quick Check.

4 / 5

Workflow Clarity

The 5-step Workflow is clearly sequenced with a concrete validation entry point (py_compile quick check) and explicit Error Handling / Failure Handling sections describing fallback paths. Not 5 because the workflow steps themselves are somewhat abstract ('Validate that the request matches the documented scope') and there is no validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

The References section clearly signals all five one-level-deep reference files, but substantial content that belongs in those files (the NIH scoring tables and the Common Weaknesses lists) is inlined in SKILL.md instead of being pointed to, matching the 'content that should be separate is inline' anchor.

3 / 5

Total

13

/

20

Passed

Description

82%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: it clearly and explicitly states what the skill does and when to use it, in third person, with a well-defined niche and natural trigger phrases. Its only weaknesses are a somewhat narrow statement of capabilities and missing common synonyms users would say (NIH, study section, R01).

DimensionReasoningScore

Specificity

The description names the domain ('biomedical proposals') and 1-2 concrete actions ('Simulate structured grant peer review', 'stress-testing' the five named criteria), but does not comprehensively list the skill's actions such as scoring, critique generation, or summary statements. The named criteria elaborate one action rather than constituting several distinct actions, so it fits the score-3 anchor better than score 4.

3 / 5

Completeness

It explicitly answers both what ('Simulate structured grant peer review for biomedical proposals') and when ('use when stress-testing significance, innovation, approach, feasibility, and reviewer-facing weaknesses before submission') with a concrete trigger phrase, matching the score-5 anchor exactly.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ('grant peer review', 'biomedical proposals', 'significance, innovation, approach, feasibility', 'before submission'), but common variations a user would actually say are missing — 'NIH', 'study section', 'R01', 'mock review', 'score my grant'. Good coverage with a few gaps matches score 4 rather than the comprehensive synonym-and-extension coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

'Simulate structured grant peer review for biomedical proposals' carves out a clear niche with distinct triggers (grant review, stress-testing criteria, pre-submission), so the risk of triggering for an unrelated skill is minimal.

5 / 5

Total

17

/

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

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/grant-mock-reviewer/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.