CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

grant-budget-justification

Use grant budget justification for academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries.

Quality

54%

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-budget-justification/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 has real bones — verified bundle files, executable audit commands, and a concrete CLI parameter table — but roughly three-quarters of it is duplicated generic policy boilerplate, and it never explains how to actually write a budget justification (no narrative examples, no per-category guidance, no agency-specific requirements). The single reference is properly wired but too thin to carry the skill's substance.

Suggestions

Consolidate the six overlapping policy sections (Error Handling, Input Validation, When Not to Use, Required Inputs, Output Contract, Failure Handling) into one short section and delete the generic template blocks (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Response Template) — 'Quick Check' is a duplicate of 'Audit-Ready Commands' and the first 'When to Use' bullet awkwardly re-pastes the description verbatim.

Add the skill's actual substance: a worked example of a narrative justification (e.g. the $50,000 mass spectrometer case written out in full) and per-category guidance for the listed Use Cases (Equipment, Personnel, Supplies, Travel), since currently only the script's internals know how to produce the deliverable.

Move agency-specific compliance details (NIH vs NSF requirements) into references/ and point to them from a single References section, keeping SKILL.md as a lean overview of when to use the skill and how to invoke the script.

DimensionReasoningScore

Conciseness

The body is heavily padded with boilerplate: 'Quick Check' duplicates 'Audit-Ready Commands' (both run `python -m py_compile scripts/main.py`), and at least six sections restate the same fallback policy ('Error Handling', 'Input Validation', 'When Not to Use', 'Required Inputs', 'Output Contract', 'Failure Handling', 'User Checkpoints'). Generic template sections ('Risk Assessment', 'Security Checklist', 'Evaluation Criteria', 'Lifecycle Status', 'Response Template') add no skill-specific value, matching 'Noticeably verbose; several unnecessary explanations or padded sections'. It avoids a 1 only because no section explains concepts Claude already knows and individual sections are short.

2 / 5

Actionability

Concrete elements exist — the executable commands (`python scripts/main.py --help`, `py_compile`), a real Parameters table for the CLI, and a verified reference file — but guidance for the skill's actual deliverable is missing: there is no example justification text, no narrative structure to follow, and the Example section is a single vague line ('Input: $50,000 for mass spectrometer / Output: Justification emphasizing essentiality and cost-sharing'). This fits 'Some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

The 5-step Workflow is sequenced and includes stop conditions ('stop early if the task would require unsupported assumptions') and a fallback path ('switch to the fallback path and state exactly what blocked full completion'), plus a separate 'Quick Validation' section. However, the steps are generic process boilerplate not tied to this skill's operations — no command invocations embedded in the sequence, no validate-output-against-agency-requirements step, and checkpoints are scattered across redundant sections rather than integrated. 'Steps listed but validation gaps; checkpoints missing or implicit' is the closest anchor.

3 / 5

Progressive Disclosure

Bundle structure is real and correctly linked: references/audit-reference.md exists, is one level deep, and is clearly signaled in a References section, and scripts/main.py exists as the documented entry point. But the SKILL.md inlines ~150 lines of template boilerplate (risk tables, checklists, lifecycle metadata like 'Next Review Date: 2026-03-06') that should be pruned or split, while the genuinely detailed material (how to write each justification type) is absent from both the body and the single thin reference. This matches 'Some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

11

/

20

Passed

Description

45%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 names a distinct domain but is circular and process-oriented: it never states what the skill concretely does and relies on generic workflow boilerplate as its trigger clause. Natural trigger keywords users would actually say (grant proposal, NIH, NSF, budget narrative) are absent.

Suggestions

State the concrete capability first, e.g. 'Generate narrative budget justifications (equipment, personnel, supplies, travel) for NIH and NSF grant proposals, including cost-benefit rationale and agency compliance checks.'

Replace the generic 'structured execution, explicit assumptions, and clear output boundaries' qualifier with concrete trigger phrases users would naturally say, such as 'Use when writing the budget justification or budget narrative section of a grant application.'

Include the key synonyms and agency names (NIH, NSF, budget narrative) as trigger terms to improve both recall and distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain ("grant budget justification") but never states a concrete action — phrases like "structured execution, explicit assumptions, and clear output boundaries" are generic process qualities, not capabilities. It never mentions what the skill actually produces (narrative budget justifications, cost-benefit rationale, agency compliance), matching the anchor 'Names the domain but actions are minimal or generic' rather than anchor 3, which requires 1-2 concrete actions.

2 / 5

Completeness

The 'what' is circular — 'Use grant budget justification' refers to the skill name without saying what it does (no mention of generating narrative justifications or cost rationales) — while an equivalent trigger clause exists ('for academic writing workflows that need structured execution...') but is vague process boilerplate rather than a concrete trigger. It sits between anchor 2 ('only when present without what') and anchor 3; the named domain and explicit trigger clause keep it at 3, but the missing action statement prevents anchor 4.

3 / 5

Trigger Term Quality

"grant budget justification" and "academic writing workflows" are natural, relevant phrases a user might say, but common variations and synonyms are missing: no "grant proposal", "NIH", "NSF", "budget narrative", "personnel costs", or "equipment". This fits 'Some relevant keywords but missing common variations or synonyms' — better than anchor 2 (which requires generic-only keywords) but short of anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

"grant budget justification" marks a fairly distinct niche, but the qualifier "academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries" is generic enough to overlap with any academic-writing or structured-writing skill. Somewhat specific but could still overlap with similar skills; the absence of distinct trigger phrases (NIH, NSF, budget narrative) keeps it below anchor 4.

3 / 5

Total

11

/

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-budget-justification/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.