Lists multiple specific concrete actions: formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements. Also names specific agencies (NSF, NIH, DOE, DARPA, Taiwan NSTC).

The 'what' is well-covered with specific actions and agencies, but there is no explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the nature of the tasks described, which caps this at 2 per the rubric guidelines.

Includes strong natural keywords users would say: 'research proposals', 'NSF', 'NIH', 'DOE', 'DARPA', 'budget preparation', 'broader impacts', 'significance statements'. These are terms researchers naturally use when seeking grant writing help.

Highly distinctive niche targeting competitive research grant proposals for specific funding agencies. The combination of agency names and grant-specific terminology (broader impacts, significance statements) makes it very unlikely to conflict with other skills.

Extremely verbose at 500+ lines. Extensively explains concepts Claude already knows (what a PDF is equivalent: what NSF is, what broader impacts are, basic writing advice like 'use active voice', 'avoid jargon'). Lists of common mistakes, writing principles, and persuasion strategies are generic knowledge that waste tokens. The 'When to Use This Skill' section is entirely unnecessary.

Despite its length, the skill provides almost no concrete, executable guidance. There are no actual proposal text examples, no template fill-in patterns, no specific language to use. It reads as a textbook overview of grant writing rather than actionable instructions. The only concrete command is the schematic generation script, which is tangential to grant writing itself.

The Phase 1-5 workflow for grant development is reasonably well-sequenced with clear phases and outputs. However, it lacks validation checkpoints (e.g., no explicit 'verify compliance with page limits before proceeding' or 'check all review criteria are addressed'). The workflow is more of a project management timeline than an operational workflow for Claude to follow when writing.

References to external files (references/*.md, assets/*.md) are present and well-organized, which is good. However, the main SKILL.md contains enormous amounts of content that should be in those reference files instead—agency-specific details, review criteria, proposal types, and common mistakes are all inline rather than delegated, creating a monolithic document.