[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMWJJ4P8SD3X2C27358Q3N":3,"skill-same:01M6MMWJJ4P8SD3X2C27358Q3N":90},{"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":23,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6MMWJJ4P8SD3X2C27358Q3N","e2e-red-triage",null,"Classify one unexpected end-to-end test failure as a product defect or an environment fault needing a new preflight check. MANUAL-ONLY: load when the suite runner names a specific failure. NEVER auto-load from context.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsno-ai\u002Fsno-station-skills\u002Fskills\u002Fe2e-red-triage\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"e2e","e2e red triage","red","triage","runner","new","when","defect","suite","load","manual","as","classify","end","only","never","auto","environment","context","write","read","preflight","product","2026-11-10 10:12:30",false,"---\nname: e2e-red-triage\ndescription: \"Classify one unexpected end-to-end test failure as a product defect or an environment fault needing a new preflight check. MANUAL-ONLY: load when the suite runner names a specific failure. NEVER auto-load from context.\"\nrequires:\n  programs: []\n  harness:\n    - {slot: 4.shell, need: required}\n    - {slot: 4.file-read-write, need: required}\n---\n\n# e2e-red-triage — for the reds the preflight could not have predicted\n\nTerms are as in `e2e-environment-preflight`: a **row** is one acceptance check in the test plan, a **red** is a row that failed or gave no answer, a **journey** is one end-to-end scenario made of rows, the **suite** is all the rows of a journey, and **preflight** is the set of environment checks that must be green before the first row runs.\n\n**Never auto-triggered, and normally never needed.** One caller — the agent running the suite —\nand one moment:\n\n> The `e2e-environment-preflight` checks were **all green**, and a row went **red anyway** — or produced a\n> null, an empty, a zero, or a silence nobody can yet explain.\n\nIf preflight was not green, the suite should not have started. If a red is an ordinary product\nfailure with a clear cause, fix it and move on; this is not the ceremony for an ordinary bug.\nThis is the residual after the gate has done its work — a small fraction, and one\nthat shrinks every time move 3 is honoured.\n\n## Why this needs its own protocol\n\nThe preflight handles the failures somebody could enumerate in advance. What is left is the class\nwhere **the failure produced nothing rather than an error, and the nothing appeared far from its\ncause.** One null can mean five different things across five runs of the same suite; \"no results\" can mean the query matched nothing or the search never ran.\n\nThe hours such a red costs are spent **attributing an absence** — arguing about what a missing\nthing meant, from evidence that never contained the answer. Guessing feels faster than\ninstrumenting and is not: a wrong guess costs a full suite run to disprove, and a *plausible*\nwrong guess is worse than an implausible one because it stops the search.\n\nThe deeper version, and the one worth carrying: **the failure is usually a two-part outcome\ncollapsed into one verdict.** An HTTP 202 \"accepted\" means the request was queued, not that the work was done, and both caller and monitor read it as success until someone looks. A cleanly stopped service records\nan exit code that looks like a crash. In each case the evidence was there, in plain\nwords, and nobody split it.\n\n**So the first question is never \"why did it fail\" — it is \"what are the two halves of this\nresult, and which half am I looking at?\"**\n\n## The three moves, in order\n\nThese are defaults; a project may choose otherwise and record it in its local binding.\n\n### 1. Do not guess. Enter diagnosis.\n\nStop proposing causes. Write down first the two things this result could be a collapse of:\nsucceeded versus reached, stopped versus crashed, empty versus unreadable, absent versus\nnever-asked, zero-matches versus source-missing.\n\n### 2. The first change makes the absence name itself. Not the product.\n\n**The first commit after this kind of red does not touch product behaviour.** It changes whatever\nproduced the empty so that it says *why* it is empty — in the artifact, as a field, not in a log\nline, which is read only by someone who already suspects the answer.\n\n    result: null\n    →  result: {value: null, because: \"\u003Cthe reason, as a code>\"}\n\nThen re-run. Only now diagnose. This inverts the usual instinct and that is the point:\ninstrumenting first looks slower for one iteration and is faster from the second onward, because\nevery future occurrence of this absence becomes a single read instead of an investigation.\n\nTwo shapes to watch for here, because both report health while broken:\n\n- **A check that passes when its input source is missing.** A count over a path that does not\n  exist returns zero — the same zero a real path with no matches returns. Before any \"it is\n  absent\" claim, prove the place you looked at is real, then look.\n- **A condition that can no longer fire.** An alarm testing an absolute count rather than a delta\n  switches itself off permanently the first time the count moves.\n\nFeed every new check a known-wrong input and watch it go red. Instruments fail toward \"healthy\".\n\n### 3. The exit condition: come back with a durable check.\n\n**A diagnosis is not the end. The finding becomes a new preflight check for that system and a line in that system's primer (see `e2e-environment-preflight`), or this red is not closed.**\n\nInvoke `e2e-environment-preflight` to write it, and record the red in the red scoreboard described in `e2e-environment-preflight`, with its bucket and the new check's id:\n\n    {\"row\":\"\u003Crow-id>\",\"bucket\":\"environment\",\"note\":\"…\",\"owed_check\":\"\u003Ccheck-id>\"}\n\nThis is the only mechanism that makes the residual shrink. Without it the same class of absence\nis rediscovered every campaign and the gate never gets stronger — the process runs, everyone is\ndiligent, and the hours are spent again. **Hitting the wall is allowed; coming back with nothing\ndurable is not.**\n\n## Classify before you close\n\nEvery red gets exactly one bucket — `source`, `environment`, `stuck`, `harness`. Be honest about\n`stuck`: a run that produced no verdict at all is not a pass and not a skip, and burying it is how\na campaign reports coverage it never had.\n\nThe counts are the point. A journey whose reds are mostly `source` found bugs. One whose reds are\nmostly `environment` or `stuck` measured its own setup, and the fix for that is upstream in the preflight — never another round here.\n","# e2e-red-triage — for the reds the preflight could not have predicted\n\nTerms are as in `e2e-environment-preflight`: a **row** is one acceptance check in the test plan, a **red** is a row that failed or gave no answer, a **journey** is one end-to-end scenario made of rows, the **suite** is all the rows of a journey, and **preflight** is the set of environment checks that must be green before the first row runs.\n\n**Never auto-triggered, and normally never needed.** One caller — the agent running the suite —\nand one moment:\n\n> The `e2e-environment-preflight` checks were **all green**, and a row went **red anyway** — or produced a\n> null, an empty, a zero, or a silence nobody can yet explain.\n\nIf preflight was not green, the suite should not have started. If a red is an ordinary product\nfailure with a clear cause, fix it and move on; this is not the ceremony for an ordinary bug.\nThis is the residual after the gate has done its work — a small fraction, and one\nthat shrinks every time move 3 is honoured.\n\n## Why this needs its own protocol\n\nThe preflight handles the failures somebody could enumerate in advance. What is left is the class\nwhere **the failure produced nothing rather than an error, and the nothing appeared far from its\ncause.** One null can mean five different things across five runs of the same suite; \"no results\" can mean the query matched nothing or the search never ran.\n\nThe hours such a red costs are spent **attributing an absence** — arguing about what a missing\nthing meant, from evidence that never contained the answer. Guessing feels faster than\ninstrumenting and is not: a wrong guess costs a full suite run to disprove, and a *plausible*\nwrong guess is worse than an implausible one because it stops the search.\n\nThe deeper version, and the one worth carrying: **the failure is usually a two-part outcome\ncollapsed into one verdict.** An HTTP 202 \"accepted\" means the request was queued, not that the work was done, and both caller and monitor read it as success until someone looks. A cleanly stopped service records\nan exit code that looks like a crash. In each case the evidence was there, in plain\nwords, and nobody split it.\n\n**So the first question is never \"why did it fail\" — it is \"what are the two halves of this\nresult, and which half am I looking at?\"**\n\n## The three moves, in order\n\nThese are defaults; a project may choose otherwise and record it in its local binding.\n\n### 1. Do not guess. Enter diagnosis.\n\nStop proposing causes. Write down first the two things this result could be a collapse of:\nsucceeded versus reached, stopped versus crashed, empty versus unreadable, absent versus\nnever-asked, zero-matches versus source-missing.\n\n### 2. The first change makes the absence name itself. Not the product.\n\n**The first commit after this kind of red does not touch product behaviour.** It changes whatever\nproduced the empty so that it says *why* it is empty — in the artifact, as a field, not in a log\nline, which is read only by someone who already suspects the answer.\n\n    result: null\n    →  result: {value: null, because: \"\u003Cthe reason, as a code>\"}\n\nThen re-run. Only now diagnose. This inverts the usual instinct and that is the point:\ninstrumenting first looks slower for one iteration and is faster from the second onward, because\nevery future occurrence of this absence becomes a single read instead of an investigation.\n\nTwo shapes to watch for here, because both report health while broken:\n\n- **A check that passes when its input source is missing.** A count over a path that does not\n  exist returns zero — the same zero a real path with no matches returns. Before any \"it is\n  absent\" claim, prove the place you looked at is real, then look.\n- **A condition that can no longer fire.** An alarm testing an absolute count rather than a delta\n  switches itself off permanently the first time the count moves.\n\nFeed every new check a known-wrong input and watch it go red. Instruments fail toward \"healthy\".\n\n### 3. The exit condition: come back with a durable check.\n\n**A diagnosis is not the end. The finding becomes a new preflight check for that system and a line in that system's primer (see `e2e-environment-preflight`), or this red is not closed.**\n\nInvoke `e2e-environment-preflight` to write it, and record the red in the red scoreboard described in `e2e-environment-preflight`, with its bucket and the new check's id:\n\n    {\"row\":\"\u003Crow-id>\",\"bucket\":\"environment\",\"note\":\"…\",\"owed_check\":\"\u003Ccheck-id>\"}\n\nThis is the only mechanism that makes the residual shrink. Without it the same class of absence\nis rediscovered every campaign and the gate never gets stronger — the process runs, everyone is\ndiligent, and the hours are spent again. **Hitting the wall is allowed; coming back with nothing\ndurable is not.**\n\n## Classify before you close\n\nEvery red gets exactly one bucket — `source`, `environment`, `stuck`, `harness`. Be honest about\n`stuck`: a run that produced no verdict at all is not a pass and not a skip, and burying it is how\na campaign reports coverage it never had.\n\nThe counts are the point. A journey whose reds are mostly `source` found bugs. One whose reds are\nmostly `environment` or `stuck` measured its own setup, and the fix for that is upstream in the preflight — never another round here.\n",{"name":5,"requires":52,"description":7},{"harness":53,"programs":59},[54,57],{"need":55,"slot":56},"required","4.shell",{"need":55,"slot":58},"4.file-read-write",[],"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fsno-ai\u002Fsno-station-skills\u002Fskills\u002Fe2e-red-triage",491,"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-14 14:06:13",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill e2e-red-triage",{"tool":76,"command":77},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill e2e-red-triage",{"tool":79,"command":80},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill e2e-red-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsno-ai\u002Fsno-station-skills\u002Fskills\u002Fe2e-red-triage\u002FSKILL.md",true,[84],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fselftest\u002Frun-selftest.sh","SCRIPT","脚本",1196,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsno-ai\u002Fsno-station-skills\u002Fskills\u002Fe2e-red-triage\u002Fscripts\u002Fselftest\u002Frun-selftest.sh",[91,101,109,117,125,133],{"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":95,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":100},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":100},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":100},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":100},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":100},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"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":95,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":100},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]