[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KZCXK5PCYWWW5FCVDYPAXK":3,"skill-same:01M6KZCXK5PCYWWW5FCVDYPAXK":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":46,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6KZCXK5PCYWWW5FCVDYPAXK","retrigger-flaky-ci",null,"Triage failed CI on a pull request or the active branch, decide whether the failures come from its changes, and rerun only failures that are unrelated. Use when asked to retrigger, rerun, or kick CI on a PR with failing checks.","openclaw\u002Fopenclaw-windows-node","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698Q6SND6RHZDPP8ZM0NSP7",2198,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fretrigger-flaky-ci\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"retrigger flaky ci","ci","when","failing","rerun","use","triage","only","decide","request","active","pull request","pr","changes","unrelated","branch","with","pull","2026-11-10 10:12:30",false,"---\nname: retrigger-flaky-ci\ndescription: \"Triage failed CI on a pull request or the active branch, decide whether the failures come from its changes, and rerun only failures that are unrelated. Use when asked to retrigger, rerun, or kick CI on a PR with failing checks.\"\n---\n\n# Retrigger flaky CI\n\nUse this skill when a user asks to retrigger, rerun, or restart CI for a pull\nrequest, or for the PR backing the current branch. The request authorizes a\nrerun of failed jobs on that PR only. It does not authorize pushing, editing\nthe PR, changing labels, or rerunning other PRs.\n\nNever rerun first and investigate later. Read the failure, compare it with the\nPR's changes, then either warn the user or rerun.\n\n## 1. Resolve the PR and its changes\n\nResolve the PR by number, or from the current branch when no number is given:\n\n```powershell\ngh pr view \u003Cnumber> --json number,title,headRefName,headRefOid,files,statusCheckRollup,url\ngh pr view --json number,title,headRefName,headRefOid,files,statusCheckRollup,url\n```\n\nRecord the PR head SHA and the changed file list. When the request refers to the\nactive branch, also compare local work with the PR:\n\n```powershell\ngit rev-parse HEAD\ngit status -sb\ngit fetch origin main --quiet\ngit diff --stat origin\u002Fmain...HEAD\n```\n\nIf local `HEAD` differs from the PR head, or there are uncommitted changes, the\nCI run did not test them. Say so, and judge the failure against the PR head\nthat CI actually ran.\n\nPull request runs of `Build and Test` check out `refs\u002Fpull\u002F\u003Cnumber>\u002Fmerge`, so\nthey include the current `main`. A failure can come from `main` rather than from\nthe PR.\n\n## 2. Read the actual failures\n\nList the failing checks from `statusCheckRollup`. `CI Gate` only aggregates the\nrequired jobs. Look at the jobs it reports as failed instead of `CI Gate` itself.\nIf checks are still queued or running, report that and stop. A partial run is\nnot grounds for a rerun.\n\nRead the failed job logs:\n\n```powershell\ngh run view \u003Crun-id> --log-failed\ngh run view \u003Crun-id> --job \u003Cjob-id> --log-failed\n```\n\nFind the specific failure in each failing job: `[FAIL]` and `Failed \u003CTestName>`\nlines with their `Error Message` and stack trace, `error CS` or `error MSB`\nbuild errors, `Test host process crashed`, validator output, or the step that\nreported `##[error]`. Record the test or step, the error, and the top stack\nframes that belong to the repository.\n\n## 3. Decide whether the PR caused the failure\n\nTreat a failure as **related** if any of the following is true:\n\n- It is a build, analyzer, or compile error in a changed file, or in code that\n  calls an API the PR changed.\n- The failing test file is in the PR diff, or the test directly exercises a\n  production owner, method, string resource, or contract the PR changed.\n  Map the repository frames in the stack trace to the diff.\n- It is a deterministic assertion about behavior, copy, localization,\n  architecture ledgers, docs, skills, proof pools, or CI classification that\n  the PR touched.\n- It fails the same way on more than one attempt of the same head SHA.\n- It reproduces locally on the PR head with a focused run, for example\n  `dotnet test \u003Cproject> --filter \"FullyQualifiedName~\u003CTestName>\"`.\n\nTreat a failure as **unrelated** only with positive evidence, such as:\n\n- The failing code path does not touch anything in the diff, and the diff\n  adds no startup, background, or Gateway traffic that could reach it.\n- The same test or job fails on `main` or on unrelated PRs:\n\n  ```powershell\n  gh run list --workflow \"Build and Test\" --status failure --limit 25 --json databaseId,headBranch,event,createdAt,displayTitle\n  gh run view \u003Cother-run-id> --log-failed\n  ```\n\n- Retained CI evidence or an existing issue shows the same failure on the\n  recorded base revision, and comparison confirms the PR does not introduce it.\n- It has the shape of a timing or infrastructure failure: a UI Automation\n  element briefly missing (`NullReferenceException` inside a wait lambda), a\n  `TimeoutException` from a fixture wait, a wall-clock limit on a loaded\n  runner, a crashed test host, a network or restore error, a runner shutdown,\n  or a missing hosted tool.\n\nA timeout counts as flaky only when the waited-for behavior is outside the\ndiff. A timeout in a path the PR changed is a related failure until it is\nreproduced or ruled out locally.\n\nIf the evidence is mixed and a focused local run is possible, run it. If it\nremains ambiguous, do not rerun. Report the uncertainty and ask the user.\n\nIf the failure is unrelated but deterministic on `main` (it fails on every\nrecent `main` run), a rerun will not help. Report it as a `main` breakage\nand do not rerun.\n\n## 4a. Related: warn and do not rerun\n\nDo not rerun. Tell the user that the failures come from the PR's changes. For\neach failure, give the job, the test or step, the error, and the changed file or\nowner that connects to it. Do not edit code unless the user asks for a fix.\n\n## 4b. Unrelated: summarize, then rerun failed jobs\n\nShow a short table before rerunning:\n\n| Job | Failing test or step | Error | Why it is unrelated |\n|---|---|---|---|\n\nThen rerun only the failed jobs of each failed run. Rerunning a job also\nreruns the jobs that depend on it, including `CI Gate`:\n\n```powershell\ngh run rerun \u003Crun-id> --failed\ngh run view \u003Crun-id> --json status,attempt,url\n```\n\nReport the run URL and the new status. Do not wait for the rerun to finish\nunless the user asks. If `gh run rerun` is refused, for example because of\nmissing permission or a fork run that needs approval, report the error as is.\n\nDo not rerun the same failure on the same head more than once. A second\nidentical failure on the same SHA reclassifies it as related, or as a real\n`main` breakage. Stop rerunning and report the evidence and blocker. When\nauthorized to fix it, investigate the cause, implement the repair, and validate\nit. Do not create a checked-in failure backlog.\n\n## Report\n\n- PR number and title, head SHA, and whether local work matches it.\n- Each failing job with its test or step and error.\n- The related or unrelated decision for each failure, with its evidence (diff\n  overlap, matching baseline failures, existing issue evidence, local reproduction).\n- The action taken: no rerun with a warning, or the rerun command and the new\n  run status.\n","# Retrigger flaky CI\n\nUse this skill when a user asks to retrigger, rerun, or restart CI for a pull\nrequest, or for the PR backing the current branch. The request authorizes a\nrerun of failed jobs on that PR only. It does not authorize pushing, editing\nthe PR, changing labels, or rerunning other PRs.\n\nNever rerun first and investigate later. Read the failure, compare it with the\nPR's changes, then either warn the user or rerun.\n\n## 1. Resolve the PR and its changes\n\nResolve the PR by number, or from the current branch when no number is given:\n\n```powershell\ngh pr view \u003Cnumber> --json number,title,headRefName,headRefOid,files,statusCheckRollup,url\ngh pr view --json number,title,headRefName,headRefOid,files,statusCheckRollup,url\n```\n\nRecord the PR head SHA and the changed file list. When the request refers to the\nactive branch, also compare local work with the PR:\n\n```powershell\ngit rev-parse HEAD\ngit status -sb\ngit fetch origin main --quiet\ngit diff --stat origin\u002Fmain...HEAD\n```\n\nIf local `HEAD` differs from the PR head, or there are uncommitted changes, the\nCI run did not test them. Say so, and judge the failure against the PR head\nthat CI actually ran.\n\nPull request runs of `Build and Test` check out `refs\u002Fpull\u002F\u003Cnumber>\u002Fmerge`, so\nthey include the current `main`. A failure can come from `main` rather than from\nthe PR.\n\n## 2. Read the actual failures\n\nList the failing checks from `statusCheckRollup`. `CI Gate` only aggregates the\nrequired jobs. Look at the jobs it reports as failed instead of `CI Gate` itself.\nIf checks are still queued or running, report that and stop. A partial run is\nnot grounds for a rerun.\n\nRead the failed job logs:\n\n```powershell\ngh run view \u003Crun-id> --log-failed\ngh run view \u003Crun-id> --job \u003Cjob-id> --log-failed\n```\n\nFind the specific failure in each failing job: `[FAIL]` and `Failed \u003CTestName>`\nlines with their `Error Message` and stack trace, `error CS` or `error MSB`\nbuild errors, `Test host process crashed`, validator output, or the step that\nreported `##[error]`. Record the test or step, the error, and the top stack\nframes that belong to the repository.\n\n## 3. Decide whether the PR caused the failure\n\nTreat a failure as **related** if any of the following is true:\n\n- It is a build, analyzer, or compile error in a changed file, or in code that\n  calls an API the PR changed.\n- The failing test file is in the PR diff, or the test directly exercises a\n  production owner, method, string resource, or contract the PR changed.\n  Map the repository frames in the stack trace to the diff.\n- It is a deterministic assertion about behavior, copy, localization,\n  architecture ledgers, docs, skills, proof pools, or CI classification that\n  the PR touched.\n- It fails the same way on more than one attempt of the same head SHA.\n- It reproduces locally on the PR head with a focused run, for example\n  `dotnet test \u003Cproject> --filter \"FullyQualifiedName~\u003CTestName>\"`.\n\nTreat a failure as **unrelated** only with positive evidence, such as:\n\n- The failing code path does not touch anything in the diff, and the diff\n  adds no startup, background, or Gateway traffic that could reach it.\n- The same test or job fails on `main` or on unrelated PRs:\n\n  ```powershell\n  gh run list --workflow \"Build and Test\" --status failure --limit 25 --json databaseId,headBranch,event,createdAt,displayTitle\n  gh run view \u003Cother-run-id> --log-failed\n  ```\n\n- Retained CI evidence or an existing issue shows the same failure on the\n  recorded base revision, and comparison confirms the PR does not introduce it.\n- It has the shape of a timing or infrastructure failure: a UI Automation\n  element briefly missing (`NullReferenceException` inside a wait lambda), a\n  `TimeoutException` from a fixture wait, a wall-clock limit on a loaded\n  runner, a crashed test host, a network or restore error, a runner shutdown,\n  or a missing hosted tool.\n\nA timeout counts as flaky only when the waited-for behavior is outside the\ndiff. A timeout in a path the PR changed is a related failure until it is\nreproduced or ruled out locally.\n\nIf the evidence is mixed and a focused local run is possible, run it. If it\nremains ambiguous, do not rerun. Report the uncertainty and ask the user.\n\nIf the failure is unrelated but deterministic on `main` (it fails on every\nrecent `main` run), a rerun will not help. Report it as a `main` breakage\nand do not rerun.\n\n## 4a. Related: warn and do not rerun\n\nDo not rerun. Tell the user that the failures come from the PR's changes. For\neach failure, give the job, the test or step, the error, and the changed file or\nowner that connects to it. Do not edit code unless the user asks for a fix.\n\n## 4b. Unrelated: summarize, then rerun failed jobs\n\nShow a short table before rerunning:\n\n| Job | Failing test or step | Error | Why it is unrelated |\n|---|---|---|---|\n\nThen rerun only the failed jobs of each failed run. Rerunning a job also\nreruns the jobs that depend on it, including `CI Gate`:\n\n```powershell\ngh run rerun \u003Crun-id> --failed\ngh run view \u003Crun-id> --json status,attempt,url\n```\n\nReport the run URL and the new status. Do not wait for the rerun to finish\nunless the user asks. If `gh run rerun` is refused, for example because of\nmissing permission or a fork run that needs approval, report the error as is.\n\nDo not rerun the same failure on the same head more than once. A second\nidentical failure on the same SHA reclassifies it as related, or as a real\n`main` breakage. Stop rerunning and report the evidence and blocker. When\nauthorized to fix it, investigate the cause, implement the repair, and validate\nit. Do not create a checked-in failure backlog.\n\n## Report\n\n- PR number and title, head SHA, and whether local work matches it.\n- Each failing job with its test or step and error.\n- The related or unrelated decision for each failure, with its evidence (diff\n  overlap, matching baseline failures, existing issue evidence, local reproduction).\n- The action taken: no rerun with a warning, or the rerun command and the new\n  run status.\n",{"name":5,"description":7},"main","3d5f14270dd6bd8b260a723ff2e73a68ea858ca8",".agents\u002Fskills\u002Fretrigger-flaky-ci",349,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-14 18:13:49",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add openclaw\u002Fopenclaw-windows-node --skill retrigger-flaky-ci",{"tool":56,"command":57},"bunx","bunx skills add openclaw\u002Fopenclaw-windows-node --skill retrigger-flaky-ci",{"tool":59,"command":60},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw-windows-node --skill retrigger-flaky-ci","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fretrigger-flaky-ci\u002FSKILL.md",true,[],[65,73,92,111,132,153],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":72},"01M7416EHCYH7YCJ9XPSQ2844V","network-handoff","Use before generating, changing, or reviewing networking, IPC, or cross-process handoffs, including requests, retries, deadlines, reconnect, process launch, configuration apply, cancellation, and cleanup. Establish confirmation, identity, authority, reconciliation, and producer compatibility before implementation.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fnetwork-handoff\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":36},"01M698QMQN5TQES4R7ZPTYAZF5","technical-documentation","Write, review, or restructure Windows node documentation and agent instructions using current source, task-focused explanations, and explicit fact preservation.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftechnical-documentation\u002FSKILL.md",[],[80,81,82,83,84,85,86,87,88,89,90,91],"documentation","technical","technical documentation","agent instructions","windows","task","review","instructions","write","node","preservation","source",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":36},"01M698QKPXJ8ZG34MYHPPCAT4T","pr-simplify","Simplify your own Windows-node change to its smallest complete fix while preserving distinct regressions, platform contracts, and required proof. Use after implementation before PR preparation, after large repairs, or when asked to shrink a change or remove slop.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-simplify\u002FSKILL.md",[],[99,30,100,101,102,20,23,103,104,105,106,107,84,89,108,109,110],"simplify","pr simplify","slop","change","fix","complete","remove","preparation","platform","implementation","proof","contracts",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":122,"publishedAt":36},"01M698QJEA384YPM8R9CPZ1YFD","openclaw-testing","Choose proportional OpenClaw Windows node tests, builds, packaging checks, and runtime proof, then diagnose failures without weakening required gates.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-testing\u002FSKILL.md",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[123,9,124,109,89,125,126,84,127,128,129,130,131],"testing","openclaw testing","gates","runtime proof","diagnose","runtime","packaging","choose","tests",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":141,"publishedAt":36},"01M698QH7JVVA09769ER9P2TKY","openclaw-proof-validation","Plan and collect OpenClaw Windows validation\u002Fproof: tests, rubber-duck review, UI evidence, MCP output, and gateway runtime proof.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-proof-validation\u002FSKILL.md",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000023","Skill与智能体开发",[109,142,9,143,144,131,145,128,146,84,147,126,86,148,149,150,151,152],"validation","openclaw proof validation","MCP","collect","evidence","gateway","output","plan","ui evidence","ui","duck",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":164,"publishedAt":36},"01M698QFXW9PDK8YZ467MBW5P1","openclaw-debugging","Debug OpenClaw Windows Companion, setup, Gateway connection, node capabilities, packaged permissions, updates, installers, and system.run by selecting the failing boundary and proof path before changing code.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw-windows-node\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenclaw-debugging\u002FSKILL.md",[159],{"categoryNo":160,"categoryName":161,"taxonomyType":162,"taxonomyTypeDesc":163},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[9,165,166,167,168,169,21,170,171,147,84,172,109,173,174,175,176,89,177,178],"debugging","openclaw debugging","updates","code","capabilities","companion","path","setup","connection","boundary","debug","system","run","permissions"]