[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MBTZ3CBCQ61342KV2BCR6C":3,"skill-same:01M6MBTZ3CBCQ61342KV2BCR6C":110},{"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":31,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6MBTZ3CBCQ61342KV2BCR6C","ab-testing-platform-strategy",null,"Plan A\u002FB testing platform strategy, architecture, and build-vs-buy decisions for product engineering teams. Use when deciding whether to build or buy an experimentation platform, scoping feature flagging, targeting, assignment, exposure logging, metrics pipelines, dashboards, governance, or evolving a simple testing setup into a durable platform.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fab-testing-platform-strategy\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"ab testing platform strategy","platform strategy","strategy","ab","ab testing","testing","platform","simple testing","when","targeting","ab-testing","experimentation","practical","product engineering","scoping","plan","logging","product","code","analytics","architecture","2026-11-10 10:12:30",false,"---\nname: ab-testing-platform-strategy\ndescription: Plan A\u002FB testing platform strategy, architecture, and build-vs-buy decisions for product engineering teams. Use when deciding whether to build or buy an experimentation platform, scoping feature flagging, targeting, assignment, exposure logging, metrics pipelines, dashboards, governance, or evolving a simple testing setup into a durable platform.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: A\u002FB Testing Platform Strategy\n  category: Product Management\n  tags: practical-ab-testing,ab-testing,experimentation,platform-engineering,product-analytics\n---\n\n# A\u002FB Testing Platform Strategy\n\nUse this skill to decide how an organization should support A\u002FB testing through\nplatform choices, architecture, ownership, and incremental scope.\n\n## Source Traceability\n\nPrimary source: Practical A\u002FB Testing by Leemay Nassery. Guidance is\ntransformed and paraphrased from chapter 5 lines 3804-4443. Related startup\nand \"start simple\" context comes from preface lines 286-332 and chapter 2 lines\n1622-1628.\n\n## Related Advanced Skills\n\n- `experimentation-strategy-roadmap`: use when deciding which platform\n  capability to prioritize across rate, quality, cost, usability, and company\n  strategy.\n- `experimentation-throughput-strategy`: use when the platform needs capacity\n  visibility, isolated versus overlapping test policies, or coordination tools.\n- `experiment-verification-monitoring`: use when the platform needs QA tooling,\n  canaries, A\u002FA tests, active monitoring, leakage checks, or quality metrics.\n- `adaptive-experimentation-strategy`: use when considering sequential testing,\n  bandits, Thompson sampling, contextual bandits, or dynamic allocation support.\n\n## Reference Routing\n\n| Need | Read |\n|------|------|\n| Platform concepts and components | `references\u002Fcore\u002Fknowledge.md` |\n| Build-vs-buy and scoping rules | `references\u002Fcore\u002Frules.md` |\n| Scenario examples | `references\u002Fcore\u002Fexamples.md` |\n| Decision workflow | `workflows\u002Fdecide-platform-strategy.md` |\n\n## Workflow\n\n1. State the experimentation goals and current constraints.\n2. Inventory required platform components.\n3. Separate must-have launch capability from later platform maturity.\n4. Compare build, buy, and hybrid options against team capacity and risk.\n5. Plan data, assignment, exposure logging, metrics, and reporting ownership.\n6. Define the smallest useful platform and the triggers for expanding it.\n\n## Output Format\n\n```markdown\n# A\u002FB Testing Platform Strategy\n\n## Recommendation\n[Build | Buy | Hybrid | Start manually] because [reason].\n\n## Current Context\n- Team:\n- Product surface:\n- Experiment volume:\n- Data maturity:\n- Engineering capacity:\n\n## Required Capabilities\n| Capability | Need Now? | Build\u002FBuy\u002FManual | Owner |\n|------------|-----------|------------------|-------|\n\n## Tradeoffs\n- Build advantages:\n- Build risks:\n- Buy advantages:\n- Buy risks:\n- Hybrid notes:\n\n## Incremental Roadmap\n1. Minimum viable experimentation:\n2. Reliability and governance:\n3. Scale and self-service:\n```\n\n## Quality Bar\n\n- Do not recommend building a full platform before the team has proven demand.\n- Do not recommend buying without checking integration, data, and governance\n  fit.\n- Keep data and exposure logging first-class; a platform without trustworthy\n  measurement creates false confidence.\n- Treat platform scope as evolutionary, not all-or-nothing.\n","# A\u002FB Testing Platform Strategy\n\nUse this skill to decide how an organization should support A\u002FB testing through\nplatform choices, architecture, ownership, and incremental scope.\n\n## Source Traceability\n\nPrimary source: Practical A\u002FB Testing by Leemay Nassery. Guidance is\ntransformed and paraphrased from chapter 5 lines 3804-4443. Related startup\nand \"start simple\" context comes from preface lines 286-332 and chapter 2 lines\n1622-1628.\n\n## Related Advanced Skills\n\n- `experimentation-strategy-roadmap`: use when deciding which platform\n  capability to prioritize across rate, quality, cost, usability, and company\n  strategy.\n- `experimentation-throughput-strategy`: use when the platform needs capacity\n  visibility, isolated versus overlapping test policies, or coordination tools.\n- `experiment-verification-monitoring`: use when the platform needs QA tooling,\n  canaries, A\u002FA tests, active monitoring, leakage checks, or quality metrics.\n- `adaptive-experimentation-strategy`: use when considering sequential testing,\n  bandits, Thompson sampling, contextual bandits, or dynamic allocation support.\n\n## Reference Routing\n\n| Need | Read |\n|------|------|\n| Platform concepts and components | `references\u002Fcore\u002Fknowledge.md` |\n| Build-vs-buy and scoping rules | `references\u002Fcore\u002Frules.md` |\n| Scenario examples | `references\u002Fcore\u002Fexamples.md` |\n| Decision workflow | `workflows\u002Fdecide-platform-strategy.md` |\n\n## Workflow\n\n1. State the experimentation goals and current constraints.\n2. Inventory required platform components.\n3. Separate must-have launch capability from later platform maturity.\n4. Compare build, buy, and hybrid options against team capacity and risk.\n5. Plan data, assignment, exposure logging, metrics, and reporting ownership.\n6. Define the smallest useful platform and the triggers for expanding it.\n\n## Output Format\n\n```markdown\n# A\u002FB Testing Platform Strategy\n\n## Recommendation\n[Build | Buy | Hybrid | Start manually] because [reason].\n\n## Current Context\n- Team:\n- Product surface:\n- Experiment volume:\n- Data maturity:\n- Engineering capacity:\n\n## Required Capabilities\n| Capability | Need Now? | Build\u002FBuy\u002FManual | Owner |\n|------------|-----------|------------------|-------|\n\n## Tradeoffs\n- Build advantages:\n- Build risks:\n- Buy advantages:\n- Buy risks:\n- Hybrid notes:\n\n## Incremental Roadmap\n1. Minimum viable experimentation:\n2. Reliability and governance:\n3. Scale and self-service:\n```\n\n## Quality Bar\n\n- Do not recommend building a full platform before the team has proven demand.\n- Do not recommend buying without checking integration, data, and governance\n  fit.\n- Keep data and exposure logging first-class; a platform without trustworthy\n  measurement creates false confidence.\n- Treat platform scope as evolutionary, not all-or-nothing.\n",{"name":5,"license":15,"metadata":58,"description":7,"compatibility":63},{"tags":59,"version":60,"category":61,"displayName":62},"practical-ab-testing,ab-testing,experimentation,platform-engineering,product-analytics","0.1.0","Product Management","A\u002FB Testing Platform Strategy","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fab-testing-platform-strategy",474,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 14:40:14",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ab-testing-platform-strategy",{"tool":80,"command":81},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ab-testing-platform-strategy",{"tool":83,"command":84},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ab-testing-platform-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fab-testing-platform-strategy\u002FSKILL.md",true,[88,94,98,102,106],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"guidelines.md","REFERENCE","参考文档",1412,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fab-testing-platform-strategy\u002Fguidelines.md",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fcore\u002Fexamples.md",1509,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fab-testing-platform-strategy\u002Freferences\u002Fcore\u002Fexamples.md",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fcore\u002Fknowledge.md",2241,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fab-testing-platform-strategy\u002Freferences\u002Fcore\u002Fknowledge.md",{"path":103,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fcore\u002Frules.md",1994,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fab-testing-platform-strategy\u002Freferences\u002Fcore\u002Frules.md",{"path":107,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":108,"sourceHtmlUrl":109},"workflows\u002Fdecide-platform-strategy.md",1943,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fab-testing-platform-strategy\u002Fworkflows\u002Fdecide-platform-strategy.md",[111,120,127,134,160,185],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":119},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":119},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":119},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":53},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[141,142,143,144,145,146,147,148,149,150,151,40,152,153,154,155,156,157,158,159],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":53},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[167,168,169,155,170,171,172,173,174,175,176,177,178,179,146,180,181,182,183,184],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":198,"publishedAt":53},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[191,194,195],{"categoryNo":192,"categoryName":193,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":196,"categoryName":197,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[187,199,200,201,202,203,204,181,205,147,206,207,208,209,40,210,211,212,213,214],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]