[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7857B33M796MWS1FH4T3VSW":3,"skill-same:01M7857B33M796MWS1FH4T3VSW":69},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7857B33M796MWS1FH4T3VSW","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.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Foptional-skills\u002Fadversarial-ux-test\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: adversarial-ux-test\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.\"\nversion: 1.0.0\nauthor: Omni @ Comelse\nlicense: MIT\nplatforms: [linux, macos, windows]\ncategory: dogfood\ntags: [qa, ux, testing, adversarial, dogfood, personas, user-testing]\ncompatible: [claude-code, openai-agents, hermes-agent, autogen, langchain, any-llm]\nsource: optional\n---\n\n# Adversarial UX Test\n\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.\n\nThink of it as an automated \"mom test\" — but angry.\n\n## Why This Works\n\nMost QA finds bugs. This finds **friction**. A technically correct app can still be unusable for real humans. The adversarial persona catches:\n- Confusing terminology that makes sense to developers but not users\n- Too many steps to accomplish basic tasks\n- Missing onboarding or \"aha moments\"\n- Accessibility issues (font size, contrast, click targets)\n- Cold-start problems (empty states, no demo content)\n- Paywall\u002Fsignup friction that kills conversion\n\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.\n\n## How to Use\n\nTell the agent:\n```\n\"Run an adversarial UX test on [URL]\"\n\"Be a grumpy [persona type] and test [app name]\"\n\"Do an asshole user test on my staging site\"\n```\n\nYou can provide a persona or let the agent generate one based on your product's target audience.\n\n## Step 1: Define the Persona\n\nIf no persona is provided, generate one by answering:\n\n1. **Who is the HARDEST user for this product?** (age 50+, non-technical role, decades of experience doing it \"the old way\")\n2. **What is their tech comfort level?** (the lower the better — WhatsApp-only, paper notebooks, wife set up their email)\n3. **What is the ONE thing they need to accomplish?** (their core job, not your feature list)\n4. **What would make them give up?** (too many clicks, jargon, slow, confusing)\n5. **How do they talk when frustrated?** (blunt, sweary, dismissive, sighing)\n\n### Good Persona Example\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.\n\n### Bad Persona Example\n> \"A user who doesn't like the app\" — too vague, no constraints, no voice.\n\nThe persona must be **specific enough to stay in character** for 20 minutes of testing.\n\n## Step 2: Become the Asshole (Browse as the Persona)\n\n1. Read any available project docs for app context and URLs\n2. **Fully inhabit the persona** — their frustrations, limitations, goals\n3. Navigate to the app using browser tools\n4. **Attempt the persona's ACTUAL TASKS** (not a feature tour):\n   - Can they do what they came to do?\n   - How many clicks\u002Fscreens to accomplish it?\n   - What confuses them?\n   - What makes them angry?\n   - Where do they get lost?\n   - What would make them give up and go back to their old way?\n\n5. Test these friction categories:\n   - **First impression** — would they even bother past the landing page?\n   - **Core workflow** — the ONE thing they need to do most often\n   - **Error recovery** — what happens when they do something wrong?\n   - **Readability** — text size, contrast, information density\n   - **Speed** — does it feel faster than their current method?\n   - **Terminology** — any jargon they wouldn't understand?\n   - **Navigation** — can they find their way back? do they know where they are?\n\n6. Take screenshots of every pain point\n7. Check browser console for JS errors on every page\n\n## Step 3: The Rant (Write Feedback in Character)\n\nWrite the feedback AS THE PERSONA — in their voice, with their frustrations. This is not a bug report. This is a real human venting.\n\n```\n[PERSONA NAME]'s Review of [PRODUCT]\n\nOverall: [Would they keep using it? Yes\u002FNo\u002FMaybe with conditions]\n\nTHE GOOD (grudging admission):\n- [things even they have to admit work]\n\nTHE BAD (legitimate UX issues):\n- [real problems that would stop them from using the product]\n\nTHE UGLY (showstoppers):\n- [things that would make them uninstall\u002Fcancel immediately]\n\nSPECIFIC COMPLAINTS:\n1. [Page\u002Ffeature]: \"[quote in persona voice]\" — [what happened, expected]\n2. ...\n\nVERDICT: \"[one-line persona quote summarizing their experience]\"\n```\n\n## Step 4: The Pragmatism Filter (Critical — Do Not Skip)\n\nStep OUT of the persona. Evaluate each complaint as a product person:\n\n- **RED: REAL UX BUG** — Any user would have this problem, not just grumpy ones. Fix it.\n- **YELLOW: VALID BUT LOW PRIORITY** — Real issue but only for extreme users. Note it.\n- **WHITE: PERSONA NOISE** — \"I hate computers\" talking, not a product problem. Skip it.\n- **GREEN: FEATURE REQUEST** — Good idea hidden in the complaint. Consider it.\n\n### Filter Criteria\n1. Would a 35-year-old competent-but-busy user have the same complaint? → RED\n2. Is this a genuine accessibility issue (font size, contrast, click targets)? → RED\n3. Is this \"I want it to work like paper\" resistance to digital? → WHITE\n4. Is this a real workflow inefficiency the persona stumbled on? → YELLOW or RED\n5. Would fixing this add complexity for the 80% who are fine? → WHITE\n6. Does the complaint reveal a missing onboarding moment? → GREEN\n\n**This filter is MANDATORY.** Never ship raw persona complaints as tickets.\n\n## Step 5: Create Tickets\n\nFor **RED** and **GREEN** items only:\n- Clear, actionable title\n- Include the persona's verbatim quote (entertaining + memorable)\n- The real UX issue underneath (objective)\n- A suggested fix (actionable)\n- Tag\u002Flabel: \"ux-review\"\n\nFor **YELLOW** items: one catch-all ticket with all notes.\n\n**WHITE** items appear in the report only. No tickets.\n\n**Max 10 tickets per session** — focus on the worst issues.\n\n## Step 6: Report\n\nDeliver:\n1. The persona rant (Step 3) — entertaining and visceral\n2. The filtered assessment (Step 4) — pragmatic and actionable\n3. Tickets created (Step 5) — with links\n4. Screenshots of key issues\n\n## Tips\n\n- **One persona per session.** Don't mix perspectives.\n- **Stay in character during Steps 2-3.** Break character only at Step 4.\n- **Test the CORE WORKFLOW first.** Don't get distracted by settings pages.\n- **Empty states are gold.** New user experience reveals the most friction.\n- **The best findings are RED items the persona found accidentally** while trying to do something else.\n- **If the persona has zero complaints, your persona is too tech-savvy.** Make them older, less patient, more set in their ways.\n- **Run this before demos, launches, or after shipping a batch of features.**\n- **Register as a NEW user when possible.** Don't use pre-seeded admin accounts — the cold start experience is where most friction lives.\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.\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.\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.\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.\n\n## Example Personas by Industry\n\nThese are starting points — customize for your specific product:\n\n| Product Type | Persona | Age | Key Trait |\n|-------------|---------|-----|-----------|\n| CRM | Retirement home director | 68 | Filing cabinet is the current CRM |\n| Photography SaaS | Rural wedding photographer | 62 | Books clients by phone, invoices on paper |\n| AI\u002FML Tool | Department store buyer | 55 | Burned by 3 failed tech startups |\n| Fitness App | Old-school gym coach | 58 | Paper notebook, thick fingers, bad eyes |\n| Accounting | Family bakery owner | 64 | Shoebox of receipts, hates subscriptions |\n| E-commerce | Market stall vendor | 60 | Cash only, smartphone is for calls |\n| Healthcare | Senior GP | 63 | Dictates notes, nurse handles the computer |\n| Education | Veteran teacher | 57 | Chalk and talk, worksheets in ring binders |\n\n## Rules\n\n- Stay in character during Steps 2-3\n- Be genuinely mean but fair — find real problems, not manufactured ones\n- The pragmatism filter (Step 4) is **MANDATORY**\n- Screenshots required for every complaint\n- Max 10 tickets per session\n- Test on staging\u002Fdeployed app, not local dev\n- One persona, one session, one report\n","# Adversarial UX Test\n\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.\n\nThink of it as an automated \"mom test\" — but angry.\n\n## Why This Works\n\nMost QA finds bugs. This finds **friction**. A technically correct app can still be unusable for real humans. The adversarial persona catches:\n- Confusing terminology that makes sense to developers but not users\n- Too many steps to accomplish basic tasks\n- Missing onboarding or \"aha moments\"\n- Accessibility issues (font size, contrast, click targets)\n- Cold-start problems (empty states, no demo content)\n- Paywall\u002Fsignup friction that kills conversion\n\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.\n\n## How to Use\n\nTell the agent:\n```\n\"Run an adversarial UX test on [URL]\"\n\"Be a grumpy [persona type] and test [app name]\"\n\"Do an asshole user test on my staging site\"\n```\n\nYou can provide a persona or let the agent generate one based on your product's target audience.\n\n## Step 1: Define the Persona\n\nIf no persona is provided, generate one by answering:\n\n1. **Who is the HARDEST user for this product?** (age 50+, non-technical role, decades of experience doing it \"the old way\")\n2. **What is their tech comfort level?** (the lower the better — WhatsApp-only, paper notebooks, wife set up their email)\n3. **What is the ONE thing they need to accomplish?** (their core job, not your feature list)\n4. **What would make them give up?** (too many clicks, jargon, slow, confusing)\n5. **How do they talk when frustrated?** (blunt, sweary, dismissive, sighing)\n\n### Good Persona Example\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.\n\n### Bad Persona Example\n> \"A user who doesn't like the app\" — too vague, no constraints, no voice.\n\nThe persona must be **specific enough to stay in character** for 20 minutes of testing.\n\n## Step 2: Become the Asshole (Browse as the Persona)\n\n1. Read any available project docs for app context and URLs\n2. **Fully inhabit the persona** — their frustrations, limitations, goals\n3. Navigate to the app using browser tools\n4. **Attempt the persona's ACTUAL TASKS** (not a feature tour):\n   - Can they do what they came to do?\n   - How many clicks\u002Fscreens to accomplish it?\n   - What confuses them?\n   - What makes them angry?\n   - Where do they get lost?\n   - What would make them give up and go back to their old way?\n\n5. Test these friction categories:\n   - **First impression** — would they even bother past the landing page?\n   - **Core workflow** — the ONE thing they need to do most often\n   - **Error recovery** — what happens when they do something wrong?\n   - **Readability** — text size, contrast, information density\n   - **Speed** — does it feel faster than their current method?\n   - **Terminology** — any jargon they wouldn't understand?\n   - **Navigation** — can they find their way back? do they know where they are?\n\n6. Take screenshots of every pain point\n7. Check browser console for JS errors on every page\n\n## Step 3: The Rant (Write Feedback in Character)\n\nWrite the feedback AS THE PERSONA — in their voice, with their frustrations. This is not a bug report. This is a real human venting.\n\n```\n[PERSONA NAME]'s Review of [PRODUCT]\n\nOverall: [Would they keep using it? Yes\u002FNo\u002FMaybe with conditions]\n\nTHE GOOD (grudging admission):\n- [things even they have to admit work]\n\nTHE BAD (legitimate UX issues):\n- [real problems that would stop them from using the product]\n\nTHE UGLY (showstoppers):\n- [things that would make them uninstall\u002Fcancel immediately]\n\nSPECIFIC COMPLAINTS:\n1. [Page\u002Ffeature]: \"[quote in persona voice]\" — [what happened, expected]\n2. ...\n\nVERDICT: \"[one-line persona quote summarizing their experience]\"\n```\n\n## Step 4: The Pragmatism Filter (Critical — Do Not Skip)\n\nStep OUT of the persona. Evaluate each complaint as a product person:\n\n- **RED: REAL UX BUG** — Any user would have this problem, not just grumpy ones. Fix it.\n- **YELLOW: VALID BUT LOW PRIORITY** — Real issue but only for extreme users. Note it.\n- **WHITE: PERSONA NOISE** — \"I hate computers\" talking, not a product problem. Skip it.\n- **GREEN: FEATURE REQUEST** — Good idea hidden in the complaint. Consider it.\n\n### Filter Criteria\n1. Would a 35-year-old competent-but-busy user have the same complaint? → RED\n2. Is this a genuine accessibility issue (font size, contrast, click targets)? → RED\n3. Is this \"I want it to work like paper\" resistance to digital? → WHITE\n4. Is this a real workflow inefficiency the persona stumbled on? → YELLOW or RED\n5. Would fixing this add complexity for the 80% who are fine? → WHITE\n6. Does the complaint reveal a missing onboarding moment? → GREEN\n\n**This filter is MANDATORY.** Never ship raw persona complaints as tickets.\n\n## Step 5: Create Tickets\n\nFor **RED** and **GREEN** items only:\n- Clear, actionable title\n- Include the persona's verbatim quote (entertaining + memorable)\n- The real UX issue underneath (objective)\n- A suggested fix (actionable)\n- Tag\u002Flabel: \"ux-review\"\n\nFor **YELLOW** items: one catch-all ticket with all notes.\n\n**WHITE** items appear in the report only. No tickets.\n\n**Max 10 tickets per session** — focus on the worst issues.\n\n## Step 6: Report\n\nDeliver:\n1. The persona rant (Step 3) — entertaining and visceral\n2. The filtered assessment (Step 4) — pragmatic and actionable\n3. Tickets created (Step 5) — with links\n4. Screenshots of key issues\n\n## Tips\n\n- **One persona per session.** Don't mix perspectives.\n- **Stay in character during Steps 2-3.** Break character only at Step 4.\n- **Test the CORE WORKFLOW first.** Don't get distracted by settings pages.\n- **Empty states are gold.** New user experience reveals the most friction.\n- **The best findings are RED items the persona found accidentally** while trying to do something else.\n- **If the persona has zero complaints, your persona is too tech-savvy.** Make them older, less patient, more set in their ways.\n- **Run this before demos, launches, or after shipping a batch of features.**\n- **Register as a NEW user when possible.** Don't use pre-seeded admin accounts — the cold start experience is where most friction lives.\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.\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.\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.\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.\n\n## Example Personas by Industry\n\nThese are starting points — customize for your specific product:\n\n| Product Type | Persona | Age | Key Trait |\n|-------------|---------|-----|-----------|\n| CRM | Retirement home director | 68 | Filing cabinet is the current CRM |\n| Photography SaaS | Rural wedding photographer | 62 | Books clients by phone, invoices on paper |\n| AI\u002FML Tool | Department store buyer | 55 | Burned by 3 failed tech startups |\n| Fitness App | Old-school gym coach | 58 | Paper notebook, thick fingers, bad eyes |\n| Accounting | Family bakery owner | 64 | Shoebox of receipts, hates subscriptions |\n| E-commerce | Market stall vendor | 60 | Cash only, smartphone is for calls |\n| Healthcare | Senior GP | 63 | Dictates notes, nurse handles the computer |\n| Education | Veteran teacher | 57 | Chalk and talk, worksheets in ring binders |\n\n## Rules\n\n- Stay in character during Steps 2-3\n- Be genuinely mean but fair — find real problems, not manufactured ones\n- The pragmatism filter (Step 4) is **MANDATORY**\n- Screenshots required for every complaint\n- Max 10 tickets per session\n- Test on staging\u002Fdeployed app, not local dev\n- One persona, one session, one report\n",{"name":5,"tags":24,"author":32,"source":33,"license":15,"version":34,"category":29,"platforms":35,"compatible":39,"description":7},[25,26,27,28,29,30,31],"qa","ux","testing","adversarial","dogfood","personas","user-testing","Omni @ Comelse","optional","1.0.0",[36,37,38],"linux","macos","windows",[40,41,42,43,44,45],"claude-code","openai-agents","hermes-agent","autogen","langchain","any-llm","master","4aa004da461d820f4ea5499e58eb8d196cf99016","optional-skills\u002Fadversarial-ux-test",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill adversarial-ux-test",{"tool":61,"command":62},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill adversarial-ux-test",{"tool":64,"command":65},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill adversarial-ux-test","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Foptional-skills\u002Fadversarial-ux-test\u002FSKILL.md",true,[],[70,77,84,91,98,105],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]