sync-feedback
Review and sync captured feedback to Product Forge
67
55%
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/sync-feedback/SKILL.mdQuality
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.
The description is too brief and lacks explicit trigger guidance. While it mentions a specific product (Product Forge) which aids distinctiveness, it fails to explain what reviewing and syncing feedback actually involves or when Claude should use this skill over others.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user wants to upload, review, or synchronize user feedback with Product Forge'
Expand the capabilities with specific actions like 'categorize feedback', 'push updates', 'check sync status', or whatever concrete operations this skill performs
Include natural trigger terms users might say such as 'upload feedback', 'send to Product Forge', 'feedback sync', or 'product feedback'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('captured feedback', 'Product Forge') and two actions ('review', 'sync'), but lacks detail on what reviewing or syncing entails or what types of feedback are handled. | 2 / 3 |
Completeness | Describes what 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 'feedback' and 'Product Forge' as relevant terms, but 'sync' and 'review' are generic. Missing natural variations users might say like 'upload feedback', 'send to Product Forge', or 'feedback management'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Product Forge' is a specific product name which helps distinctiveness, but 'review feedback' and 'sync' are generic enough to potentially overlap with other feedback or sync-related 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 command skill with excellent actionability and clear workflow documentation. The execution instructions are thorough with concrete examples and expected outputs. However, the skill is lengthy and could benefit from splitting detailed execution instructions into a separate reference file, and some content is repeated between the workflow diagram and execution sections.
Suggestions
Consider moving detailed 'Execution Instructions' to a separate EXECUTION.md file and keeping only the quick reference in the main skill
Remove the duplicate workflow representation - keep either the ASCII diagram or the numbered list in execution instructions, not both
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy (workflow shown twice - once as diagram, once in execution instructions) and could be tightened. The detailed execution instructions are necessary but some sections repeat information. | 2 / 3 |
Actionability | Provides fully executable commands, specific file paths, concrete output examples, and exact scripts to run. The execution instructions are copy-paste ready with clear bash commands and expected outputs. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow with explicit sequence (enable → work → process → review → export). Status transitions are documented, and each mode has step-by-step instructions with validation points (e.g., 'Run /sync-feedback --review to review extracted feedback'). | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (monolithic) with detailed execution instructions that could potentially be split into separate reference files. All content is inline rather than using progressive disclosure to external files. | 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.