Create project timeline visualizations for grant proposals
51
27%
Does it follow best practices?
Impact
95%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Academic Writing/grant-gantt-chart-gen/SKILL.mdQuality
Discovery
32%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 identifies a specific niche (grant proposal timelines) but is too brief to effectively guide skill selection. It lacks explicit trigger conditions, comprehensive capability details, and natural keyword variations that users might employ when requesting this functionality.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when creating Gantt charts, project schedules, or timeline graphics for grant applications, funding proposals, or research submissions.'
Expand specific capabilities: mention chart types (Gantt, milestone), features (dependencies, phases, deliverables), and output formats.
Include natural keyword variations users might say: 'Gantt chart', 'project schedule', 'funding proposal timeline', 'research timeline', 'milestone visualization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (project timeline visualizations, grant proposals) and one action (create), but lacks comprehensive detail about what specific capabilities are involved (e.g., Gantt charts, milestones, dependencies, export formats). | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('project timeline', 'grant proposals', 'visualizations') but misses common variations users might say like 'Gantt chart', 'project schedule', 'funding proposal', 'research timeline', or 'milestone chart'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'grant proposals' and 'timeline visualizations' provides some specificity, but could overlap with general visualization skills, project management skills, or document creation skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a CLI reference card with extensive boilerplate but lacks the core content needed to be actionable. It tells Claude to run a script but provides no script implementation, no input format examples, and no actual guidance on creating Gantt charts. The Risk Assessment and Evaluation Criteria sections consume tokens without adding operational value.
Suggestions
Add an example of the expected CSV input format with sample milestone data (columns, date formats, required fields)
Include the actual Python implementation or reference where the script can be found, since 'scripts/main.py' doesn't exist without it
Add a workflow showing: 1) prepare milestone CSV, 2) run command, 3) verify output meets grant requirements, 4) iterate if needed
Remove or drastically reduce the Risk Assessment, Security Checklist, Evaluation Criteria, and Lifecycle Status sections - these are template boilerplate that don't help Claude execute the task
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes substantial boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add little value for Claude executing the task. The core usage information is reasonably concise, but nearly half the document is template filler. | 2 / 3 |
Actionability | The skill provides only a CLI command with no actual implementation details. There's no code showing how to create the Gantt chart, no example of the CSV input format, and no guidance on what the script actually does internally. Claude cannot execute this without the actual script. | 1 / 3 |
Workflow Clarity | There is no workflow described - just a single command invocation. No steps for preparing input data, no validation checkpoints, no error handling guidance, and no feedback loop for verifying the output meets grant proposal requirements. | 1 / 3 |
Progressive Disclosure | The content is organized with clear sections and a parameter table, which aids navigation. However, there are no references to additional documentation for advanced features, examples, or the actual script implementation that would be needed. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
4a48721
Table of Contents
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.