[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74FAQX3VM9426F9CKW0VAXY":3,"skill-same:01M74FAQX3VM9426F9CKW0VAXY":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":13,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M74FAQX3VM9426F9CKW0VAXY","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.","lzy18001500226\u002FMoSim","lzy18001500226","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152623587?v=4","01M71ZMEX36NK05B642131DEEK","01M71ZMEXSMX72KPVNJ572G0CM",0,"MIT","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fdogfood\u002Fadversarial-ux-test\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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]\nmetadata:\n  hermes:\n    tags: [qa, ux, testing, adversarial, dogfood, personas, user-testing]\n    related_skills: [dogfood]\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,"author":23,"license":14,"version":24,"metadata":25,"platforms":36,"description":7},"Omni @ Comelse","1.0.0",{"hermes":26},{"tags":27,"related_skills":35},[28,29,30,31,32,33,34],"qa","ux","testing","adversarial","dogfood","personas","user-testing",[32],[37,38,39],"linux","macos","windows","main","e0ec177d00f087cb04e90206b2f7d3aa2f5a1350","References\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fdogfood\u002Fadversarial-ux-test","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim","https:\u002F\u002Fgithub.com\u002Flzy18001500226","2026-08-31 23:29:00",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add lzy18001500226\u002FMoSim --skill adversarial-ux-test",{"tool":52,"command":53},"bunx","bunx skills add lzy18001500226\u002FMoSim --skill adversarial-ux-test",{"tool":55,"command":56},"pnpm","pnpm dlx skills add lzy18001500226\u002FMoSim --skill adversarial-ux-test","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Foptional-skills\u002Fdogfood\u002Fadversarial-ux-test\u002FSKILL.md",true,[],[61,71,79,87,95,103],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":70},"01M78RK6JGRPTD3TDSMTQWDQ9P","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":70},"01M78RK29KVRDQXSMVZX1GQTJN","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":70},"01M78RJPF3210Y5DA9VJ6JMMG6","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":70},"01M78RJH7X67C5AY8ZVS7RQNWJ","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":70},"01M78RBBAYMJ6T3ZMAYHCFM6G7","skill-creator-cc","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":111},"01M76VV9V2R9FZTVGMJZV7Y996","prd-writing-guide","Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FSKILL.md",[],[],"2026-11-12 13:55:43"]