Generate agent-ready prompts from existing task specification files. Use when regenerating prompts after editing tasks, updating prompt templates, or preparing tasks for cpo execution.
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill parallel-prompt-generator80
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
75%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 has good structure with explicit 'Use when' guidance and a distinct niche around task specification and cpo execution. However, it could benefit from more specific capability details and more natural trigger terms that users would actually say instead of technical jargon like 'cpo'.
Suggestions
Expand the capabilities section to list specific actions (e.g., 'parse task specs, format prompts, validate output structure')
Add more natural trigger terms users might say, such as 'task prompts', 'agent prompts', 'prompt generation', or explain what 'cpo' stands for
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (agent-ready prompts, task specification files) and describes the action (generate), but lacks comprehensive detail about what specific operations are performed or what the output looks like. | 2 / 3 |
Completeness | Clearly answers both what ('Generate agent-ready prompts from existing task specification files') and when ('Use when regenerating prompts after editing tasks, updating prompt templates, or preparing tasks for cpo execution') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'regenerating prompts', 'prompt templates', 'cpo execution', and 'tasks', but 'cpo' is technical jargon that users may not naturally say, and common variations are limited. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'agent-ready prompts', 'task specification files', and 'cpo execution' creates a clear niche that is unlikely to conflict with general prompt or document skills. | 3 / 3 |
Total | 10 / 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, highly actionable skill that provides complete guidance for generating agent prompts. Its main strength is the concrete, copy-paste ready template and validation scripts. The primary weakness is length - some content (like the full prompt template) could be externalized, and there's minor redundancy between the requirements table and the template section.
Suggestions
Consider moving the full prompt template (Step 4) to a separate PROMPT-TEMPLATE.md file and referencing it, reducing the main skill file length
Remove the duplicate template requirements table at the top since Step 4 contains the authoritative template with all sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy - the template requirements table at the top duplicates information in Step 4, and some explanations could be tighter. The mermaid diagram adds visual clarity but the workflow is simple enough to not require it. | 2 / 3 |
Actionability | Provides fully executable guidance with concrete file paths, exact template structure, validation commands, and copy-paste ready bash scripts. The Step 4 template is complete and directly usable. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit validation checkpoints (pre-generation validation checklist, post-generation validation script). Error handling section covers edge cases with specific warning formats. Regeneration mode includes backup step. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~300 lines) and could benefit from splitting detailed templates or examples into separate reference files. The Related Skills table provides good navigation to related content. | 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 | |
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.