grant-gantt-chart-gen
Create project timeline visualizations for grant proposals
Install with Tessl CLI
npx tessl i github:aipoch/medical-research-skills --skill grant-gantt-chart-gen41
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 be effective for skill selection. It lacks explicit trigger guidance, comprehensive capability details, and natural keyword variations that would help Claude confidently choose this skill over alternatives.
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 project planning.'
Expand the capability list to include specific actions: 'Create Gantt charts, milestone timelines, and project schedule visualizations for grant proposals. Supports phase breakdowns, deliverable mapping, and budget period alignment.'
Include natural keyword variations users might say: 'grant timeline', 'project schedule', 'Gantt chart', 'funding proposal timeline', 'research project plan', 'milestone chart'.
| 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 | Only describes what it does at a high level; completely missing a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('project timeline', 'grant proposals', 'visualizations') that users might say, but missing common variations 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 grant writing 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 provides a basic CLI interface description but lacks the essential actionable content needed for execution. The milestone CSV format is never specified, no examples are provided, and the document is padded with generic template sections (Risk Assessment, Security Checklist, Evaluation Criteria) that don't help Claude perform the task.
Suggestions
Add a concrete example of the milestones.csv format with sample data (columns, date formats, required fields)
Include a sample output image or description of what the generated Gantt chart looks like
Remove or drastically reduce the boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that don't provide actionable guidance
Add a workflow showing how to iterate: create CSV → generate chart → review → adjust parameters → regenerate
| 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 this 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 explanation of the CSV format required, no example milestone data, and no sample output. Claude cannot execute this without knowing the expected input structure. | 1 / 3 |
Workflow Clarity | There is no workflow described - just a single command with parameters. No guidance on creating the milestone CSV, no validation steps, no error handling process, and no feedback loop for iterating on the visualization. | 1 / 3 |
Progressive Disclosure | The content is organized with clear sections and a parameter table, but it's a flat structure with no references to detailed documentation. The boilerplate sections clutter the main content without adding navigational value. | 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 | |
- 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.