AF grant-proposal-assistant
Grant proposal writing assistant for NIH (R01/R21), NSF and other mainstream funding applications. Triggers when user needs help writing specific aims, research strategy, budget justification, or other grant sections. Provides templates, section generators, and best practice guidance for competitive grant proposals.
As a process F 49/100 · Will not run — References files that are not bundled: references/budget_templates.xlsx
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 317 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: references/budget_templates.xlsx - note
frontmatter-keyunknown frontmatter key "status" - note
frontmatter-keyunknown frontmatter key "risk_level" - note
frontmatter-keyunknown frontmatter key "skill_type" - note
frontmatter-keyunknown frontmatter key "owner" - note
frontmatter-keyunknown frontmatter key "reviewer" - note
frontmatter-keyunknown frontmatter key "last_updated"
Process rating: all ten parameters 49/100
- 0Tools and files. 1 referenced file(s) missing: references/budget_templates.xlsx
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 44 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1175 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 317: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 44 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (4 of 5)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.