CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

grant-funding-scout

NIH funding trend analysis to identify high-priority research areas.

Quality

63%

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/Evidence Insight/grant-funding-scout/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 has genuinely useful executable bones (commands, a full Parameters table, an error-handling path), but roughly half the body is template boilerplate and broken cross-references that waste context. Moving administrative sections into references and consolidating the triplicated validation commands would make the remaining content lean and actionable.

Suggestions

Remove or collapse the boilerplate sections (Key Features, Dependencies, Implementation Details, Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) — or move them to references/audit-reference.md — keeping only what Claude needs to execute.

Fix the broken cross-references ('See ## Prerequisites above' points to a section that comes later) and delete the duplicated py_compile command, which appears in Quick Check, Audit-Ready Commands, and Example Usage.

Replace the hardcoded example path ('20260318/scientific-skills/Evidence Insight/grant-funding-scout') with a runnable example such as `python scripts/main.py --research-area "cancer immunotherapy" --years 3 --format json`.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with template padding: 'Key Features' and 'Implementation Details' contain self-referential filler ('See ## Prerequisites above', 'See ## Workflow above' — both pointing to sections that appear later), the py_compile command is repeated three times, and administrative sections (Risk Assessment, Security Checklist, Lifecycle Status with a 'Next Review Date') add tokens without execution value.

2 / 5

Actionability

There are concrete commands (py_compile, --help, running scripts/main.py) and a complete Parameters table, but the guidance is incomplete: the 'Example run plan' is procedural rather than executable, the Example section is a one-line sketch, and the Example Usage embeds an unrunnable hardcoded path ('20260318/scientific-skills/...') rather than copy-paste ready commands.

3 / 5

Workflow Clarity

The five-step Workflow is clearly sequenced with explicit checkpoints — validate the request against scope, 'stop early if the task would require unsupported assumptions', and a documented fallback on failure — supported by an Error Handling section. It falls short of 5 because steps are framed abstractly ('Use the packaged script path') with no validate-fix-retry loop on outputs.

4 / 5

Progressive Disclosure

The single reference (references/audit-reference.md) is real, clearly signaled, and one level deep, but large amounts of content that belong in reference files — Security Checklist, Risk Assessment, Evaluation Criteria, Lifecycle Status — are inlined in SKILL.md, and the audit commands duplicate what the reference already documents.

3 / 5

Total

12

/

20

Passed

Description

53%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.

The description clearly and concisely states what the skill does in a distinct niche, but it omits any 'when to use' trigger guidance and only covers a thin slice of the natural vocabulary (missing 'grants', 'funding trends', 'awards'). Adding an explicit 'Use when...' clause with those synonyms would lift both completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when analyzing grant funding patterns, identifying emerging or oversaturated research areas, or planning grant positioning strategy.'

Broaden keyword coverage with natural synonyms: 'grants', 'grant trends', 'funding opportunities', 'awards', 'NIH RePORTER'.

State the concrete outputs (top-funded institutions, emerging topics, trend metrics) so the 'what' covers what the body actually delivers.

DimensionReasoningScore

Specificity

Names the domain ('NIH funding trend analysis') and one to two actions ('identify high-priority research areas'), but coverage is not comprehensive — no mention of data sources, outputs, or the analysis deliverables the body documents.

3 / 5

Completeness

The 'what' is clearly stated ('NIH funding trend analysis to identify high-priority research areas'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Contains relevant keywords like 'NIH', 'funding', and 'research areas', but misses natural variations users would say such as 'grants', 'grant trends', 'funding opportunities', or 'awards'.

3 / 5

Distinctiveness Conflict Risk

The NIH-funding niche is mostly distinct with specific terminology, though it carries minor overlap risk with sibling research-analysis skills that lack explicit trigger phrases to disambiguate.

4 / 5

Total

13

/

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/Evidence Insight/grant-funding-scout/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.