[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDB33J1MBWX27WAJ6R402P":3,"skill-same:01M6MDB33J1MBWX27WAJ6R402P":60},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6MDB33J1MBWX27WAJ6R402P","five-whys",null,"Root cause analysis using the Five Whys technique. Use when a bug persists despite surface fixes, a failure recurs, or a process keeps breaking. Ensures the fix targets the root, not the symptom.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Ffive-whys\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"five whys","root cause analysis","analysis","fix","process","use","bug","targets","root","fixes","root cause","when","2026-11-10 10:12:30",false,"---\nname: five-whys\ndescription: Root cause analysis using the Five Whys technique. Use when a bug persists despite surface fixes, a failure recurs, or a process keeps breaking. Ensures the fix targets the root, not the symptom.\n---\n\n# Five Whys — Root Cause Analysis\n\n## The Rule\n\n```\nDO NOT FIX THE SYMPTOM. FIND THE CAUSE.\n```\n\nA fix that doesn't address the root cause is temporary. The cause returns.\n\n## Protocol\n\n### Step 1 — Define the problem precisely\n\nOne concrete sentence. Not vague.\n\n| Wrong | Correct |\n|-------|---------|\n| \"The system is slow\" | \"GET \u002Forders exceeds 3s for 90% of requests in prod since Friday\" |\n| \"Tests fail sometimes\" | \"test_payment_flow fails in CI roughly 1 in 20 runs with no clear error message\" |\n\n### Step 2 — Five Whys cascade\n\nFor each answer, ask: **\"Why does that happen?\"**\n\nDon't stop until you reach something you control — a decision, a process, a line of code, a missing configuration.\n\n```\nProblem: Users see another user's data\n  Why 1: Cache returns the wrong entry\n  Why 2: Cache key does not include user_id\n  Why 3: Developer assumed the endpoint was public\n  Why 4: No isolation test existed for this endpoint\n  Why 5: Code review had no data isolation checklist\n  → Root cause: review process missing a security checklist\n```\n\n### Step 3 — Validate in reverse\n\nRead the chain bottom-up: \"No review checklist → cache key missing user_id → data leak.\" If the chain holds, the root cause is valid.\n\n### Step 4 — Fix at the root, not the symptom\n\nFix at the deepest level that is practical to change.\n\n| Fix level | Example | Durability |\n|-----------|---------|------------|\n| Symptom | Manually flush cache | Hours |\n| Proximate cause | Add user_id to cache key | Days |\n| Root cause | Add isolation checklist to review | Permanent |\n\nIf you can only fix an intermediate level, document the root cause as tracked technical debt with a concrete TODO.\n\n## Branching\n\nA root cause can have multiple branches — explore all before choosing where to fix.\n\n```\nProblem: Deploy fails in prod but not in staging\n  Branch A: different configuration (env vars, secrets)\n  Branch B: prod data has different volume or format\n  Branch C: network dependencies only reachable in prod\n```\n\nTest each branch independently. Do not assume.\n\n## When to Stop\n\nStop before the 5th why if you reach a clear, actionable root cause. Stop after the 5th if the chain hasn't converged — there may be multiple independent root causes.\n\n## Output\n\nDocument the analysis:\n\n```markdown\n**Problem:** [concrete one-liner]\n**Root cause:** [deepest level found]\n**Fix:** [concrete action with file\u002Fcomponent]\n**Temporary fix (if needed):** [what you apply now while the real fix is in progress]\n**Technical debt:** [what remains unresolved and why]\n```\n\n## Integration with A Team\n\n- Run this skill **before** launching the `systematic-debugging` agent — Five Whys defines the investigation scope\n- After finding the root cause, use the `tdd-guide` agent to write the test that would have caught it\n- If the root cause implies a process change, document the analysis in `DAILY.md`\n","# Five Whys — Root Cause Analysis\n\n## The Rule\n\n```\nDO NOT FIX THE SYMPTOM. FIND THE CAUSE.\n```\n\nA fix that doesn't address the root cause is temporary. The cause returns.\n\n## Protocol\n\n### Step 1 — Define the problem precisely\n\nOne concrete sentence. Not vague.\n\n| Wrong | Correct |\n|-------|---------|\n| \"The system is slow\" | \"GET \u002Forders exceeds 3s for 90% of requests in prod since Friday\" |\n| \"Tests fail sometimes\" | \"test_payment_flow fails in CI roughly 1 in 20 runs with no clear error message\" |\n\n### Step 2 — Five Whys cascade\n\nFor each answer, ask: **\"Why does that happen?\"**\n\nDon't stop until you reach something you control — a decision, a process, a line of code, a missing configuration.\n\n```\nProblem: Users see another user's data\n  Why 1: Cache returns the wrong entry\n  Why 2: Cache key does not include user_id\n  Why 3: Developer assumed the endpoint was public\n  Why 4: No isolation test existed for this endpoint\n  Why 5: Code review had no data isolation checklist\n  → Root cause: review process missing a security checklist\n```\n\n### Step 3 — Validate in reverse\n\nRead the chain bottom-up: \"No review checklist → cache key missing user_id → data leak.\" If the chain holds, the root cause is valid.\n\n### Step 4 — Fix at the root, not the symptom\n\nFix at the deepest level that is practical to change.\n\n| Fix level | Example | Durability |\n|-----------|---------|------------|\n| Symptom | Manually flush cache | Hours |\n| Proximate cause | Add user_id to cache key | Days |\n| Root cause | Add isolation checklist to review | Permanent |\n\nIf you can only fix an intermediate level, document the root cause as tracked technical debt with a concrete TODO.\n\n## Branching\n\nA root cause can have multiple branches — explore all before choosing where to fix.\n\n```\nProblem: Deploy fails in prod but not in staging\n  Branch A: different configuration (env vars, secrets)\n  Branch B: prod data has different volume or format\n  Branch C: network dependencies only reachable in prod\n```\n\nTest each branch independently. Do not assume.\n\n## When to Stop\n\nStop before the 5th why if you reach a clear, actionable root cause. Stop after the 5th if the chain hasn't converged — there may be multiple independent root causes.\n\n## Output\n\nDocument the analysis:\n\n```markdown\n**Problem:** [concrete one-liner]\n**Root cause:** [deepest level found]\n**Fix:** [concrete action with file\u002Fcomponent]\n**Temporary fix (if needed):** [what you apply now while the real fix is in progress]\n**Technical debt:** [what remains unresolved and why]\n```\n\n## Integration with A Team\n\n- Run this skill **before** launching the `systematic-debugging` agent — Five Whys defines the investigation scope\n- After finding the root cause, use the `tdd-guide` agent to write the test that would have caught it\n- If the root cause implies a process change, document the analysis in `DAILY.md`\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Ffive-whys",483,"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-13 02:16:32",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill five-whys",{"tool":52,"command":53},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill five-whys",{"tool":55,"command":56},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill five-whys","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Ffive-whys\u002FSKILL.md",true,[],[61,69,76,83,108,133],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"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.","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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":68},"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":68},"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":31},"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",[],[90,91,92,93,94,95,96,97,22,98,99,30,100,101,102,103,104,105,106,107],"search","deja search","never","error","ready","memory","re","decide","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":31},"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",[],[115,116,117,103,118,119,120,121,122,123,124,125,126,127,95,128,129,130,131,132],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":150,"publishedAt":31},"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",[139,144,147],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":145,"categoryName":146,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":148,"categoryName":149,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000010","后端与接口",[135,151,152,153,154,155,156,129,157,96,158,159,160,161,30,162,163,164,165,166],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]