CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-grant-writer-us

Guides a US nonprofit from grant prospect research to a submitted federal or foundation proposal with budget, narrative and compliance checks. Use when: Generate compliant SF-424A budget justifications with 15% MTDC rates; Draft SBIR Phase I skeletons for NSF, NIH, and DoD agencies; Create logic models to align grant activities with measurable outcomes.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-business-operations/skills/nex-grant-writer-us/SKILL.md

The canonical home for this skill is nex-grant-writer-us in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

40%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 reads as a well-organized public-facing product page rather than an operational skill: it describes what the packaged product does without giving Claude any executable procedure, templates, or validation steps. It is concise and honest about limitations, but a working skill needs the actual workflow instructions the removed scripts and templates contained.

Suggestions

Replace the descriptive 'What it does' bullets with a numbered, step-by-step workflow (prospect research → fit scoring → skeleton → budget + narrative → compliance check) with explicit inputs and outputs at each step.

Inline the core actionable material — e.g., the SF-424A budget justification structure, the logic model template, and a compliance checklist keyed to page limits, attachments, and registration prerequisites — or restore them as reference files the body links to.

Add validation checkpoints for the submission compliance step (what to check against the funder announcement and what to do when a requirement fails) and trim the promotional footer and FAQ that duplicate the description.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the promotional footer ('More skills, including the paid catalog'), the origin note, and an FAQ that restates the description add tokens that do not help Claude execute the skill.

3 / 5

Actionability

The body describes capabilities ('Builds the proposal skeleton required by the funder', 'Runs a submission compliance check') rather than instructing how to do them; the only concrete detail is the MTDC exclusion rule in the example, and the scripts and templates that would make it actionable are explicitly absent.

2 / 5

Workflow Clarity

The 'What it does' bullets imply a pipeline order (research, skeleton, budget, compliance) but the steps are poorly defined, with no explicit sequence, no per-step guidance, and no validation checkpoints for the compliance check it claims to run.

2 / 5

Progressive Disclosure

Sections are well-organized (What it does, Use cases, Known limitations, Example, Questions) with no broken file references, but the note that 'Scripts, extension source, and templates from the original package are not in this folder' leaves the detailed material referenced yet unavailable, a minor organization gap.

4 / 5

Total

11

/

20

Passed

Description

83%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: third-person voice, concrete actions, specific regulatory artifacts, and an explicit 'Use when' clause. Its only weakness is a when-clause narrower than the stated capability, which could miss the most common user phrasing ('help me write a grant proposal').

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with specific artifacts — 'grant prospect research', 'SF-424A budget justifications with 15% MTDC rates', 'SBIR Phase I skeletons for NSF, NIH, and DoD', 'logic models' — covering research, budget, narrative, and compliance comprehensively.

5 / 5

Completeness

It answers both 'what' ('Guides a US nonprofit from grant prospect research to a submitted federal or foundation proposal') and 'when' (explicit 'Use when:' clause), but the when-clause covers only three narrow task triggers and omits the broader, most natural trigger of writing a grant proposal.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('grant', 'federal', 'proposal', 'budget justification', 'SBIR', 'logic model', agency names), but common variations like 'grant application', 'RFP', or 'grant writing' are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly staked out by US-specific grant artifacts (SF-424A, MTDC de minimis rate, SBIR/STTR, federal/foundation funders), making accidental triggering by unrelated skills very unlikely.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-business-operations/skills/nex-grant-writer-us/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.