CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

funding-trend-forecaster

Analyze funding abstracts and project metadata to identify topic shifts and forecast near-term grant priorities.

Quality

65%

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/funding-trend-forecaster/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 body is highly actionable — concrete commands, a parameter table, config and output examples, and an existing script and reference file — but it is heavily padded with templated boilerplate, self-referential filler, and duplicated sections, and buries inline content that should live in references. Tightening the structure and sequencing validation into the workflow would lift it substantially.

Suggestions

Delete the templated filler lines ('See `## Features` above for related details', 'See `## Usage` above', 'See `## Workflow` above') and merge the duplicated sections (Key Features into Features, Implementation Details into Workflow) — this padding drove the conciseness score of 2.

Move the full config.json example, the complete output JSON schema, the architecture tree, and the roadmap into files under references/ and link them from the relevant sections, keeping SKILL.md a lean overview.

Sequence validation inline in the Workflow steps (e.g. step 2: run 'python -m py_compile scripts/main.py' and 'python scripts/main.py --help' before executing the analysis) instead of scattering checkpoints across Quick Check and Audit-Ready Commands.

Fix the hardcoded build path in Example Usage ('cd "20260318/scientific-skills/Evidence Insight/funding-trend-forecaster"') so the commands are copy-paste runnable.

DimensionReasoningScore

Conciseness

The ~340-line body is noticeably verbose: templated filler ('See `## Features` above for related details', 'See `## Usage` above', 'See `## Workflow` above'), redundant overlapping sections (Key Features vs Features, Implementation Details vs Workflow vs Output Requirements), and padded boilerplate throughout. It avoids explaining concepts Claude already knows, so it stays above a 1, but several sections earn no token.

2 / 5

Actionability

Concrete, mostly executable guidance: real commands ('python -m py_compile scripts/main.py', 'python scripts/main.py --source nih --months 3', '--forecast --years 3'), a parameter table, a Python API example, and a full config example. Minor gaps — the Example Usage 'cd' path is a hardcoded build artifact, and the import surface of the API example is unverified — keep it below copy-paste-perfect.

4 / 5

Workflow Clarity

A 5-step Workflow sequence exists and validation commands (py_compile, --help) plus error-handling fallbacks are documented, but the checkpoints are scattered across Quick Check, Audit-Ready Commands, and Error Handling rather than sequenced inline, and steps are abstract ('Use the packaged script path or the documented reasoning path'). Sequence present, checkpoints implicit — a solid 3.

3 / 5

Progressive Disclosure

Headers provide structure and one real one-level-deep reference exists (references/audit-reference.md is a real file), but large content that belongs in separate files is inlined (full config.json example, complete output JSON schema, architecture tree, roadmap), and the single reference is listed at the bottom rather than clearly signaled from the relevant sections.

3 / 5

Total

12

/

20

Passed

Description

66%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 specific, third-person description with concrete actions and a well-defined domain, but it lacks any explicit 'Use when...' trigger guidance, which caps completeness and weakens discoverability. Adding trigger phrases with common synonyms (funding trends, grant forecasting, agency names) would round it out.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user mentions grant funding, research funding trends, NIH/NSF/Horizon Europe awards, or wants to forecast funding priorities' — its absence caps completeness at 3.

Include natural trigger synonyms users would say, such as 'funding trends', 'grant forecasting', and agency names (NIH, NSF, Horizon Europe), to broaden keyword coverage.

Optionally mention the deliverable format (trend reports/forecasts) to sharpen the 'what' and further reduce overlap with generic data-analysis skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Analyze funding abstracts and project metadata', 'identify topic shifts', 'forecast near-term grant priorities' — with a clearly named domain. It falls short of a 5 because it omits notable capabilities (multi-source data collection from NIH/NSF/Horizon Europe, visualization/reporting), leaving minor gaps in coverage.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is entirely absent rather than merely weakly implied, so completeness is capped at 3 per the judging guidelines. It is not a 2 because the 'what' half is specific and multi-action.

3 / 5

Trigger Term Quality

Natural phrases like 'funding abstracts', 'topic shifts', and 'grant priorities' are terms users would plausibly say when needing this skill. A few common variations are missing (e.g., 'funding trends', 'grant forecasting', agency names like NIH/NSF), keeping it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The research-funding/grant-forecasting niche is fairly distinct with triggers unlikely to fire for unrelated skills. Minor overlap risk exists with general data-analysis or research-literature skills, especially since no 'when' guidance narrows the trigger surface.

4 / 5

Total

15

/

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/funding-trend-forecaster/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.