Copy a command from Product Forge to user or project level
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill copy-command67
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
32%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 lacks critical information for skill selection. While it mentions the specific product 'Product Forge' and the action of copying commands, it fails to explain what this actually accomplishes, what triggers should invoke it, or provide enough context for Claude to distinguish it from other skills.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when user wants to copy Product Forge commands', 'configure project settings', or 'set up user-level commands'
Expand the capabilities description to explain what 'copying a command' means in practice - does it duplicate configurations, export settings, or transfer command definitions?
Include natural trigger terms users might say, such as 'duplicate command', 'copy configuration', 'move command to project', or specific Product Forge terminology
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific action ('Copy a command') and mentions the domain ('Product Forge', 'user or project level'), but lacks detail about what copying entails or what commands are involved. | 2 / 3 |
Completeness | Describes what it does at a basic level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Product Forge', 'command', 'user level', and 'project level' which are relevant terms, but 'Product Forge' is a specific product name that users may not naturally mention, and common variations are missing. | 2 / 3 |
Distinctiveness Conflict Risk | 'Product Forge' provides some distinctiveness as a specific product, but 'copy a command' is generic enough that it could overlap with other command-copying or configuration skills. | 2 / 3 |
Total | 7 / 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 and workflow clarity. The execution instructions provide clear, numbered steps with concrete commands and proper error handling. Minor improvements could be made in conciseness by reducing redundancy between sections and tightening the confirmation message templates.
Suggestions
Remove the 'Directory Structure' section as it duplicates information already conveyed in the Arguments section and execution instructions
Condense the confirmation message template - Claude can generate appropriate success messages without verbose templates
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - the directory structure section repeats information already shown in the arguments section, and the confirmation messages are more verbose than necessary. | 2 / 3 |
Actionability | Provides fully executable bash commands, specific file paths, and concrete examples for every operation. The usage examples are copy-paste ready and the execution instructions include exact commands to run. | 3 / 3 |
Workflow Clarity | Clear numbered sequences for both listing and copying workflows, with explicit validation checkpoints (checking if destination exists, prompting user for conflict resolution) and error handling paths. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the execution instructions section is quite long and could potentially be split into a separate reference file. However, for a command skill of this complexity, inline documentation is 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 | |
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.