CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-grants

Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan's NSTC when you need agency-compliant narratives, budgets, and review-criteria alignment for a specific solicitation/FOA/BAA.

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/Protocol Design/research-grants/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 body provides genuinely concrete, domain-specific guidance with a sequenced example workflow and useful criteria checklists, but bundle integrity undermines it: all four referenced scripts are missing, 5 of 12 references do not exist, and the three asset templates are undiscoverable while ~80 lines of their content are duplicated inline. The structure and signaling are good, but the paths do not resolve and the inline/asset split is not leveraged.

Suggestions

Ship the four referenced scripts (compliance_checker.py, budget_calculator.py, deadline_tracker.py, generate_schematic.py) or remove the 'complete, runnable workflow' framing and its bash examples, since no scripts/ directory exists in the bundle.

Restore bundle integrity for references: add the five missing files (budget_preparation.md, review_criteria.md, timeline_planning.md, team_building.md, resubmission_strategies.md) or prune them from the reference list so every listed path resolves.

Reference the three asset templates (assets/nih_specific_aims_template.md, assets/budget_justification_template.md, assets/nsf_project_summary_template.md) from SKILL.md and replace the ~80 lines of inline proposal and budget skeletons with brief pointers, also deduplicating agency guidance between 'Key Features' and 'Implementation Details' and dropping the maintainer-facing requirements.txt note.

DimensionReasoningScore

Conciseness

Mostly efficient domain content (agency criteria, milestone/risk parameters, resubmission mechanics) that Claude does not already know, but ~80 lines of inline templates (the NIH proposal skeleton and budget justification outline) duplicate files already present in assets/, agency guidance appears in both 'Key Features' and 'Implementation Details', and the maintainer-facing note about adding a requirements.txt is runtime-irrelevant padding. Not a 2 because the bulk is genuinely instructional rather than explanation of known concepts.

3 / 5

Actionability

The 4-step example workflow, copy-paste markdown skeletons, and concrete criteria (milestones 'Measurable/Time-bound/Decision-linked', risk chains 'failure mode → detection signal → mitigation → fallback') are strong, but every bash command targets a scripts/ directory that does not exist in the bundle (compliance_checker.py, generate_schematic.py, budget_calculator.py, deadline_tracker.py), so the claimed 'complete, runnable workflow' is not runnable. Not a 4 because missing key executable pieces is more than a minor gap.

3 / 5

Workflow Clarity

The numbered Example Usage (generate diagrams → draft skeleton → run compliance check → produce budget justification) gives a clear sequence, and step 3 'Run a basic formatting/compliance check (if available)' provides a validation checkpoint, complemented by budget-to-workplan consistency checks in Implementation Details. Not a 5 because the validation step is hedged ('if available') with no explicit fix-and-retry feedback loop; not a 3 because the sequence and checkpoints are more complete than 'checkpoints missing or implicit'.

4 / 5

Progressive Disclosure

References are clearly signaled in a flat, one-level bullet list, but scored against the actual bundle: 5 of the 12 listed reference files are missing (budget_preparation, review_criteria, timeline_planning, team_building, resubmission_strategies), the entire scripts/ directory is absent, and the 3 asset templates are never referenced from SKILL.md while their content is re-inlined in the body. This mixed picture fits anchor 3 ('could be better organized; content that should be separate is inline') better than anchor 4's 'minor organization gaps'.

3 / 5

Total

13

/

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: it defines a clear niche (agency-specific grant proposals) with an explicit 'when you need ... for a specific solicitation/FOA/BAA' trigger clause and good keyword coverage across all five agencies. Its only flaws are the second-person trigger phrasing (costing it specificity) and the absence of the single most natural user term, 'grant'.

DimensionReasoningScore

Specificity

The description lists several concrete deliverable-oriented actions — 'Write competitive research proposals', 'agency-compliant narratives, budgets, and review-criteria alignment' — which fits anchor 4, but the trigger clause 'when you need agency-compliant narratives' is second person, so the third-person-voice rule reduces the score by 1. It is not a 2 because the domain (grant proposals for five named agencies) and deliverables are far more concrete than 'names the domain but actions are minimal'.

3 / 5

Completeness

Both questions are answered explicitly with concrete trigger phrases: what — 'Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan's NSTC'; when — 'when you need agency-compliant narratives, budgets, and review-criteria alignment for a specific solicitation/FOA/BAA'. This matches the anchor-5 example structure and is not a 4, since the 'when' clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'research proposals', 'NSF, NIH, DOE, DARPA, and Taiwan's NSTC', 'narratives', 'budgets', 'solicitation/FOA/BAA'. It falls short of anchor 5 because the most natural user phrasing — 'grant', 'grant application', 'funding' — never appears, and no synonyms or award-mechanism terms (e.g., R01) are included.

4 / 5

Distinctiveness Conflict Risk

Naming five specific funding agencies and solicitation types (FOA/BAA) creates a clear, mostly distinct niche with strong trigger terms. It is not a 5 because 'research proposals' and 'narratives, budgets' could still pull in generic proposal-, scientific-, or technical-writing requests when no agency is mentioned, a minor overlap with closely related skills.

4 / 5

Total

16

/

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: 12 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Protocol Design/research-grants/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.