maceybaker/botfooding
When the agent, as the user of the tool, is asked to provide feedback.
Overall
score
53%
Does it follow best practices?
Validation for skill structure
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. It fails to specify what actions the skill performs, uses no natural trigger terms users would employ, and lacks explicit guidance on when Claude should select it. The description reads more like a partial condition than a functional skill description.
Suggestions
Add concrete actions the skill performs (e.g., 'Collects bug reports, feature requests, and usability feedback. Formats and submits feedback to the development team.')
Include natural trigger terms users would say: 'Use when the user mentions bug, issue, feature request, suggestion, complaint, or wants to report a problem with the tool.'
Rewrite in third person voice describing capabilities rather than conditions (e.g., 'Handles user feedback submission for the tool' instead of 'When the agent...is asked').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('provide feedback about the tool itself') without listing any concrete actions. It doesn't specify what kind of feedback, how it's collected, or what happens with it. | 1 / 3 |
Completeness | The description only vaguely addresses 'when' (when asked to provide feedback) but fails to explain 'what' the skill actually does. There's no explicit 'Use when...' clause or trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. 'Feedback about the tool itself' is abstract and technical. Users would more likely say 'bug report', 'feature request', 'suggestion', or 'complaint'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'feedback about the tool itself' provides some specificity about the target (the tool vs other things), but 'feedback' is generic enough to potentially conflict with other feedback-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is concise and well-scoped for its purpose of collecting UX feedback during tool usage. However, it would benefit from concrete examples of what good feedback entries look like and clearer workflow triggers for when to record observations versus when to summarize.
Suggestions
Add 1-2 example entries showing what a good 'unclear UX' or 'unexpected outcome' note looks like in botfooding_ux_notes.md
Clarify the workflow timing: specify whether to record notes in real-time or batch them, and define explicit triggers for the summarization step
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient at 15 lines. It assumes Claude's competence and doesn't explain obvious concepts like what UX feedback is or how to write markdown files. | 3 / 3 |
Actionability | Provides clear categories of what to track (unclear UX, unexpected outcomes, pleasant interactions) but lacks concrete examples of what good feedback entries look like or a template structure for the notes file. | 2 / 3 |
Workflow Clarity | The workflow is implicit (use tool → record notes → summarize at end) but lacks explicit sequencing. No guidance on when/how often to write notes during usage, or what constitutes a 'blocking point' that triggers summarization. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is appropriately self-contained with clear sections. No external references are needed for this scope. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
63%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 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed | |
Install with Tessl CLI
npx tessl i maceybaker/botfooding@0.1.1Reviewed
Table of Contents