[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NDNE57KW25EDKF8VGV3R9":3,"skill-same:01M71NDNE57KW25EDKF8VGV3R9":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M71NDNE57KW25EDKF8VGV3R9","dogfood",null,"Systematic exploratory QA testing of web applications — find bugs, capture evidence, and generate structured reports","q2805187159\u002FAnvil","q2805187159","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F105276843?v=4","01M71KF4TN999VNJX9FY9QT06A","铁甲勇士宋小宝","01M71KF4V97XXQ7AGES97R4Q9F",3,"MIT","https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fdogfood\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"evidence","bugs","applications","testing","find bugs","qa testing","qa","reports","browser","web","generate","find","systematic","capture","structured","2026-11-10 10:56:23",false,"---\nname: dogfood\ndescription: Systematic exploratory QA testing of web applications — find bugs, capture evidence, and generate structured reports\nversion: 1.0.0\nmetadata:\n  hermes:\n    tags: [qa, testing, browser, web, dogfood]\n    related_skills: []\n---\n\n# Dogfood: Systematic Web Application QA Testing\n\n## Overview\n\nThis skill guides you through systematic exploratory QA testing of web applications using the browser toolset. You will navigate the application, interact with elements, capture evidence of issues, and produce a structured bug report.\n\n## Prerequisites\n\n- Browser toolset must be available (`browser_navigate`, `browser_snapshot`, `browser_click`, `browser_type`, `browser_vision`, `browser_console`, `browser_scroll`, `browser_back`, `browser_press`)\n- A target URL and testing scope from the user\n\n## Inputs\n\nThe user provides:\n1. **Target URL** — the entry point for testing\n2. **Scope** — what areas\u002Ffeatures to focus on (or \"full site\" for comprehensive testing)\n3. **Output directory** (optional) — where to save screenshots and the report (default: `.\u002Fdogfood-output`)\n\n## Workflow\n\nFollow this 5-phase systematic workflow:\n\n### Phase 1: Plan\n\n1. Create the output directory structure:\n   ```\n   {output_dir}\u002F\n   ├── screenshots\u002F       # Evidence screenshots\n   └── report.md          # Final report (generated in Phase 5)\n   ```\n2. Identify the testing scope based on user input.\n3. Build a rough sitemap by planning which pages and features to test:\n   - Landing\u002Fhome page\n   - Navigation links (header, footer, sidebar)\n   - Key user flows (sign up, login, search, checkout, etc.)\n   - Forms and interactive elements\n   - Edge cases (empty states, error pages, 404s)\n\n### Phase 2: Explore\n\nFor each page or feature in your plan:\n\n1. **Navigate** to the page:\n   ```\n   browser_navigate(url=\"https:\u002F\u002Fexample.com\u002Fpage\")\n   ```\n\n2. **Take a snapshot** to understand the DOM structure:\n   ```\n   browser_snapshot()\n   ```\n\n3. **Check the console** for JavaScript errors:\n   ```\n   browser_console(clear=true)\n   ```\n   Do this after every navigation and after every significant interaction. Silent JS errors are high-value findings.\n\n4. **Take an annotated screenshot** to visually assess the page and identify interactive elements:\n   ```\n   browser_vision(question=\"Describe the page layout, identify any visual issues, broken elements, or accessibility concerns\", annotate=true)\n   ```\n   The `annotate=true` flag overlays numbered `[N]` labels on interactive elements. Each `[N]` maps to ref `@eN` for subsequent browser commands.\n\n5. **Test interactive elements** systematically:\n   - Click buttons and links: `browser_click(ref=\"@eN\")`\n   - Fill forms: `browser_type(ref=\"@eN\", text=\"test input\")`\n   - Test keyboard navigation: `browser_press(key=\"Tab\")`, `browser_press(key=\"Enter\")`\n   - Scroll through content: `browser_scroll(direction=\"down\")`\n   - Test form validation with invalid inputs\n   - Test empty submissions\n\n6. **After each interaction**, check for:\n   - Console errors: `browser_console()`\n   - Visual changes: `browser_vision(question=\"What changed after the interaction?\")`\n   - Expected vs actual behavior\n\n### Phase 3: Collect Evidence\n\nFor every issue found:\n\n1. **Take a screenshot** showing the issue:\n   ```\n   browser_vision(question=\"Capture and describe the issue visible on this page\", annotate=false)\n   ```\n   Save the `screenshot_path` from the response — you will reference it in the report.\n\n2. **Record the details**:\n   - URL where the issue occurs\n   - Steps to reproduce\n   - Expected behavior\n   - Actual behavior\n   - Console errors (if any)\n   - Screenshot path\n\n3. **Classify the issue** using the issue taxonomy (see `references\u002Fissue-taxonomy.md`):\n   - Severity: Critical \u002F High \u002F Medium \u002F Low\n   - Category: Functional \u002F Visual \u002F Accessibility \u002F Console \u002F UX \u002F Content\n\n### Phase 4: Categorize\n\n1. Review all collected issues.\n2. De-duplicate — merge issues that are the same bug manifesting in different places.\n3. Assign final severity and category to each issue.\n4. Sort by severity (Critical first, then High, Medium, Low).\n5. Count issues by severity and category for the executive summary.\n\n### Phase 5: Report\n\nGenerate the final report using the template at `templates\u002Fdogfood-report-template.md`.\n\nThe report must include:\n1. **Executive summary** with total issue count, breakdown by severity, and testing scope\n2. **Per-issue sections** with:\n   - Issue number and title\n   - Severity and category badges\n   - URL where observed\n   - Description of the issue\n   - Steps to reproduce\n   - Expected vs actual behavior\n   - Screenshot references (use `MEDIA:\u003Cscreenshot_path>` for inline images)\n   - Console errors if relevant\n3. **Summary table** of all issues\n4. **Testing notes** — what was tested, what was not, any blockers\n\nSave the report to `{output_dir}\u002Freport.md`.\n\n## Tools Reference\n\n| Tool | Purpose |\n|------|---------|\n| `browser_navigate` | Go to a URL |\n| `browser_snapshot` | Get DOM text snapshot (accessibility tree) |\n| `browser_click` | Click an element by ref (`@eN`) or text |\n| `browser_type` | Type into an input field |\n| `browser_scroll` | Scroll up\u002Fdown on the page |\n| `browser_back` | Go back in browser history |\n| `browser_press` | Press a keyboard key |\n| `browser_vision` | Screenshot + AI analysis; use `annotate=true` for element labels |\n| `browser_console` | Get JS console output and errors |\n\n## Tips\n\n- **Always check `browser_console()` after navigating and after significant interactions.** Silent JS errors are among the most valuable findings.\n- **Use `annotate=true` with `browser_vision`** when you need to reason about interactive element positions or when the snapshot refs are unclear.\n- **Test with both valid and invalid inputs** — form validation bugs are common.\n- **Scroll through long pages** — content below the fold may have rendering issues.\n- **Test navigation flows** — click through multi-step processes end-to-end.\n- **Check responsive behavior** by noting any layout issues visible in screenshots.\n- **Don't forget edge cases**: empty states, very long text, special characters, rapid clicking.\n- When reporting screenshots to the user, include `MEDIA:\u003Cscreenshot_path>` so they can see the evidence inline.\n","# Dogfood: Systematic Web Application QA Testing\n\n## Overview\n\nThis skill guides you through systematic exploratory QA testing of web applications using the browser toolset. You will navigate the application, interact with elements, capture evidence of issues, and produce a structured bug report.\n\n## Prerequisites\n\n- Browser toolset must be available (`browser_navigate`, `browser_snapshot`, `browser_click`, `browser_type`, `browser_vision`, `browser_console`, `browser_scroll`, `browser_back`, `browser_press`)\n- A target URL and testing scope from the user\n\n## Inputs\n\nThe user provides:\n1. **Target URL** — the entry point for testing\n2. **Scope** — what areas\u002Ffeatures to focus on (or \"full site\" for comprehensive testing)\n3. **Output directory** (optional) — where to save screenshots and the report (default: `.\u002Fdogfood-output`)\n\n## Workflow\n\nFollow this 5-phase systematic workflow:\n\n### Phase 1: Plan\n\n1. Create the output directory structure:\n   ```\n   {output_dir}\u002F\n   ├── screenshots\u002F       # Evidence screenshots\n   └── report.md          # Final report (generated in Phase 5)\n   ```\n2. Identify the testing scope based on user input.\n3. Build a rough sitemap by planning which pages and features to test:\n   - Landing\u002Fhome page\n   - Navigation links (header, footer, sidebar)\n   - Key user flows (sign up, login, search, checkout, etc.)\n   - Forms and interactive elements\n   - Edge cases (empty states, error pages, 404s)\n\n### Phase 2: Explore\n\nFor each page or feature in your plan:\n\n1. **Navigate** to the page:\n   ```\n   browser_navigate(url=\"https:\u002F\u002Fexample.com\u002Fpage\")\n   ```\n\n2. **Take a snapshot** to understand the DOM structure:\n   ```\n   browser_snapshot()\n   ```\n\n3. **Check the console** for JavaScript errors:\n   ```\n   browser_console(clear=true)\n   ```\n   Do this after every navigation and after every significant interaction. Silent JS errors are high-value findings.\n\n4. **Take an annotated screenshot** to visually assess the page and identify interactive elements:\n   ```\n   browser_vision(question=\"Describe the page layout, identify any visual issues, broken elements, or accessibility concerns\", annotate=true)\n   ```\n   The `annotate=true` flag overlays numbered `[N]` labels on interactive elements. Each `[N]` maps to ref `@eN` for subsequent browser commands.\n\n5. **Test interactive elements** systematically:\n   - Click buttons and links: `browser_click(ref=\"@eN\")`\n   - Fill forms: `browser_type(ref=\"@eN\", text=\"test input\")`\n   - Test keyboard navigation: `browser_press(key=\"Tab\")`, `browser_press(key=\"Enter\")`\n   - Scroll through content: `browser_scroll(direction=\"down\")`\n   - Test form validation with invalid inputs\n   - Test empty submissions\n\n6. **After each interaction**, check for:\n   - Console errors: `browser_console()`\n   - Visual changes: `browser_vision(question=\"What changed after the interaction?\")`\n   - Expected vs actual behavior\n\n### Phase 3: Collect Evidence\n\nFor every issue found:\n\n1. **Take a screenshot** showing the issue:\n   ```\n   browser_vision(question=\"Capture and describe the issue visible on this page\", annotate=false)\n   ```\n   Save the `screenshot_path` from the response — you will reference it in the report.\n\n2. **Record the details**:\n   - URL where the issue occurs\n   - Steps to reproduce\n   - Expected behavior\n   - Actual behavior\n   - Console errors (if any)\n   - Screenshot path\n\n3. **Classify the issue** using the issue taxonomy (see `references\u002Fissue-taxonomy.md`):\n   - Severity: Critical \u002F High \u002F Medium \u002F Low\n   - Category: Functional \u002F Visual \u002F Accessibility \u002F Console \u002F UX \u002F Content\n\n### Phase 4: Categorize\n\n1. Review all collected issues.\n2. De-duplicate — merge issues that are the same bug manifesting in different places.\n3. Assign final severity and category to each issue.\n4. Sort by severity (Critical first, then High, Medium, Low).\n5. Count issues by severity and category for the executive summary.\n\n### Phase 5: Report\n\nGenerate the final report using the template at `templates\u002Fdogfood-report-template.md`.\n\nThe report must include:\n1. **Executive summary** with total issue count, breakdown by severity, and testing scope\n2. **Per-issue sections** with:\n   - Issue number and title\n   - Severity and category badges\n   - URL where observed\n   - Description of the issue\n   - Steps to reproduce\n   - Expected vs actual behavior\n   - Screenshot references (use `MEDIA:\u003Cscreenshot_path>` for inline images)\n   - Console errors if relevant\n3. **Summary table** of all issues\n4. **Testing notes** — what was tested, what was not, any blockers\n\nSave the report to `{output_dir}\u002Freport.md`.\n\n## Tools Reference\n\n| Tool | Purpose |\n|------|---------|\n| `browser_navigate` | Go to a URL |\n| `browser_snapshot` | Get DOM text snapshot (accessibility tree) |\n| `browser_click` | Click an element by ref (`@eN`) or text |\n| `browser_type` | Type into an input field |\n| `browser_scroll` | Scroll up\u002Fdown on the page |\n| `browser_back` | Go back in browser history |\n| `browser_press` | Press a keyboard key |\n| `browser_vision` | Screenshot + AI analysis; use `annotate=true` for element labels |\n| `browser_console` | Get JS console output and errors |\n\n## Tips\n\n- **Always check `browser_console()` after navigating and after significant interactions.** Silent JS errors are among the most valuable findings.\n- **Use `annotate=true` with `browser_vision`** when you need to reason about interactive element positions or when the snapshot refs are unclear.\n- **Test with both valid and invalid inputs** — form validation bugs are common.\n- **Scroll through long pages** — content below the fold may have rendering issues.\n- **Test navigation flows** — click through multi-step processes end-to-end.\n- **Check responsive behavior** by noting any layout issues visible in screenshots.\n- **Don't forget edge cases**: empty states, very long text, special characters, rapid clicking.\n- When reporting screenshots to the user, include `MEDIA:\u003Cscreenshot_path>` so they can see the evidence inline.\n",{"name":5,"version":44,"metadata":45,"description":7},"1.0.0",{"hermes":46},{"tags":47,"related_skills":48},[30,27,32,33,5],[],"main","6ffadc67c9777282fa1f9330ec12ac8778064409","skills\u002Fdogfood",0,"https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil","https:\u002F\u002Fgithub.com\u002Fq2805187159","Independent Researcher\r\n\r\nEmail: q2805187159@gmail.com\r\n\r\nGithub: q2805187159\r\n\r\nResearch Interests:\r\n- LLM Agents\r\n- Tool Routing\r\n- RAG","2026-06-24 18:31:41",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add q2805187159\u002FAnvil --skill dogfood",{"tool":63,"command":64},"bunx","bunx skills add q2805187159\u002FAnvil --skill dogfood",{"tool":66,"command":67},"pnpm","pnpm dlx skills add q2805187159\u002FAnvil --skill dogfood","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fdogfood\u002FSKILL.md",true,[71,77],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fissue-taxonomy.md","REFERENCE","参考文档",3682,"https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fdogfood\u002Freferences\u002Fissue-taxonomy.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"templates\u002Fdogfood-report-template.md",1528,"https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fdogfood\u002Ftemplates\u002Fdogfood-report-template.md",[82,108,141,148,172,195],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":94,"publishedAt":39},"01M71NPWVVMB1AZ8XGKNJFT0YP","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[90,91],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[95,27,96,97,26,98,99,100,101,102,32,103,104,33,105,106,107],"webapp","webapp testing","for","local","frontend","debugging","toolkit","logs","with","playwright","behavior","ui","screenshots",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":122,"publishedAt":39},"01M71NPTQ96H4XSZVZT422BNRB","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[114,117],{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[123,124,33,125,126,97,127,128,129,130,131,132,133,134,135,136,137,138,139,140],"guidelines","design","web design guidelines","web design","vercel","interface","web interface guidelines","use","when","best practices","file","code","review","check","compliance","audit","ux","accessibility",{"skillNo":142,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":147,"publishedAt":39},"01M71NPS2D31Y2BGFYA9DB7CE4","https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines copy\u002FSKILL.md",[145,146],{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[123,124,33,125,126,97,127,128,129,130,131,132,133,134,135,136,137,138,139,140],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":160,"publishedAt":39},"01M71NPQ9DRT54QSQJ0BHBM3VG","video-generation","Use this skill when the user requests to generate, create, or imagine videos. Supports structured prompts and reference image for guided generation.","https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-generation\u002FSKILL.md",[154,157],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":158,"categoryName":159,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[161,162,163,97,130,131,164,165,166,167,34,168,169,170,171,38],"Video","video generation","generation","image","create","imagine","requests","videos","reference","prompts","user",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":179,"publishedAt":39},"01M71NPN57CT154SWXAS52475X","youtube-downloader","Download YouTube videos with customizable quality and format options. Use this skill when the user asks to download, save, or grab YouTube videos. Supports various quality settings (best, 1080p, 720p, 480p, 360p), multiple formats (mp4, webm, mkv), and audio-only downloads as MP3.","https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-downloader\u002FSKILL.md",[178],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},[180,181,182,183,184,185,186,130,131,187,103,188,189,190,191,192,168,193,171,194],"youtube","youtube downloader","mp4","as","downloads","Audio","only","mp3","options","quality","format","settings","grab","formats","download",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":39},"01M71NPKD95YB8N3J6J78QGFFW","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fq2805187159\u002FAnvil\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[202,203,204,24,205,206,207,130,208,131,209,210,211,212,213,214],"verification","verification before completion","running","complete","prs","claim","assertions","committing","output","claims","work","about","commands"]