parallel-validate-prompts
Validate and fix parallel prompts for required sections
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill parallel-validate-prompts65
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
17%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 terse and relies on domain-specific jargon without explaining what parallel prompts are or when this skill should be used. It lacks natural trigger terms users would say and provides no explicit guidance for skill selection. The description needs significant expansion to be useful for skill routing.
Suggestions
Add a 'Use when...' clause explaining trigger scenarios (e.g., 'Use when validating prompt files, checking prompt structure, or when user mentions parallel prompts or prompt sections')
Expand the capabilities to explain what 'required sections' means and what specific validation/fixes are performed (e.g., 'Checks for missing headers, validates section ordering, adds required metadata')
Include natural language trigger terms users might actually say (e.g., 'prompt validation', 'check my prompts', 'fix prompt format', 'prompt structure')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (parallel prompts) and two actions (validate and fix), but lacks detail on what validation entails or what 'required sections' means. Not comprehensive enough for a 3. | 2 / 3 |
Completeness | Only addresses 'what' at a surface level. Completely missing a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Uses technical jargon ('parallel prompts', 'required sections') that users are unlikely to naturally say. Missing common variations or natural language triggers. | 1 / 3 |
Distinctiveness Conflict Risk | 'Parallel prompts' is somewhat specific terminology that narrows the domain, but 'validate and fix' and 'required sections' are generic enough to potentially overlap with other validation or linting skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%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 and workflow clarity. The step-by-step execution instructions are concrete and include proper validation checkpoints and error recovery paths. Minor verbosity in duplicated section listings and lengthy output examples slightly reduce token efficiency, but overall the skill provides clear, executable guidance.
Suggestions
Consolidate the required sections information - it appears both in the 'Required Sections' table and again in the Python REQUIRED_SECTIONS list. Keep only the code version with inline comments for purpose.
Shorten the verbose output example - showing 2 files (one pass, one fail) would be sufficient instead of implying all 5 files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the required sections table appears twice (once in 'Required Sections' and again in the validation code), and the verbose output example is quite lengthy when a shorter example would suffice. | 2 / 3 |
Actionability | Provides fully executable guidance with concrete bash commands, Python code for validation logic, specific file paths, exact section markers to check for, and complete output format examples that are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 6-step numbered workflow with explicit validation checkpoints, error handling paths, backup creation before fixes, and a re-validation recommendation after fixes. Exit codes are clearly defined for different outcomes. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from usage to arguments to detailed execution instructions. References to related commands and skills are clearly signaled at the end without deep nesting. | 3 / 3 |
Total | 11 / 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.