project-tracker-master
Use this skill whenever a user asks to "Update the project tracker," "Process meeting notes for the tracker," or "Generate a new task list update." It synthesizes raw meeting transcripts with existing project trackers, dynamically adapts to existing columns, generates a strictly formatted .docx tracker using a Node.js script (docx package), and automatically drafts a clean email summary.
Install with Tessl CLI
npx tessl i github:davidkogit/public-skills --skill project-tracker-master91
Quality
88%
Does it follow best practices?
Impact
95%
1.69xAverage score across 3 eval scenarios
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities, includes natural trigger phrases, and explicitly states when to use it. The description effectively combines workflow context (meeting notes to tracker to email) with technical specifics (.docx, Node.js), making it highly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'synthesizes raw meeting transcripts with existing project trackers', 'dynamically adapts to existing columns', 'generates a strictly formatted .docx tracker using a Node.js script', and 'automatically drafts a clean email summary'. | 3 / 3 |
Completeness | Explicitly answers both what (synthesizes transcripts, adapts columns, generates .docx, drafts email) AND when ('Use this skill whenever a user asks to...' with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would actually say: 'Update the project tracker', 'Process meeting notes for the tracker', 'Generate a new task list update'. Also includes relevant terms like 'meeting transcripts', 'project trackers', and 'email summary'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche combining meeting notes processing with project tracker updates and .docx generation. The specific workflow (meeting transcripts → tracker → email summary) and technical implementation (Node.js docx package) make it highly distinctive. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates good workflow structure with clear sequencing, validation steps, and fallback recovery. However, it lacks concrete executable examples - the reference to TRACKER_TEMPLATE.js without showing any sample code or data structure makes it harder to act on immediately. The email output format is described but not exemplified.
Suggestions
Add a minimal inline code example showing the expected rowsData structure or a sample Node.js snippet for generating one row
Include a brief example of the expected email summary output format to make the 'Key Completions / In Progress / Open Blockers' structure concrete
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations. Every section serves a clear purpose without padding or explaining concepts Claude already knows. | 3 / 3 |
Actionability | Provides clear steps and references a template script, but lacks executable code examples. The instruction to 'adapt the rowsData' is vague without showing the actual template structure or a concrete example. | 2 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit validation checkpoint, fallback recovery logic, and error handling. The workflow includes a feedback loop for debugging failures. | 3 / 3 |
Progressive Disclosure | References external file (scripts/TRACKER_TEMPLATE.js) appropriately, but the skill itself could benefit from a quick inline example of the expected rowsData format or output structure to reduce dependency on the external file for basic understanding. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.