integrate-command
Integrate a user or project command into Product Forge
59
42%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/claude-code-dev/skills/integrate-command/SKILL.mdQuality
Discovery
7%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 severely underdeveloped, providing almost no actionable information for Claude to determine when to select this skill. It lacks concrete actions, natural trigger terms, and explicit usage guidance. The only distinguishing element is the 'Product Forge' product name, but without context on what that is or what integration means in this context.
Suggestions
Add specific concrete actions describing what 'integrate' means (e.g., 'Register new CLI commands, configure command handlers, add command routing to Product Forge projects').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when adding new commands to Product Forge, setting up CLI integrations, or configuring project commands').
Explain what Product Forge is briefly and what types of commands can be integrated to help Claude understand the skill's scope.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Integrate a user or project command') without specifying concrete actions. It doesn't explain what integration entails or what specific tasks are performed. | 1 / 3 |
Completeness | Missing both clear 'what' (what does integration actually involve?) and 'when' (no 'Use when...' clause or explicit trigger guidance). The description fails to answer either question adequately. | 1 / 3 |
Trigger Term Quality | Contains technical jargon ('Product Forge') that users may not naturally use, and generic terms like 'command' and 'integrate' that lack specificity. Missing natural trigger terms users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Product Forge' provides some specificity to a particular system, but 'integrate a command' is generic enough to potentially conflict with other integration or command-related skills. | 2 / 3 |
Total | 5 / 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 command skill with excellent actionability and workflow clarity. The step-by-step execution instructions are concrete and include proper validation and error handling. Minor improvements could be made by trimming redundant content (the example workflow largely duplicates earlier sections) and tightening some explanations.
Suggestions
Remove or significantly condense the 'Example Workflow' section as it largely repeats the execution instructions and confirmation output
Consider whether the detailed error message templates need to be fully spelled out, or if a more concise format would suffice
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - the example workflow section largely repeats information already covered in the execution instructions, and some explanations could be tightened. | 2 / 3 |
Actionability | Provides fully executable bash commands, specific file paths, clear argument parsing, and concrete examples. The find commands, cp operations, and error messages are all copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 7-step sequence with explicit validation checkpoints (locate source, validate plugin, check conflicts). Includes error handling for each failure mode and uses AskUserQuestion for conflict resolution. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but everything is inline in one file. The detailed execution instructions could potentially be separated, though for a command of this complexity it's borderline acceptable. | 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 | |
- Repository
- jpoutrin/product-forge
- Commit
0ebe7ae
- 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.