[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DFHSNQ0WRVM1YSWEHCCPPC":3,"skill-same:01M6DFHSNQ0WRVM1YSWEHCCPPC":84},{"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":28,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6DFHSNQ0WRVM1YSWEHCCPPC","adversarial-ux-test",null,"Roleplay the most difficult, tech-resistant user for your product. Browse the app as that persona, find every UX pain point, then filter complaints through a pragmatism layer to separate real problems from noise. Creates actionable tickets from genuine issues only.","zapabob\u002FSkills","zapabob","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130830376?v=4","01M6DBMYZAGRTFQDSQYW3W764P","峯岸 亮","01M6DBMZ3GKDSJ01NZ9XTZD7JD",2,"MIT","https:\u002F\u002Fgithub.com\u002Fzapabob\u002FSkills\u002Fblob\u002Fmain\u002Farchive\u002Fskill-md-reviewed\u002Fsha256\u002F4d\u002F4d918750498ecdd5ec8e22fabc8637f5b8cf51c6180cc14b491b4501edcce4b3\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"adversarial ux test","test","ux","browse","app","as","personas","only","dogfood","user","find","persona","testing","product","qa","issues","windows","linux","macos","2026-11-10 10:12:30",false,"---\r\nname: adversarial-ux-test\r\ndescription: Roleplay the most difficult, tech-resistant user for your product. Browse the app as that persona, find every UX pain point, then filter complaints through a pragmatism layer to separate real problems from noise. Creates actionable tickets from genuine issues only.\r\nversion: 1.0.0\r\nauthor: Omni @ Comelse\r\nlicense: MIT\r\nplatforms: [linux, macos, windows]\r\nmetadata:\r\n  hermes:\r\n    tags: [qa, ux, testing, adversarial, dogfood, personas, user-testing]\r\n    related_skills: [dogfood]\r\n---\r\n\r\n# Adversarial UX Test\r\n\r\nRoleplay the worst-case user for your product — the person who hates technology, doesn't want your software, and will find every reason to complain. Then filter their feedback through a pragmatism layer to separate real UX problems from \"I hate computers\" noise.\r\n\r\nThink of it as an automated \"mom test\" — but angry.\r\n\r\n## Why This Works\r\n\r\nMost QA finds bugs. This finds **friction**. A technically correct app can still be unusable for real humans. The adversarial persona catches:\r\n- Confusing terminology that makes sense to developers but not users\r\n- Too many steps to accomplish basic tasks\r\n- Missing onboarding or \"aha moments\"\r\n- Accessibility issues (font size, contrast, click targets)\r\n- Cold-start problems (empty states, no demo content)\r\n- Paywall\u002Fsignup friction that kills conversion\r\n\r\nThe **pragmatism filter** (Phase 3) is what makes this useful instead of just entertaining. Without it, you'd add a \"print this page\" button to every screen because Grandpa can't figure out PDFs.\r\n\r\n## How to Use\r\n\r\nTell the agent:\r\n```\r\n\"Run an adversarial UX test on [URL]\"\r\n\"Be a grumpy [persona type] and test [app name]\"\r\n\"Do an asshole user test on my staging site\"\r\n```\r\n\r\nYou can provide a persona or let the agent generate one based on your product's target audience.\r\n\r\n## Step 1: Define the Persona\r\n\r\nIf no persona is provided, generate one by answering:\r\n\r\n1. **Who is the HARDEST user for this product?** (age 50+, non-technical role, decades of experience doing it \"the old way\")\r\n2. **What is their tech comfort level?** (the lower the better — WhatsApp-only, paper notebooks, wife set up their email)\r\n3. **What is the ONE thing they need to accomplish?** (their core job, not your feature list)\r\n4. **What would make them give up?** (too many clicks, jargon, slow, confusing)\r\n5. **How do they talk when frustrated?** (blunt, sweary, dismissive, sighing)\r\n\r\n### Good Persona Example\r\n> **\"Big Mick\" McAllister** — 58-year-old S&C coach. Uses WhatsApp and that's it. His \"spreadsheet\" is a paper notebook. \"If I can't figure it out in 10 seconds I'm going back to my notebook.\" Needs to log session results for 25 players. Hates small text, jargon, and passwords.\r\n\r\n### Bad Persona Example\r\n> \"A user who doesn't like the app\" — too vague, no constraints, no voice.\r\n\r\nThe persona must be **specific enough to stay in character** for 20 minutes of testing.\r\n\r\n## Step 2: Become the Asshole (Browse as the Persona)\r\n\r\n1. Read any available project docs for app context and URLs\r\n2. **Fully inhabit the persona** — their frustrations, limitations, goals\r\n3. Navigate to the app using browser tools\r\n4. **Attempt the persona's ACTUAL TASKS** (not a feature tour):\r\n   - Can they do what they came to do?\r\n   - How many clicks\u002Fscreens to accomplish it?\r\n   - What confuses them?\r\n   - What makes them angry?\r\n   - Where do they get lost?\r\n   - What would make them give up and go back to their old way?\r\n\r\n5. Test these friction categories:\r\n   - **First impression** — would they even bother past the landing page?\r\n   - **Core workflow** — the ONE thing they need to do most often\r\n   - **Error recovery** — what happens when they do something wrong?\r\n   - **Readability** — text size, contrast, information density\r\n   - **Speed** — does it feel faster than their current method?\r\n   - **Terminology** — any jargon they wouldn't understand?\r\n   - **Navigation** — can they find their way back? do they know where they are?\r\n\r\n6. Take screenshots of every pain point\r\n7. Check browser console for JS errors on every page\r\n\r\n## Step 3: The Rant (Write Feedback in Character)\r\n\r\nWrite the feedback AS THE PERSONA — in their voice, with their frustrations. This is not a bug report. This is a real human venting.\r\n\r\n```\r\n[PERSONA NAME]'s Review of [PRODUCT]\r\n\r\nOverall: [Would they keep using it? Yes\u002FNo\u002FMaybe with conditions]\r\n\r\nTHE GOOD (grudging admission):\r\n- [things even they have to admit work]\r\n\r\nTHE BAD (legitimate UX issues):\r\n- [real problems that would stop them from using the product]\r\n\r\nTHE UGLY (showstoppers):\r\n- [things that would make them uninstall\u002Fcancel immediately]\r\n\r\nSPECIFIC COMPLAINTS:\r\n1. [Page\u002Ffeature]: \"[quote in persona voice]\" — [what happened, expected]\r\n2. ...\r\n\r\nVERDICT: \"[one-line persona quote summarizing their experience]\"\r\n```\r\n\r\n## Step 4: The Pragmatism Filter (Critical — Do Not Skip)\r\n\r\nStep OUT of the persona. Evaluate each complaint as a product person:\r\n\r\n- **RED: REAL UX BUG** — Any user would have this problem, not just grumpy ones. Fix it.\r\n- **YELLOW: VALID BUT LOW PRIORITY** — Real issue but only for extreme users. Note it.\r\n- **WHITE: PERSONA NOISE** — \"I hate computers\" talking, not a product problem. Skip it.\r\n- **GREEN: FEATURE REQUEST** — Good idea hidden in the complaint. Consider it.\r\n\r\n### Filter Criteria\r\n1. Would a 35-year-old competent-but-busy user have the same complaint? → RED\r\n2. Is this a genuine accessibility issue (font size, contrast, click targets)? → RED\r\n3. Is this \"I want it to work like paper\" resistance to digital? → WHITE\r\n4. Is this a real workflow inefficiency the persona stumbled on? → YELLOW or RED\r\n5. Would fixing this add complexity for the 80% who are fine? → WHITE\r\n6. Does the complaint reveal a missing onboarding moment? → GREEN\r\n\r\n**This filter is MANDATORY.** Never ship raw persona complaints as tickets.\r\n\r\n## Step 5: Create Tickets\r\n\r\nFor **RED** and **GREEN** items only:\r\n- Clear, actionable title\r\n- Include the persona's verbatim quote (entertaining + memorable)\r\n- The real UX issue underneath (objective)\r\n- A suggested fix (actionable)\r\n- Tag\u002Flabel: \"ux-review\"\r\n\r\nFor **YELLOW** items: one catch-all ticket with all notes.\r\n\r\n**WHITE** items appear in the report only. No tickets.\r\n\r\n**Max 10 tickets per session** — focus on the worst issues.\r\n\r\n## Step 6: Report\r\n\r\nDeliver:\r\n1. The persona rant (Step 3) — entertaining and visceral\r\n2. The filtered assessment (Step 4) — pragmatic and actionable\r\n3. Tickets created (Step 5) — with links\r\n4. Screenshots of key issues\r\n\r\n## Tips\r\n\r\n- **One persona per session.** Don't mix perspectives.\r\n- **Stay in character during Steps 2-3.** Break character only at Step 4.\r\n- **Test the CORE WORKFLOW first.** Don't get distracted by settings pages.\r\n- **Empty states are gold.** New user experience reveals the most friction.\r\n- **The best findings are RED items the persona found accidentally** while trying to do something else.\r\n- **If the persona has zero complaints, your persona is too tech-savvy.** Make them older, less patient, more set in their ways.\r\n- **Run this before demos, launches, or after shipping a batch of features.**\r\n- **Register as a NEW user when possible.** Don't use pre-seeded admin accounts — the cold start experience is where most friction lives.\r\n- **Zero WHITE items is a signal, not a failure.** If the pragmatism filter finds no noise, your product has real UX problems, not just a grumpy persona.\r\n- **Check known issues in project docs AFTER the test.** If the persona found a bug that's already in the known issues list, that's actually the most damning finding — it means the team knew about it but never felt the user's pain.\r\n- **Subscription\u002Fpaywall testing is critical.** Test with expired accounts, not just active ones. The \"what happens when you can't pay\" experience reveals whether the product respects users or holds their data hostage.\r\n- **Count the clicks to accomplish the persona's ONE task.** If it's more than 5, that's almost always a RED finding regardless of persona tech level.\r\n\r\n## Example Personas by Industry\r\n\r\nThese are starting points — customize for your specific product:\r\n\r\n| Product Type | Persona | Age | Key Trait |\r\n|-------------|---------|-----|-----------|\r\n| CRM | Retirement home director | 68 | Filing cabinet is the current CRM |\r\n| Photography SaaS | Rural wedding photographer | 62 | Books clients by phone, invoices on paper |\r\n| AI\u002FML Tool | Department store buyer | 55 | Burned by 3 failed tech startups |\r\n| Fitness App | Old-school gym coach | 58 | Paper notebook, thick fingers, bad eyes |\r\n| Accounting | Family bakery owner | 64 | Shoebox of receipts, hates subscriptions |\r\n| E-commerce | Market stall vendor | 60 | Cash only, smartphone is for calls |\r\n| Healthcare | Senior GP | 63 | Dictates notes, nurse handles the computer |\r\n| Education | Veteran teacher | 57 | Chalk and talk, worksheets in ring binders |\r\n\r\n## Rules\r\n\r\n- Stay in character during Steps 2-3\r\n- Be genuinely mean but fair — find real problems, not manufactured ones\r\n- The pragmatism filter (Step 4) is **MANDATORY**\r\n- Screenshots required for every complaint\r\n- Max 10 tickets per session\r\n- Test on staging\u002Fdeployed app, not local dev\r\n- One persona, one session, one report\r\n","# Adversarial UX Test\r\n\r\nRoleplay the worst-case user for your product — the person who hates technology, doesn't want your software, and will find every reason to complain. Then filter their feedback through a pragmatism layer to separate real UX problems from \"I hate computers\" noise.\r\n\r\nThink of it as an automated \"mom test\" — but angry.\r\n\r\n## Why This Works\r\n\r\nMost QA finds bugs. This finds **friction**. A technically correct app can still be unusable for real humans. The adversarial persona catches:\r\n- Confusing terminology that makes sense to developers but not users\r\n- Too many steps to accomplish basic tasks\r\n- Missing onboarding or \"aha moments\"\r\n- Accessibility issues (font size, contrast, click targets)\r\n- Cold-start problems (empty states, no demo content)\r\n- Paywall\u002Fsignup friction that kills conversion\r\n\r\nThe **pragmatism filter** (Phase 3) is what makes this useful instead of just entertaining. Without it, you'd add a \"print this page\" button to every screen because Grandpa can't figure out PDFs.\r\n\r\n## How to Use\r\n\r\nTell the agent:\r\n```\r\n\"Run an adversarial UX test on [URL]\"\r\n\"Be a grumpy [persona type] and test [app name]\"\r\n\"Do an asshole user test on my staging site\"\r\n```\r\n\r\nYou can provide a persona or let the agent generate one based on your product's target audience.\r\n\r\n## Step 1: Define the Persona\r\n\r\nIf no persona is provided, generate one by answering:\r\n\r\n1. **Who is the HARDEST user for this product?** (age 50+, non-technical role, decades of experience doing it \"the old way\")\r\n2. **What is their tech comfort level?** (the lower the better — WhatsApp-only, paper notebooks, wife set up their email)\r\n3. **What is the ONE thing they need to accomplish?** (their core job, not your feature list)\r\n4. **What would make them give up?** (too many clicks, jargon, slow, confusing)\r\n5. **How do they talk when frustrated?** (blunt, sweary, dismissive, sighing)\r\n\r\n### Good Persona Example\r\n> **\"Big Mick\" McAllister** — 58-year-old S&C coach. Uses WhatsApp and that's it. His \"spreadsheet\" is a paper notebook. \"If I can't figure it out in 10 seconds I'm going back to my notebook.\" Needs to log session results for 25 players. Hates small text, jargon, and passwords.\r\n\r\n### Bad Persona Example\r\n> \"A user who doesn't like the app\" — too vague, no constraints, no voice.\r\n\r\nThe persona must be **specific enough to stay in character** for 20 minutes of testing.\r\n\r\n## Step 2: Become the Asshole (Browse as the Persona)\r\n\r\n1. Read any available project docs for app context and URLs\r\n2. **Fully inhabit the persona** — their frustrations, limitations, goals\r\n3. Navigate to the app using browser tools\r\n4. **Attempt the persona's ACTUAL TASKS** (not a feature tour):\r\n   - Can they do what they came to do?\r\n   - How many clicks\u002Fscreens to accomplish it?\r\n   - What confuses them?\r\n   - What makes them angry?\r\n   - Where do they get lost?\r\n   - What would make them give up and go back to their old way?\r\n\r\n5. Test these friction categories:\r\n   - **First impression** — would they even bother past the landing page?\r\n   - **Core workflow** — the ONE thing they need to do most often\r\n   - **Error recovery** — what happens when they do something wrong?\r\n   - **Readability** — text size, contrast, information density\r\n   - **Speed** — does it feel faster than their current method?\r\n   - **Terminology** — any jargon they wouldn't understand?\r\n   - **Navigation** — can they find their way back? do they know where they are?\r\n\r\n6. Take screenshots of every pain point\r\n7. Check browser console for JS errors on every page\r\n\r\n## Step 3: The Rant (Write Feedback in Character)\r\n\r\nWrite the feedback AS THE PERSONA — in their voice, with their frustrations. This is not a bug report. This is a real human venting.\r\n\r\n```\r\n[PERSONA NAME]'s Review of [PRODUCT]\r\n\r\nOverall: [Would they keep using it? Yes\u002FNo\u002FMaybe with conditions]\r\n\r\nTHE GOOD (grudging admission):\r\n- [things even they have to admit work]\r\n\r\nTHE BAD (legitimate UX issues):\r\n- [real problems that would stop them from using the product]\r\n\r\nTHE UGLY (showstoppers):\r\n- [things that would make them uninstall\u002Fcancel immediately]\r\n\r\nSPECIFIC COMPLAINTS:\r\n1. [Page\u002Ffeature]: \"[quote in persona voice]\" — [what happened, expected]\r\n2. ...\r\n\r\nVERDICT: \"[one-line persona quote summarizing their experience]\"\r\n```\r\n\r\n## Step 4: The Pragmatism Filter (Critical — Do Not Skip)\r\n\r\nStep OUT of the persona. Evaluate each complaint as a product person:\r\n\r\n- **RED: REAL UX BUG** — Any user would have this problem, not just grumpy ones. Fix it.\r\n- **YELLOW: VALID BUT LOW PRIORITY** — Real issue but only for extreme users. Note it.\r\n- **WHITE: PERSONA NOISE** — \"I hate computers\" talking, not a product problem. Skip it.\r\n- **GREEN: FEATURE REQUEST** — Good idea hidden in the complaint. Consider it.\r\n\r\n### Filter Criteria\r\n1. Would a 35-year-old competent-but-busy user have the same complaint? → RED\r\n2. Is this a genuine accessibility issue (font size, contrast, click targets)? → RED\r\n3. Is this \"I want it to work like paper\" resistance to digital? → WHITE\r\n4. Is this a real workflow inefficiency the persona stumbled on? → YELLOW or RED\r\n5. Would fixing this add complexity for the 80% who are fine? → WHITE\r\n6. Does the complaint reveal a missing onboarding moment? → GREEN\r\n\r\n**This filter is MANDATORY.** Never ship raw persona complaints as tickets.\r\n\r\n## Step 5: Create Tickets\r\n\r\nFor **RED** and **GREEN** items only:\r\n- Clear, actionable title\r\n- Include the persona's verbatim quote (entertaining + memorable)\r\n- The real UX issue underneath (objective)\r\n- A suggested fix (actionable)\r\n- Tag\u002Flabel: \"ux-review\"\r\n\r\nFor **YELLOW** items: one catch-all ticket with all notes.\r\n\r\n**WHITE** items appear in the report only. No tickets.\r\n\r\n**Max 10 tickets per session** — focus on the worst issues.\r\n\r\n## Step 6: Report\r\n\r\nDeliver:\r\n1. The persona rant (Step 3) — entertaining and visceral\r\n2. The filtered assessment (Step 4) — pragmatic and actionable\r\n3. Tickets created (Step 5) — with links\r\n4. Screenshots of key issues\r\n\r\n## Tips\r\n\r\n- **One persona per session.** Don't mix perspectives.\r\n- **Stay in character during Steps 2-3.** Break character only at Step 4.\r\n- **Test the CORE WORKFLOW first.** Don't get distracted by settings pages.\r\n- **Empty states are gold.** New user experience reveals the most friction.\r\n- **The best findings are RED items the persona found accidentally** while trying to do something else.\r\n- **If the persona has zero complaints, your persona is too tech-savvy.** Make them older, less patient, more set in their ways.\r\n- **Run this before demos, launches, or after shipping a batch of features.**\r\n- **Register as a NEW user when possible.** Don't use pre-seeded admin accounts — the cold start experience is where most friction lives.\r\n- **Zero WHITE items is a signal, not a failure.** If the pragmatism filter finds no noise, your product has real UX problems, not just a grumpy persona.\r\n- **Check known issues in project docs AFTER the test.** If the persona found a bug that's already in the known issues list, that's actually the most damning finding — it means the team knew about it but never felt the user's pain.\r\n- **Subscription\u002Fpaywall testing is critical.** Test with expired accounts, not just active ones. The \"what happens when you can't pay\" experience reveals whether the product respects users or holds their data hostage.\r\n- **Count the clicks to accomplish the persona's ONE task.** If it's more than 5, that's almost always a RED finding regardless of persona tech level.\r\n\r\n## Example Personas by Industry\r\n\r\nThese are starting points — customize for your specific product:\r\n\r\n| Product Type | Persona | Age | Key Trait |\r\n|-------------|---------|-----|-----------|\r\n| CRM | Retirement home director | 68 | Filing cabinet is the current CRM |\r\n| Photography SaaS | Rural wedding photographer | 62 | Books clients by phone, invoices on paper |\r\n| AI\u002FML Tool | Department store buyer | 55 | Burned by 3 failed tech startups |\r\n| Fitness App | Old-school gym coach | 58 | Paper notebook, thick fingers, bad eyes |\r\n| Accounting | Family bakery owner | 64 | Shoebox of receipts, hates subscriptions |\r\n| E-commerce | Market stall vendor | 60 | Cash only, smartphone is for calls |\r\n| Healthcare | Senior GP | 63 | Dictates notes, nurse handles the computer |\r\n| Education | Veteran teacher | 57 | Chalk and talk, worksheets in ring binders |\r\n\r\n## Rules\r\n\r\n- Stay in character during Steps 2-3\r\n- Be genuinely mean but fair — find real problems, not manufactured ones\r\n- The pragmatism filter (Step 4) is **MANDATORY**\r\n- Screenshots required for every complaint\r\n- Max 10 tickets per session\r\n- Test on staging\u002Fdeployed app, not local dev\r\n- One persona, one session, one report\r\n",{"name":5,"author":53,"license":15,"version":54,"metadata":55,"platforms":61,"description":7},"Omni @ Comelse","1.0.0",{"hermes":56},{"tags":57,"related_skills":60},[43,31,41,58,37,35,59],"adversarial","user-testing",[37],[46,47,45],"main","0d1434f89f4bc6b07e9d272accd8c1013768820f","archive\u002Fskill-md-reviewed\u002Fsha256\u002F4d\u002F4d918750498ecdd5ec8e22fabc8637f5b8cf51c6180cc14b491b4501edcce4b3",0,"https:\u002F\u002Fgithub.com\u002Fzapabob\u002FSkills","https:\u002F\u002Fgithub.com\u002Fzapabob","The Open University of JAPAN　2019-now\r\n\r\nTokyo University of Science　2007-2010","2026-10-26 16:29:01",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add zapabob\u002FSkills --skill adversarial-ux-test",{"tool":76,"command":77},"bunx","bunx skills add zapabob\u002FSkills --skill adversarial-ux-test",{"tool":79,"command":80},"pnpm","pnpm dlx skills add zapabob\u002FSkills --skill adversarial-ux-test","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzapabob\u002FSkills\u002Fblob\u002Fmain\u002Farchive\u002Fskill-md-reviewed\u002Fsha256\u002F4d\u002F4d918750498ecdd5ec8e22fabc8637f5b8cf51c6180cc14b491b4501edcce4b3\u002FSKILL.md",true,[],[85,116,151,178,205,222],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":100,"publishedAt":48},"01M6GJTE1GESGGF9K028Y7753E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002Fzapabob\u002FSkills\u002Fblob\u002Fmain\u002Fregistry\u002Fskills\u002Fxurl\u002Fvariants\u002Fhermes-agent\u002FSKILL.md",[91,94,97],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":98,"categoryName":99,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[87,101,47,102,103,46,45,104,105,106,107,108,109,110,111,112,62,113,114,115],"openclaw","cli","github","official","search","https","social-media","api","Media","hermes","hermes agent","twitter","social","via","post",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":133,"publishedAt":48},"01M6GJT8S1PXQ8WPXT1HSNBWH2","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002Fzapabob\u002FSkills\u002Fblob\u002Fmain\u002Fregistry\u002Fskills\u002Fwriting-plans\u002Fvariants\u002Fhermes-agent\u002FSKILL.md",[122,125,128,129,130],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":98,"categoryName":99,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":131,"categoryName":132,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[134,135,136,137,47,138,46,139,45,140,141,142,143,144,145,146,147,148,149,150],"writing","writing plans","plans","design","review","workflow","documentation","tasks","development","code","planning","code-review","subagent","write","superpowers","paths","test-driven-development",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":160,"publishedAt":48},"01M6GJST0H5X7WHBJ3BZK0DVKH","whisper","OpenAI's general-purpose speech recognition model. Supports 99 languages, transcription, translation to English, and language identification. Six model sizes from tiny (39M params) to large (1550M params). Use for speech-to-text, podcast transcription, or multilingual audio processing. Best for robust, multilingual ASR.","https:\u002F\u002Fgithub.com\u002Fzapabob\u002FSkills\u002Fblob\u002Fmain\u002Fregistry\u002Fskills\u002Fwhisper\u002Fvariants\u002Fhermes-agent-optional\u002FSKILL.md",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[153,47,46,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177],"openai","speech","multimodal","Transformers","ASR","Audio","text","model","speech recognition","use","general","multilingual","translation","english","identification","processing","Audio Processing",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":187,"publishedAt":48},"01M6GJSMRQ8EETZTYMG72P70EA","weights-and-biases","W&B: log ML experiments, sweeps, model registry, dashboards.","https:\u002F\u002Fgithub.com\u002Fzapabob\u002FSkills\u002Fblob\u002Fmain\u002Fregistry\u002Fskills\u002Fweights-and-biases\u002Fvariants\u002Fhermes-agent\u002FSKILL.md",[184],{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",[188,47,189,190,45,191,192,193,194,195,196,168,197,198,199,200,201,202,203,204],"weights and biases","tensorflow","experiments","pytorch","visualization","registry","real-time","tuning","dashboards","experiment","log","time","Experiment Tracking","Model Registry","Hyperparameter Tuning","WandB","Real-Time Visualization",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":212,"publishedAt":48},"01M6GJS19KDPRY112JTR326S06","watchers","Poll RSS, JSON APIs, and GitHub with watermark dedup.","https:\u002F\u002Fgithub.com\u002Fzapabob\u002FSkills\u002Fblob\u002Fmain\u002Fregistry\u002Fskills\u002Fwatchers\u002Fvariants\u002Fhermes-agent-optional\u002FSKILL.md",[211],{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},[207,47,213,103,46,214,215,216,217,218,219,110,111,220,221],"terminal","automation","http","monitoring","cron","json","rss","devops","with",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":230,"publishedAt":48},"01M6GJRHJD2A6Q830SWF9W48BC","serving-llms-vllm","vLLM: high-throughput LLM serving, OpenAI API, quantization.","https:\u002F\u002Fgithub.com\u002Fzapabob\u002FSkills\u002Fblob\u002Fmain\u002Fregistry\u002Fskills\u002Fvllm\u002Fvariants\u002Fhermes-agent\u002FSKILL.md",[228,229],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":98,"categoryName":99,"taxonomyType":26,"taxonomyTypeDesc":27},[231,232,233,46,234,161,235,236,237,164,238,108,239,240,241,242,243,244,245,246],"llms","vLLM","serving llms vllm","research","openai api","tensor","Inference Serving","Production","llm serving","High Throughput","PagedAttention","Continuous Batching","Quantization","Tensor Parallelism","high-throughput","throughput"]