prd-progress
Show implementation progress from linked tasks
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill prd-progress63
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
22%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 description is too brief and vague to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient natural language keywords. The phrase 'linked tasks' hints at a specific integration but doesn't clarify what system or how the linking works.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios like 'Use when the user asks about task completion, project progress, or wants to see status of linked work items'
Expand the capabilities with specific actions such as 'Displays completion percentages, visualizes task dependencies, summarizes blocked items, and generates progress reports from linked tasks'
Include natural trigger terms users would say: 'project status', 'task progress', 'how much is done', 'sprint progress', 'milestone tracking'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('show implementation progress') without specifying concrete actions like tracking completion percentages, displaying task statuses, generating reports, or visualizing timelines. | 1 / 3 |
Completeness | Only partially addresses 'what' (showing progress) and completely lacks 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 ('implementation progress', 'linked tasks') but misses common variations users might say like 'project status', 'task tracking', 'progress report', 'milestone', or 'sprint progress'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Linked tasks' provides some specificity suggesting integration with a task management system, but 'implementation progress' is generic enough to potentially conflict with project management, reporting, or dashboard skills. | 2 / 3 |
Total | 6 / 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 is a well-structured skill with excellent actionability - the task parsing rules, output formats, and execution steps are concrete and implementable. The main weakness is verbosity in the output format examples, which could be condensed or moved to a reference file. The workflow is clear with good error handling coverage.
Suggestions
Consider moving the detailed output format examples to a separate FORMATS.md reference file, keeping only the simple format inline
Remove obvious implementation tips like 'don't double-count' that Claude would naturally handle
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the three output format examples are quite verbose and could be condensed. The implementation tips section adds value but some points are obvious to Claude. | 2 / 3 |
Actionability | Highly actionable with concrete task parsing rules, specific markdown formats to recognize, complete output examples in all three formats, and clear execution steps. Claude can directly implement this. | 3 / 3 |
Workflow Clarity | Clear 6-step execution sequence with explicit fallback logic for finding task files. Error handling section covers edge cases. The workflow is well-structured for a parsing/display task. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the three complete output format examples make this quite long. The detailed format examples could be moved to a separate reference file. | 2 / 3 |
Total | 10 / 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.