Content
40%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |