CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

grant-proposal-assistant

Assist with biomedical grant proposal drafting, structure, and revision; use when preparing fundable proposal sections, aligning aims and methods, or improving reviewer-facing clarity.

Quality

72%

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-proposal-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 has genuinely useful concrete material (CLI examples, parameter table, agency-specific page limits, real reference templates), but it is buried in extensive generic boilerplate that roughly doubles the document's length. Structural issues — a stale file reference, inconsistent section names between commands and the parameter table, and duplicated validation sections — further dilute it.

Suggestions

Cut the boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria/Test Cases, Lifecycle Status, and the overlapping Output Requirements/Output Contract/Failure Handling/Error Handling/User Checkpoints/Quick Validation policy blocks) down to one concise guardrails section, keeping only the Quick Check command once.

Fix the reference mismatch: 'references/budget_templates.xlsx' should be 'references/budget_templates.md', and link each reference file from the section that uses it (e.g., Best Practices → review_checklist.md, Specific Aims guidance → specific_aims_examples.md).

Replace the abstract 5-step policy Workflow with a concrete operational sequence for the skill's actual tasks (e.g., generate aims template → fill in with user inputs → validate against review_checklist.md → flag gaps), and reconcile the '--section project_summary' example with the documented section options.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: 'Quick Check' and 'Audit-Ready Commands' duplicate the same py_compile validation, and ~10 boilerplate policy sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status with a '2026-03-06' date, Output Requirements/Output Contract, Failure Handling/Error Handling, User Checkpoints, Quick Validation) overlap heavily and add little Claude doesn't already know. It is not a 1 because the core Usage, Parameters, and Agency-Specific sections are concrete, but the padding goes well beyond 'some unnecessary explanation'.

2 / 5

Actionability

Provides concrete, executable commands ('python scripts/main.py --section full --agency NIH --type R01 --output proposal.md'), a full parameter table, and a library usage example. Minor gaps keep it from a 5: 'items=[...]' is a placeholder, and 'Audit-Ready Commands' uses '--section project_summary', which is not among the documented options (aims, significance, approach, budget, full).

4 / 5

Workflow Clarity

A 5-step Workflow exists and a validation entry point is present (py_compile Quick Check, plus fallback handling in Error Handling), but the steps are abstract policy language ('Confirm the user objective', 'Return a structured result') rather than a concrete sequence for drafting/reviewing a proposal section. Checkpoints are partially implicit and the actual template-to-output sequence is never laid out, matching anchor 3 rather than 4.

3 / 5

Progressive Disclosure

References exist and are one level deep with descriptions, but the listed 'references/budget_templates.xlsx' does not exist (the actual file is budget_templates.md), reference files are never linked from the sections that need them (e.g., Best Practices does not point to review_checklist.md), and large amounts of generic policy content are inlined in SKILL.md instead of being split out. This fits anchor 3; not 4 because of the broken reference and buried navigation.

3 / 5

Total

12

/

20

Passed

Description

83%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: third-person, concise, with a clear 'what' and an explicit 'use when' trigger clause covering concrete scenarios. The main improvement opportunity is adding the agency and mechanism keywords (NIH, R01, NSF, grant application) that users naturally say and that the skill actually targets.

Suggestions

Add natural trigger keywords users would actually say — e.g., 'use when drafting or revising NIH R01/R21 or NSF grant applications, Specific Aims pages, or budget justifications' — to lift trigger-term coverage and distinctiveness.

Mention the review/critique capability in the description so it matches the skill's documented 'Review & Critique' feature.

DimensionReasoningScore

Specificity

Lists several specific actions — 'drafting, structure, and revision', 'preparing fundable proposal sections', 'aligning aims and methods', 'improving reviewer-facing clarity' — which matches anchor 4's 'several specific actions; minor gaps in coverage'. It is not 5 because capabilities the skill actually provides (budget justification, review/critique checklist) are omitted; not 3 because it goes beyond 1–2 actions.

4 / 5

Completeness

Clearly answers both questions with an explicit trigger clause: 'Assist with biomedical grant proposal drafting, structure, and revision; use when preparing fundable proposal sections, aligning aims and methods, or improving reviewer-facing clarity.' This matches anchor 5's 'clearly and explicitly answers both what AND when with concrete trigger phrases', and is well above anchor 4's weaker 'when'.

5 / 5

Trigger Term Quality

Natural terms like 'grant proposal', 'drafting', 'revision', and 'aims' are present, giving good keyword coverage (anchor 4). It falls short of anchor 5's comprehensive coverage because the most natural user vocabulary — agency and mechanism names like 'NIH', 'R01', 'R21', 'NSF', 'grant application', 'Specific Aims page' — is absent even though the skill targets those agencies.

4 / 5

Distinctiveness Conflict Risk

The 'biomedical grant proposal' niche with distinct triggers ('aligning aims and methods', 'fundable proposal sections') is mostly distinct with minor overlap risk against generic scientific-writing or manuscript-editing skills — matching anchor 4. It is not 5 because the description does not name agencies, so it could also fire for non-biomedical or non-grant writing-revision requests.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/grant-proposal-assistant/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.