parallel-integrate
Verify integration after parallel agent execution and generate report
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill parallel-integrate62
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 technical, lacking the explicit trigger guidance needed for Claude to reliably select it. While it hints at a specific domain (parallel agent workflows), it fails to explain what verification involves or provide natural language cues users would actually use.
Suggestions
Add a 'Use when...' clause specifying triggers like 'after running multiple agents', 'check agent results', 'parallel task completion', or 'multi-agent workflow'
Expand the capabilities to be more concrete, e.g., 'Validates outputs from parallel agent runs, checks for conflicts or inconsistencies, and generates a summary report of agent execution results'
Include natural user phrases such as 'agent results', 'check parallel tasks', 'agent output report', or 'verify agent work'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names two actions ('verify integration' and 'generate report') and a context ('parallel agent execution'), but lacks detail on what verification entails or what the report contains. | 2 / 3 |
Completeness | Only addresses 'what' at a high level. Completely missing a 'Use when...' clause or any explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Uses technical jargon ('parallel agent execution', 'integration') that users are unlikely to naturally say. Missing common variations or natural language triggers. | 1 / 3 |
Distinctiveness Conflict Risk | The 'parallel agent execution' context provides some specificity, but 'verify integration' and 'generate report' are generic enough to potentially overlap with other testing or reporting 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, highly actionable skill with clear workflows and validation checkpoints for a complex multi-step integration process. The main weakness is length - the skill could be more concise by extracting report templates and tech-specific checks into separate files, and removing the redundant checklist that duplicates the workflow steps.
Suggestions
Extract the detailed report template (integration-report.md format) into a separate REPORT-TEMPLATE.md file and reference it
Consider moving technology-specific integration checks (Django/TypeScript/Go) into separate files to reduce main skill length
Remove or consolidate the Integration Checklist section as it largely duplicates the numbered workflow steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy (e.g., the integration checklist largely duplicates the workflow steps, and the example section repeats information). Some sections could be tightened, though it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Provides fully executable bash commands, specific file paths, concrete JSON structures, and copy-paste ready code blocks for Django, TypeScript, and Go projects. The report templates are detailed and actionable. | 3 / 3 |
Workflow Clarity | Clear numbered sequence from step 0-9 with explicit validation checkpoints (branch status verification, contract compliance checks, boundary violation checks). Includes feedback loops ('After fixing issues, re-run') and clear conditional logic for different scenarios. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~300 lines) and could benefit from splitting detailed report templates or technology-specific checks into separate reference files. References to related commands are present but inline content is heavy. | 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.