dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
Overall
score
99%
Does it follow best practices?
Validation for skill structure
Discovery
100%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 is an excellent skill description that hits all the marks. It provides specific concrete actions, includes a comprehensive list of natural trigger terms users would actually say, explicitly addresses both what the skill does and when to use it, and carves out a distinct niche in web application quality assurance with detailed evidence production.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'explore and test a web application', 'find bugs, UX issues, and other problems', 'produces a structured report with full reproduction evidence', 'step-by-step screenshots, repro videos, and detailed repro steps'. | 3 / 3 |
Completeness | Clearly answers both what (systematically explore and test web apps, find bugs/UX issues, produce structured reports with evidence) AND when (explicit 'Use when...' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'dogfood', 'QA', 'exploratory test', 'find issues', 'bug hunt', 'test this app/site/platform', 'review the quality'. These are exactly the phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on web application QA/testing with distinct triggers like 'dogfood', 'bug hunt', 'QA'. The combination of exploratory testing + structured evidence reports creates a unique profile unlikely to conflict with general testing or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates best practices across all dimensions. It provides a complete, actionable workflow for exploratory testing with clear commands, appropriate evidence-gathering strategies for different issue types, and well-organized progressive disclosure. The guidance section reinforces key principles without being redundant.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence throughout. No unnecessary explanations of basic concepts, and every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable bash commands throughout, with specific examples for every step. Commands are copy-paste ready with clear placeholders for variables like {SESSION}, {OUTPUT_DIR}, etc. | 3 / 3 |
Workflow Clarity | Clear 6-step workflow with explicit validation checkpoints. The documentation section distinguishes between interactive vs static issues with different evidence requirements. Includes explicit guidance on pacing, incremental writing, and session management. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear references to external files (issue-taxonomy.md, report template). References are one level deep and clearly signaled in tables. Core workflow is inline while detailed taxonomies and templates are appropriately externalized. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
91%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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.