[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698Q70G4HPSFV27J0YBNAYS":3,"skill-same:01M698Q70G4HPSFV27J0YBNAYS":67},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M698Q70G4HPSFV27J0YBNAYS","clawhub-pr-maintainer",null,"Use when reviewing, triaging, validating, or discussing ClawHub GitHub issues or pull requests, including author context, CI, UI proof, evidence, labels, close decisions, and maintainer handoff.","openclaw\u002Fclawhub","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDMKEC6E49395505BD05",9555,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclawhub-pr-maintainer\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"clawhub","clawhub pr maintainer","pr","when","author","labels","requests","close","proof","evidence","use","context","decisions","ci","ui","pull","issues","github issues","pull requests","github","2026-11-10 10:12:30",false,"---\nname: clawhub-pr-maintainer\ndescription: Use when reviewing, triaging, validating, or discussing ClawHub GitHub issues or pull requests, including author context, CI, UI proof, evidence, labels, close decisions, and maintainer handoff.\n---\n\n# ClawHub PR Maintainer\n\nUse this skill for maintainer-facing ClawHub GitHub workflow, not for ordinary\nimplementation work.\n\n## Start With Live GitHub State\n\n- Use `gh pr view` or `gh issue view` against `openclaw\u002Fclawhub`; verify live\n  state before commenting, labeling, closing, or recommending merge.\n- For PRs, read title, body, author, labels, comments, files, commits, status\n  checks, review state, and linked issues.\n- Surface author identity briefly: GitHub name\u002Flogin and account age when\n  useful. Treat identity as triage signal, never as proof by itself.\n\nCommon read-only commands:\n\n```sh\ngh pr view \u003Cnumber> --repo openclaw\u002Fclawhub --json title,body,author,labels,comments,files,commits,statusCheckRollup,reviewDecision,url,additions,deletions,changedFiles\ngh issue view \u003Cnumber> --repo openclaw\u002Fclawhub --json title,body,author,labels,comments,state,url\ngh api users\u002F\u003Clogin> --jq '{login,name,created_at,type}'\n```\n\n## Review Evidence Bar\n\n- For bug fixes, require symptom evidence, a plausible root cause in the touched\n  code path, and either a regression test or focused manual proof.\n- For UI changes, require screenshots or video when the behavior is meaningfully\n  visual. Use tests as supplemental evidence, not a substitute for visible proof.\n- Do not merge or recommend merge based only on PR prose, AI rationale, or green\n  CI when the changed behavior has not been exercised.\n- For contributor-provided screenshots\u002Fvideos\u002Flogs, inspect the artifact\n  directly and state what it proves. Do not rerun `proof:ui` just to inspect\n  existing evidence.\n\n## Structure PR Review Output\n\n- Start every PR review with 1-3 plain sentences explaining what the change does\n  and why it matters.\n- Show size near the top as `LOC: +x\u002F-y (N files)`, using live PR stats or\n  local diff stats.\n- Then list findings first. If none, say `No blocking findings` or\n  `No findings`.\n- Always answer: affected ClawHub surface, bug or behavior being changed,\n  evidence checked, and best-fix verdict.\n- For bug\u002Fregression fixes, include a compact `Provenance:` line when a bounded\n  history pass identifies it. Separate code author, PR author,\n  merger\u002Fcommitter, current PR author, PR number, and date when those differ.\n  If the blamed PR was merged by automation, identify the human trigger when\n  practical; otherwise say trigger unknown.\n\n## Read Beyond The Diff\n\n- For code-path bug, regression, or behavior changes, review the surrounding\n  path, not just changed lines. Open the runtime entry point, owner module, one\n  caller, one callee, adjacent tests, and sibling surfaces that should share the\n  invariant.\n- For docs\u002Fconfig\u002Fprocess-only changes, read the changed file, its linked or\n  adjacent source of truth, and any route\u002Fworkflow\u002Ftemplate the change claims to\n  affect. Do not require runtime caller\u002Fcallee evidence when no runtime path\n  exists.\n- Compare against current `origin\u002Fmain` behavior or current published docs when\n  regression, compatibility, or user-visible docs accuracy matters.\n- For dependency-backed behavior, read the upstream docs\u002Fsource\u002Ftypes before\n  judging API use, defaults, output shapes, errors, timeouts, memory behavior, or\n  compatibility.\n- Mention the main files or contracts read when the verdict depends on\n  code-path, docs, config, or workflow evidence.\n- If a required path is uninspected, keep reading or mark\n  `Remaining uncertainty`; do not call the PR best, proof-sufficient, or\n  merge-ready.\n\n## Best-Fix Review Loop\n\nEvery PR review must explicitly answer: \"Is this the best fix, or only a\nplausible fix?\"\n\nBefore verdict:\n\n1. Reconstruct the bug, feature need, or behavior claim from the issue, PR, and\n   proof.\n2. For code-path changes, trace current behavior from entry point to failure or\n   decision point.\n3. For docs\u002Fconfig\u002Fprocess-only changes, trace the reader\u002Foperator workflow or\n   automation path the change is meant to clarify.\n4. Read touched files, relevant callers\u002Fcallees for code changes, adjacent docs\n   or tests, owner modules, and relevant source-of-truth docs.\n5. Read sibling surfaces that should share the invariant or could be broken by a\n   one-sided fix.\n6. Compare against current `origin\u002Fmain` and shipped behavior when relevant.\n7. Identify at least one alternative fix location or shape, then reject it with\n   evidence.\n\nReview output must include:\n\n- `Best-fix verdict:` best \u002F acceptable mitigation \u002F wrong layer \u002F too narrow \u002F\n  too broad.\n- `Alternatives considered:` 1-3 concrete alternatives and why rejected.\n- `Code read:` compact list of main files\u002Fcontracts checked.\n- `Remaining uncertainty:` what was not proven.\n\n## Enforce Bug-Fix Evidence\n\n- Never merge a bug-fix PR based only on issue text, PR text, or AI rationale.\n- Before recommending merge for a bug fix, require:\n  1. symptom evidence such as a repro, logs, failing test, or focused manual\n     proof\n  2. a verified root cause in code with file\u002Fline\n  3. blame-backed provenance for regressions when traceable, or commit SHA\u002Fdate\n     when no PR is traceable\n  4. a fix that touches the implicated code path\n  5. a regression test when feasible, or explicit manual verification plus a\n     reason no test was added\n- If the claim is unsubstantiated or likely wrong, request evidence or changes\n  instead of recommending merge.\n\n## Decide UI Proof Mode\n\nGenerate new visual evidence with the best proof runtime available in the\ncurrent session. Use Crabbox through `bun run proof:ui` only when a Crabbox\nskill or working Crabbox capability is available. Otherwise ignore Crabbox and\nrun the existing Playwright proof runtime against a real local ClawHub instance;\nmissing Crabbox access is not a blocker.\n\n- `before-after`: bug fixes, regressions, changed copy, changed layout, or any\n  PR where main-vs-candidate comparison clarifies the change.\n- `feature`: new page, new flow, new UI state, or behavior that cannot exist on\n  `origin\u002Fmain`.\n- No generated proof: docs-only, backend-only, tests-only, metadata-only, or\n  already-sufficient contributor evidence.\n\nWrite a temporary Playwright scenario under `.artifacts\u002Fproof-scenarios\u002F`; do\nnot infer manual clicks. Keep screenshots and videos in `.artifacts\u002F` until\npublishing. Never commit proof artifacts.\n\nFor the local fallback, start ClawHub with the relevant local Convex state and\nrun the scenario through the local Playwright runner:\n\n```sh\nbun run proof:ui -- --runner local --mode feature \\\n  --scenario .artifacts\u002Fproof-scenarios\u002F\u003Cname>.pw.ts \\\n  --candidate-url \u003Clocal-clawhub-url>\n```\n\nFor before\u002Fafter proof, run the same scenario against an `origin\u002Fmain` checkout\nand the candidate checkout, then pass both URLs with `--baseline-url` and\n`--candidate-url`. The runner accepts only localhost or loopback URLs and writes\npublishable `baseline\u002F` and `candidate\u002F` artifacts. Use the Codex app browser to\ninspect the running local instances and captured evidence.\n\n## Final Review Comment With Proof\n\nUse [proof-video](..\u002Fproof-video\u002FSKILL.md) for capture, editing, inspection and\npublication. Capture from the real running ClawHub instance and inspect every\nfinal image\u002Fvideo before uploading it. Lead with the successful candidate;\nlabel any failed baseline separately and state companion fixes and simulations.\n\nAttach inspected media directly to the PR with native GitHub attachments:\n\n```sh\ngh pr comment \u003Cnumber> --repo openclaw\u002Fclawhub \\\n  --body-file .artifacts\u002Fproof\u002Fcomment.md \\\n  --attach .artifacts\u002Fproof\u002Fafter.mp4 \\\n  --attach '.artifacts\u002Fproof\u002Fbefore.png#Before' \\\n  --attach '.artifacts\u002Fproof\u002Fafter.png#After'\n```\n\nVideos use bare uploaded URLs so GitHub renders players; do not add video alt\ntext. Include exact refs, the tested flow, validation and limitations in the\ncomment itself. Verify the final comment and return its direct link.\n\nNever push proof assets or generated reports to any product repository branch,\nincluding `qa-artifacts`. The old `proof:publish` helper is retired. Do not leave\nonly local paths or links to a source-tree directory as published evidence.\nIf attachment upload fails, retain the local files and report the precise\nblocker instead of claiming they are attached.\n\n## ClawSweeper\n\nClawSweeper is the bot control plane for automated PR\u002Fissue review once ClawHub\ndispatch is configured. Until then, use this skill for manual maintainer review.\nIf ClawSweeper has posted a review, read it as evidence but verify live PR state\nbefore acting.\n\n## Commenting And Labels\n\n- Use literal multiline comment bodies or `--body-file`; never pass escaped\n  `\\n` strings.\n- For issue comments and PR comments containing backticks or shell characters,\n  prefer a single-quoted heredoc or `--body-file` over inline `-b` bodies.\n- Do not wrap issue or PR refs like `#123` in backticks when you want GitHub to\n  auto-link them.\n- Keep maintainer comments short: finding, evidence, requested action, and\n  verification path.\n- Use `gh pr comment --body-file`; add `--attach` for inspected media. Follow\n  the proof-video skill for safe updates to an existing proof comment.\n- Do not close more than five issues\u002FPRs in one action without explicit\n  confirmation and the exact target list.\n","# ClawHub PR Maintainer\n\nUse this skill for maintainer-facing ClawHub GitHub workflow, not for ordinary\nimplementation work.\n\n## Start With Live GitHub State\n\n- Use `gh pr view` or `gh issue view` against `openclaw\u002Fclawhub`; verify live\n  state before commenting, labeling, closing, or recommending merge.\n- For PRs, read title, body, author, labels, comments, files, commits, status\n  checks, review state, and linked issues.\n- Surface author identity briefly: GitHub name\u002Flogin and account age when\n  useful. Treat identity as triage signal, never as proof by itself.\n\nCommon read-only commands:\n\n```sh\ngh pr view \u003Cnumber> --repo openclaw\u002Fclawhub --json title,body,author,labels,comments,files,commits,statusCheckRollup,reviewDecision,url,additions,deletions,changedFiles\ngh issue view \u003Cnumber> --repo openclaw\u002Fclawhub --json title,body,author,labels,comments,state,url\ngh api users\u002F\u003Clogin> --jq '{login,name,created_at,type}'\n```\n\n## Review Evidence Bar\n\n- For bug fixes, require symptom evidence, a plausible root cause in the touched\n  code path, and either a regression test or focused manual proof.\n- For UI changes, require screenshots or video when the behavior is meaningfully\n  visual. Use tests as supplemental evidence, not a substitute for visible proof.\n- Do not merge or recommend merge based only on PR prose, AI rationale, or green\n  CI when the changed behavior has not been exercised.\n- For contributor-provided screenshots\u002Fvideos\u002Flogs, inspect the artifact\n  directly and state what it proves. Do not rerun `proof:ui` just to inspect\n  existing evidence.\n\n## Structure PR Review Output\n\n- Start every PR review with 1-3 plain sentences explaining what the change does\n  and why it matters.\n- Show size near the top as `LOC: +x\u002F-y (N files)`, using live PR stats or\n  local diff stats.\n- Then list findings first. If none, say `No blocking findings` or\n  `No findings`.\n- Always answer: affected ClawHub surface, bug or behavior being changed,\n  evidence checked, and best-fix verdict.\n- For bug\u002Fregression fixes, include a compact `Provenance:` line when a bounded\n  history pass identifies it. Separate code author, PR author,\n  merger\u002Fcommitter, current PR author, PR number, and date when those differ.\n  If the blamed PR was merged by automation, identify the human trigger when\n  practical; otherwise say trigger unknown.\n\n## Read Beyond The Diff\n\n- For code-path bug, regression, or behavior changes, review the surrounding\n  path, not just changed lines. Open the runtime entry point, owner module, one\n  caller, one callee, adjacent tests, and sibling surfaces that should share the\n  invariant.\n- For docs\u002Fconfig\u002Fprocess-only changes, read the changed file, its linked or\n  adjacent source of truth, and any route\u002Fworkflow\u002Ftemplate the change claims to\n  affect. Do not require runtime caller\u002Fcallee evidence when no runtime path\n  exists.\n- Compare against current `origin\u002Fmain` behavior or current published docs when\n  regression, compatibility, or user-visible docs accuracy matters.\n- For dependency-backed behavior, read the upstream docs\u002Fsource\u002Ftypes before\n  judging API use, defaults, output shapes, errors, timeouts, memory behavior, or\n  compatibility.\n- Mention the main files or contracts read when the verdict depends on\n  code-path, docs, config, or workflow evidence.\n- If a required path is uninspected, keep reading or mark\n  `Remaining uncertainty`; do not call the PR best, proof-sufficient, or\n  merge-ready.\n\n## Best-Fix Review Loop\n\nEvery PR review must explicitly answer: \"Is this the best fix, or only a\nplausible fix?\"\n\nBefore verdict:\n\n1. Reconstruct the bug, feature need, or behavior claim from the issue, PR, and\n   proof.\n2. For code-path changes, trace current behavior from entry point to failure or\n   decision point.\n3. For docs\u002Fconfig\u002Fprocess-only changes, trace the reader\u002Foperator workflow or\n   automation path the change is meant to clarify.\n4. Read touched files, relevant callers\u002Fcallees for code changes, adjacent docs\n   or tests, owner modules, and relevant source-of-truth docs.\n5. Read sibling surfaces that should share the invariant or could be broken by a\n   one-sided fix.\n6. Compare against current `origin\u002Fmain` and shipped behavior when relevant.\n7. Identify at least one alternative fix location or shape, then reject it with\n   evidence.\n\nReview output must include:\n\n- `Best-fix verdict:` best \u002F acceptable mitigation \u002F wrong layer \u002F too narrow \u002F\n  too broad.\n- `Alternatives considered:` 1-3 concrete alternatives and why rejected.\n- `Code read:` compact list of main files\u002Fcontracts checked.\n- `Remaining uncertainty:` what was not proven.\n\n## Enforce Bug-Fix Evidence\n\n- Never merge a bug-fix PR based only on issue text, PR text, or AI rationale.\n- Before recommending merge for a bug fix, require:\n  1. symptom evidence such as a repro, logs, failing test, or focused manual\n     proof\n  2. a verified root cause in code with file\u002Fline\n  3. blame-backed provenance for regressions when traceable, or commit SHA\u002Fdate\n     when no PR is traceable\n  4. a fix that touches the implicated code path\n  5. a regression test when feasible, or explicit manual verification plus a\n     reason no test was added\n- If the claim is unsubstantiated or likely wrong, request evidence or changes\n  instead of recommending merge.\n\n## Decide UI Proof Mode\n\nGenerate new visual evidence with the best proof runtime available in the\ncurrent session. Use Crabbox through `bun run proof:ui` only when a Crabbox\nskill or working Crabbox capability is available. Otherwise ignore Crabbox and\nrun the existing Playwright proof runtime against a real local ClawHub instance;\nmissing Crabbox access is not a blocker.\n\n- `before-after`: bug fixes, regressions, changed copy, changed layout, or any\n  PR where main-vs-candidate comparison clarifies the change.\n- `feature`: new page, new flow, new UI state, or behavior that cannot exist on\n  `origin\u002Fmain`.\n- No generated proof: docs-only, backend-only, tests-only, metadata-only, or\n  already-sufficient contributor evidence.\n\nWrite a temporary Playwright scenario under `.artifacts\u002Fproof-scenarios\u002F`; do\nnot infer manual clicks. Keep screenshots and videos in `.artifacts\u002F` until\npublishing. Never commit proof artifacts.\n\nFor the local fallback, start ClawHub with the relevant local Convex state and\nrun the scenario through the local Playwright runner:\n\n```sh\nbun run proof:ui -- --runner local --mode feature \\\n  --scenario .artifacts\u002Fproof-scenarios\u002F\u003Cname>.pw.ts \\\n  --candidate-url \u003Clocal-clawhub-url>\n```\n\nFor before\u002Fafter proof, run the same scenario against an `origin\u002Fmain` checkout\nand the candidate checkout, then pass both URLs with `--baseline-url` and\n`--candidate-url`. The runner accepts only localhost or loopback URLs and writes\npublishable `baseline\u002F` and `candidate\u002F` artifacts. Use the Codex app browser to\ninspect the running local instances and captured evidence.\n\n## Final Review Comment With Proof\n\nUse [proof-video](..\u002Fproof-video\u002FSKILL.md) for capture, editing, inspection and\npublication. Capture from the real running ClawHub instance and inspect every\nfinal image\u002Fvideo before uploading it. Lead with the successful candidate;\nlabel any failed baseline separately and state companion fixes and simulations.\n\nAttach inspected media directly to the PR with native GitHub attachments:\n\n```sh\ngh pr comment \u003Cnumber> --repo openclaw\u002Fclawhub \\\n  --body-file .artifacts\u002Fproof\u002Fcomment.md \\\n  --attach .artifacts\u002Fproof\u002Fafter.mp4 \\\n  --attach '.artifacts\u002Fproof\u002Fbefore.png#Before' \\\n  --attach '.artifacts\u002Fproof\u002Fafter.png#After'\n```\n\nVideos use bare uploaded URLs so GitHub renders players; do not add video alt\ntext. Include exact refs, the tested flow, validation and limitations in the\ncomment itself. Verify the final comment and return its direct link.\n\nNever push proof assets or generated reports to any product repository branch,\nincluding `qa-artifacts`. The old `proof:publish` helper is retired. Do not leave\nonly local paths or links to a source-tree directory as published evidence.\nIf attachment upload fails, retain the local files and report the precise\nblocker instead of claiming they are attached.\n\n## ClawSweeper\n\nClawSweeper is the bot control plane for automated PR\u002Fissue review once ClawHub\ndispatch is configured. Until then, use this skill for manual maintainer review.\nIf ClawSweeper has posted a review, read it as evidence but verify live PR state\nbefore acting.\n\n## Commenting And Labels\n\n- Use literal multiline comment bodies or `--body-file`; never pass escaped\n  `\\n` strings.\n- For issue comments and PR comments containing backticks or shell characters,\n  prefer a single-quoted heredoc or `--body-file` over inline `-b` bodies.\n- Do not wrap issue or PR refs like `#123` in backticks when you want GitHub to\n  auto-link them.\n- Keep maintainer comments short: finding, evidence, requested action, and\n  verification path.\n- Use `gh pr comment --body-file`; add `--attach` for inspected media. Follow\n  the proof-video skill for safe updates to an existing proof comment.\n- Do not close more than five issues\u002FPRs in one action without explicit\n  confirmation and the exact target list.\n",{"name":5,"description":7},"main","fd6beef619775fe02dd2548b0658bf88b46d7740",".agents\u002Fskills\u002Fclawhub-pr-maintainer",1492,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub","https:\u002F\u002Fclawhub.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","Your personal, open source AI assistant.","2026-11-15 03:03:27",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add openclaw\u002Fclawhub --skill clawhub-pr-maintainer",{"tool":59,"command":60},"bunx","bunx skills add openclaw\u002Fclawhub --skill clawhub-pr-maintainer",{"tool":62,"command":63},"pnpm","pnpm dlx skills add openclaw\u002Fclawhub --skill clawhub-pr-maintainer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclawhub-pr-maintainer\u002FSKILL.md",true,[],[68,76,83,106,136,151],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":75},"01M7415W7GWE5XEH7ETJ1YWCF2","notes","Turn user-provided notes into a concise agenda.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002Fscripts\u002Fsecurity\u002Ffixtures\u002Ftemplate-qualification\u002Fskills\u002Fnotes\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":75},"01M7415V57FG63ZGV9W35MV3TH","hosted-research","Read approved reference material for the hosted proof.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002Ffixtures\u002Ftemplates\u002Fhosted-e2e\u002Fpackage\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":38},"01M698QE868QCJ1HN5H03NAKCZ","convex-advisor","Read the Convex deployment's 72h insights (read limits, OCC contention), root-cause each event in code, report evidence-backed perf\u002Fcost findings with fixes.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-advisor\u002FSKILL.md",[],[90,91,92,93,94,95,27,96,97,98,99,100,101,102,103,104,105],"convex advisor","advisor","convex","with","cost","perf","limits","fixes","event","deployment","read","report","insights","code","root","root-cause",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":117,"publishedAt":38},"01M698QD01M039DZ8WCRE8J6WY","convex-add","Add a capability to the CURRENT Convex app — consults the served Convex capability catalog for always-current procedures (billing, crons, auth, agent, search, …); falls back to built-in hosting or @convex-dev component search. TRIGGER when the user runs \u002Fadd, or asks to add hosting\u002Fpublishing or any backend capability to an existing Convex app.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-add\u002FSKILL.md",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[118,92,119,120,121,21,122,123,124,125,126,127,128,129,130,131,132,133,134,135],"add","convex add","publishing","user","Existing","dev","auth","hosting","catalog","trigger","search","for","back","capability","backend","app","billing","component",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":38},"01M698QBS5JVY310XM3RGFZCK4","convex-acquire-domain","Find and buy a domain for the current Convex app through Convex, then bind it (labs; spend action).","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-acquire-domain\u002FSKILL.md",[],[92,143,144,145,146,133,129,147,148,149,150],"domain","acquire","convex acquire domain","bind","find","buy","action","it",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":38},"01M698Q9P74GJAVDMCP33QBBWX","controlling-costs","Analyzes Axiom query patterns to find unused data, then builds dashboards and monitors for cost optimization. Use when asked to reduce Axiom costs, find unused columns or field values, identify data waste, or track ingest spend.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcontrolling-costs\u002FSKILL.md",[],[158,159,129,160,161,162,163,28,21,164,165,94,166,167,168,147,169,170,171],"controlling costs","data","Optimization","cost optimization","ingest","unused","reduce","query","track","values","axiom","columns","patterns","dashboards"]