enable-feedback-hooks
Enable feedback capture hooks for the current project
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/enable-feedback-hooks/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 lacking in clarity and actionability. It uses unexplained technical jargon without describing what the skill actually does, what benefits it provides, or when Claude should select it. Users would have no idea what 'feedback capture hooks' means or when they'd want this capability.
Suggestions
Explain what 'feedback capture hooks' actually do in concrete terms (e.g., 'Collects user feedback through automated prompts, stores responses in a database, and generates feedback reports')
Add a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user wants to gather feedback, collect user opinions, set up feedback forms, or track user responses')
Clarify the scope and context - what kind of project, what type of feedback, and what happens with the captured data
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Enable feedback capture hooks') without explaining what concrete actions this entails or what 'feedback capture hooks' actually do. | 1 / 3 |
Completeness | Only partially addresses 'what' with vague technical language, and completely missing any 'when' guidance or 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | Uses technical jargon ('feedback capture hooks') that users would not naturally say. Missing common terms users might use like 'collect feedback', 'user input', or 'track responses'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'feedback capture hooks' is somewhat specific technical terminology that wouldn't overlap with many other skills, but without clear context it's hard to distinguish from other feedback or hook-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 skill with excellent actionability - the JSON configuration and shell commands are copy-paste ready. The workflow is clear with distinct enable/disable paths. Minor improvements could be made by tightening the explanatory sections and potentially moving detailed execution instructions to a separate file.
Suggestions
Consider moving the detailed 'Execution Instructions' section to a separate IMPLEMENTATION.md file, keeping only a brief summary in the main skill
Consolidate the privacy bullet points - they repeat the 'local/your machine' concept four times
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundant explanations (e.g., privacy section repeats 'local' concept multiple times, feedback types list could be more compact). The execution instructions section is appropriately detailed for a procedural task. | 2 / 3 |
Actionability | Provides fully executable commands, complete JSON configuration to copy-paste, and specific file paths. The enable/disable flows are concrete with exact shell commands and JSON structures. | 3 / 3 |
Workflow Clarity | Clear numbered sequences for both enable and disable modes with explicit steps. The ASCII diagram shows the data flow clearly. Each step has a specific action and expected outcome. | 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 implementation file. The skill references other commands (/sync-feedback) appropriately. | 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.