[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698RV8GPTBN7GRF1MP1MXV1":3,"skill-same:01M698RV8GPTBN7GRF1MP1MXV1":95},{"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},"01M698RV8GPTBN7GRF1MP1MXV1","convex-setup-auth",null,"Sets up Convex auth, identity mapping, and access control. Use for login, auth providers, users tables, protected functions, or roles in a Convex app.","openclaw\u002Fclawhub","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDMKEC6E49395505BD05",9552,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-setup-auth\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"convex setup auth","convex","auth","setup","setup auth","for","convex auth","login","users","mapping","app","roles","control","Access Control","functions","up","use","access","Providers","identity","2026-11-10 10:12:30",false,"---\nname: convex-setup-auth\ndescription:\n  Sets up Convex auth, identity mapping, and access control. Use for login, auth\n  providers, users tables, protected functions, or roles in a Convex app.\n---\n\n# Convex Authentication Setup\n\nImplement secure authentication in Convex with user management and access\ncontrol.\n\n## When to Use\n\n- Setting up authentication for the first time\n- Implementing user management (users table, identity mapping)\n- Creating authentication helper functions\n- Setting up auth providers (Convex Auth, Clerk, WorkOS AuthKit, Auth0, custom\n  JWT)\n\n## When Not to Use\n\n- Auth for a non-Convex backend\n- Pure OAuth\u002FOIDC documentation without a Convex implementation\n- Debugging unrelated bugs that happen to surface near auth code\n- The auth provider is already fully configured and the user only needs a\n  one-line fix\n\n## First Step: Choose the Auth Provider\n\nConvex supports multiple authentication approaches. Do not assume a provider.\n\nBefore writing setup code:\n\n1. Ask the user which auth solution they want, unless the repository already\n   makes it obvious\n2. If the repo already uses a provider, continue with that provider unless the\n   user wants to switch\n3. If the user has not chosen a provider and the repo does not make it obvious,\n   ask before proceeding\n\nCommon options:\n\n- [Convex Auth](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fconvex-auth) - good default when\n  the user wants auth handled directly in Convex\n- [Clerk](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fclerk) - use when the app already uses\n  Clerk or the user wants Clerk's hosted auth features\n- [WorkOS AuthKit](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauthkit\u002F) - use when the app\n  already uses WorkOS or the user wants AuthKit specifically\n- [Auth0](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauth0) - use when the app already uses\n  Auth0\n- Custom JWT provider - use when integrating an existing auth system not covered\n  above\n\nLook for signals in the repo before asking:\n\n- Dependencies such as `@clerk\u002F*`, `@workos-inc\u002F*`, `@auth0\u002F*`, or Convex Auth\n  packages\n- Existing files such as `convex\u002Fauth.config.ts`, auth middleware, provider\n  wrappers, or login components\n- Environment variables that clearly point at a provider\n\n## After Choosing a Provider\n\nRead the provider's official guide and the matching local reference file:\n\n- Convex Auth: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fconvex-auth), then\n  `references\u002Fconvex-auth.md`\n- Clerk: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fclerk), then\n  `references\u002Fclerk.md`\n- WorkOS AuthKit: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauthkit\u002F), then\n  `references\u002Fworkos-authkit.md`\n- Auth0: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauth0), then\n  `references\u002Fauth0.md`\n\nThe local reference files contain the concrete workflow, expected files and env\nvars, gotchas, and validation checks.\n\nUse those sources for:\n\n- package installation\n- client provider wiring\n- environment variables\n- `convex\u002Fauth.config.ts` setup\n- login and logout UI patterns\n- framework-specific setup for React, Vite, or Next.js\n\nFor shared auth behavior, use the official Convex docs as the source of truth:\n\n- [Auth in Functions](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Ffunctions-auth) for\n  `ctx.auth.getUserIdentity()`\n- [Storing Users in the Convex Database](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fdatabase-auth)\n  for optional app-level user storage\n- [Authentication](https:\u002F\u002Fdocs.convex.dev\u002Fauth) for general auth and\n  authorization guidance\n- [Convex Auth Authorization](https:\u002F\u002Flabs.convex.dev\u002Fauth\u002Fauthz) when the\n  provider is Convex Auth\n\nPrefer official docs over recalled steps, because provider CLIs and Convex Auth\ninternals change between versions. Inventing setup from memory risks outdated\npatterns. For third-party providers, only add app-level user storage if the app\nactually needs user documents in Convex. Not every app needs a `users` table.\nFor Convex Auth, follow the Convex Auth docs and built-in auth tables rather\nthan adding a parallel `users` table plus `storeUser` flow, because Convex Auth\nalready manages user records internally. After running provider initialization\ncommands, verify generated files and complete the post-init wiring steps the\nprovider reference calls out. Initialization commands rarely finish the entire\nintegration.\n\n## Core Pattern: Protecting Backend Functions\n\nThe most common auth task is checking identity in Convex functions.\n\n```ts\n\u002F\u002F Bad: trusting a client-provided userId\nexport const getMyProfile = query({\n  args: { userId: v.id(\"users\") },\n  handler: async (ctx, args) => {\n    return await ctx.db.get(args.userId);\n  },\n});\n```\n\n```ts\n\u002F\u002F Good: verifying identity server-side\nexport const getMyProfile = query({\n  args: {},\n  handler: async (ctx) => {\n    const identity = await ctx.auth.getUserIdentity();\n    if (!identity) throw new Error(\"Not authenticated\");\n\n    return await ctx.db\n      .query(\"users\")\n      .withIndex(\"by_tokenIdentifier\", (q) =>\n        q.eq(\"tokenIdentifier\", identity.tokenIdentifier),\n      )\n      .unique();\n  },\n});\n```\n\n## Workflow\n\n1. Determine the provider, either by asking the user or inferring from the repo\n2. Ask whether the user wants local-only setup or production-ready setup now\n3. Read the matching provider reference file\n4. Follow the official provider docs for current setup details\n5. Follow the official Convex docs for shared backend auth behavior, user\n   storage, and authorization patterns\n6. Only add app-level user storage if the docs and app requirements call for it\n7. Add authorization checks for ownership, roles, or team access only where the\n   app needs them\n8. Verify login state, protected queries, environment variables, and production\n   configuration if requested\n\nIf the flow blocks on interactive provider or deployment setup, ask the user\nexplicitly for the exact human step needed, then continue after they complete\nit. For UI-facing auth flows, offer to validate the real sign-up or sign-in flow\nafter setup is done. If the environment has browser automation tools, you can\nuse them. If it does not, give the user a short manual validation checklist\ninstead.\n\n## Reference Files\n\n### Provider References\n\n- `references\u002Fconvex-auth.md`\n- `references\u002Fclerk.md`\n- `references\u002Fworkos-authkit.md`\n- `references\u002Fauth0.md`\n\n## Checklist\n\n- [ ] Chosen the correct auth provider before writing setup code\n- [ ] Read the relevant provider reference file\n- [ ] Asked whether the user wants local-only setup or production-ready setup\n- [ ] Used the official provider docs for provider-specific wiring\n- [ ] Used the official Convex docs for shared auth behavior and authorization\n      patterns\n- [ ] Only added app-level user storage if the app actually needs it\n- [ ] Did not invent a cross-provider `users` table or `storeUser` flow for\n      Convex Auth\n- [ ] Added authentication checks in protected backend functions\n- [ ] Added authorization checks where the app actually needs them\n- [ ] Clear error messages (\"Not authenticated\", \"Unauthorized\")\n- [ ] Client auth provider configured for the chosen provider\n- [ ] If requested, production auth setup is covered too\n","# Convex Authentication Setup\n\nImplement secure authentication in Convex with user management and access\ncontrol.\n\n## When to Use\n\n- Setting up authentication for the first time\n- Implementing user management (users table, identity mapping)\n- Creating authentication helper functions\n- Setting up auth providers (Convex Auth, Clerk, WorkOS AuthKit, Auth0, custom\n  JWT)\n\n## When Not to Use\n\n- Auth for a non-Convex backend\n- Pure OAuth\u002FOIDC documentation without a Convex implementation\n- Debugging unrelated bugs that happen to surface near auth code\n- The auth provider is already fully configured and the user only needs a\n  one-line fix\n\n## First Step: Choose the Auth Provider\n\nConvex supports multiple authentication approaches. Do not assume a provider.\n\nBefore writing setup code:\n\n1. Ask the user which auth solution they want, unless the repository already\n   makes it obvious\n2. If the repo already uses a provider, continue with that provider unless the\n   user wants to switch\n3. If the user has not chosen a provider and the repo does not make it obvious,\n   ask before proceeding\n\nCommon options:\n\n- [Convex Auth](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fconvex-auth) - good default when\n  the user wants auth handled directly in Convex\n- [Clerk](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fclerk) - use when the app already uses\n  Clerk or the user wants Clerk's hosted auth features\n- [WorkOS AuthKit](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauthkit\u002F) - use when the app\n  already uses WorkOS or the user wants AuthKit specifically\n- [Auth0](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauth0) - use when the app already uses\n  Auth0\n- Custom JWT provider - use when integrating an existing auth system not covered\n  above\n\nLook for signals in the repo before asking:\n\n- Dependencies such as `@clerk\u002F*`, `@workos-inc\u002F*`, `@auth0\u002F*`, or Convex Auth\n  packages\n- Existing files such as `convex\u002Fauth.config.ts`, auth middleware, provider\n  wrappers, or login components\n- Environment variables that clearly point at a provider\n\n## After Choosing a Provider\n\nRead the provider's official guide and the matching local reference file:\n\n- Convex Auth: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fconvex-auth), then\n  `references\u002Fconvex-auth.md`\n- Clerk: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fclerk), then\n  `references\u002Fclerk.md`\n- WorkOS AuthKit: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauthkit\u002F), then\n  `references\u002Fworkos-authkit.md`\n- Auth0: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauth0), then\n  `references\u002Fauth0.md`\n\nThe local reference files contain the concrete workflow, expected files and env\nvars, gotchas, and validation checks.\n\nUse those sources for:\n\n- package installation\n- client provider wiring\n- environment variables\n- `convex\u002Fauth.config.ts` setup\n- login and logout UI patterns\n- framework-specific setup for React, Vite, or Next.js\n\nFor shared auth behavior, use the official Convex docs as the source of truth:\n\n- [Auth in Functions](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Ffunctions-auth) for\n  `ctx.auth.getUserIdentity()`\n- [Storing Users in the Convex Database](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fdatabase-auth)\n  for optional app-level user storage\n- [Authentication](https:\u002F\u002Fdocs.convex.dev\u002Fauth) for general auth and\n  authorization guidance\n- [Convex Auth Authorization](https:\u002F\u002Flabs.convex.dev\u002Fauth\u002Fauthz) when the\n  provider is Convex Auth\n\nPrefer official docs over recalled steps, because provider CLIs and Convex Auth\ninternals change between versions. Inventing setup from memory risks outdated\npatterns. For third-party providers, only add app-level user storage if the app\nactually needs user documents in Convex. Not every app needs a `users` table.\nFor Convex Auth, follow the Convex Auth docs and built-in auth tables rather\nthan adding a parallel `users` table plus `storeUser` flow, because Convex Auth\nalready manages user records internally. After running provider initialization\ncommands, verify generated files and complete the post-init wiring steps the\nprovider reference calls out. Initialization commands rarely finish the entire\nintegration.\n\n## Core Pattern: Protecting Backend Functions\n\nThe most common auth task is checking identity in Convex functions.\n\n```ts\n\u002F\u002F Bad: trusting a client-provided userId\nexport const getMyProfile = query({\n  args: { userId: v.id(\"users\") },\n  handler: async (ctx, args) => {\n    return await ctx.db.get(args.userId);\n  },\n});\n```\n\n```ts\n\u002F\u002F Good: verifying identity server-side\nexport const getMyProfile = query({\n  args: {},\n  handler: async (ctx) => {\n    const identity = await ctx.auth.getUserIdentity();\n    if (!identity) throw new Error(\"Not authenticated\");\n\n    return await ctx.db\n      .query(\"users\")\n      .withIndex(\"by_tokenIdentifier\", (q) =>\n        q.eq(\"tokenIdentifier\", identity.tokenIdentifier),\n      )\n      .unique();\n  },\n});\n```\n\n## Workflow\n\n1. Determine the provider, either by asking the user or inferring from the repo\n2. Ask whether the user wants local-only setup or production-ready setup now\n3. Read the matching provider reference file\n4. Follow the official provider docs for current setup details\n5. Follow the official Convex docs for shared backend auth behavior, user\n   storage, and authorization patterns\n6. Only add app-level user storage if the docs and app requirements call for it\n7. Add authorization checks for ownership, roles, or team access only where the\n   app needs them\n8. Verify login state, protected queries, environment variables, and production\n   configuration if requested\n\nIf the flow blocks on interactive provider or deployment setup, ask the user\nexplicitly for the exact human step needed, then continue after they complete\nit. For UI-facing auth flows, offer to validate the real sign-up or sign-in flow\nafter setup is done. If the environment has browser automation tools, you can\nuse them. If it does not, give the user a short manual validation checklist\ninstead.\n\n## Reference Files\n\n### Provider References\n\n- `references\u002Fconvex-auth.md`\n- `references\u002Fclerk.md`\n- `references\u002Fworkos-authkit.md`\n- `references\u002Fauth0.md`\n\n## Checklist\n\n- [ ] Chosen the correct auth provider before writing setup code\n- [ ] Read the relevant provider reference file\n- [ ] Asked whether the user wants local-only setup or production-ready setup\n- [ ] Used the official provider docs for provider-specific wiring\n- [ ] Used the official Convex docs for shared auth behavior and authorization\n      patterns\n- [ ] Only added app-level user storage if the app actually needs it\n- [ ] Did not invent a cross-provider `users` table or `storeUser` flow for\n      Convex Auth\n- [ ] Added authentication checks in protected backend functions\n- [ ] Added authorization checks where the app actually needs them\n- [ ] Clear error messages (\"Not authenticated\", \"Unauthorized\")\n- [ ] Client auth provider configured for the chosen provider\n- [ ] If requested, production auth setup is covered too\n",{"name":5,"description":7},"main","fd6beef619775fe02dd2548b0658bf88b46d7740",".agents\u002Fskills\u002Fconvex-setup-auth",1494,"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-12 02:56:02",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add openclaw\u002Fclawhub --skill convex-setup-auth",{"tool":59,"command":60},"bunx","bunx skills add openclaw\u002Fclawhub --skill convex-setup-auth",{"tool":62,"command":63},"pnpm","pnpm dlx skills add openclaw\u002Fclawhub --skill convex-setup-auth","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-setup-auth\u002FSKILL.md",true,[67,73,79,83,87,91],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"agents\u002Fopenai.yaml","REFERENCE","参考文档",485,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-setup-auth\u002Fagents\u002Fopenai.yaml",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"assets\u002Ficon.svg","ASSET","资产文件",394,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-setup-auth\u002Fassets\u002Ficon.svg",{"path":80,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fauth0.md",7542,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-setup-auth\u002Freferences\u002Fauth0.md",{"path":84,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fclerk.md",6340,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-setup-auth\u002Freferences\u002Fclerk.md",{"path":88,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fconvex-auth.md",8400,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-setup-auth\u002Freferences\u002Fconvex-auth.md",{"path":92,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fworkos-authkit.md",6318,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconvex-setup-auth\u002Freferences\u002Fworkos-authkit.md",[96,119,147,162,183,210],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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",[],[103,19,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"convex advisor","advisor","perf","deployment","code","report","read","evidence","cost","root-cause","event","with","insights","root","fixes","limits",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":130,"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",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[131,19,132,133,20,134,135,136,137,138,139,140,141,28,142,143,23,144,145,146],"convex add","add","component","dev","search","user","catalog","backend","publishing","hosting","back","trigger","billing","Existing","capability","when",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"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",[],[154,19,155,156,157,158,159,28,160,161,23],"convex acquire domain","acquire","domain","find","buy","bind","it","action",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"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",[],[169,170,171,172,173,157,34,111,174,175,176,177,178,179,23,180,181,182,146],"controlling costs","cost optimization","Optimization","data","dashboards","ingest","patterns","query","columns","axiom","values","reduce","track","unused",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":195,"publishedAt":38},"01M698Q868XZ7WJ92AKABGJVTY","clawhub-production-release","Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend changes to clawhub.ai, dispatching the Deploy workflow, publishing a stable CLI tag, checking release prerequisites, or proving the exact production SHA and workflow outcome.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclawhub-production-release\u002FSKILL.md",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":193,"categoryName":194,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000011","运维与部署",[196,197,198,199,200,201,202,203,204,205,206,207,34,138,139,208,209,146],"clawhub production release","clawhub","release","Production","frontend","cli","workflow","deploy","run","npm","verify","outcome","releases","changes",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":216,"publishedAt":38},"01M698Q70G4HPSFV27J0YBNAYS","clawhub-pr-maintainer","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.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fclawhub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclawhub-pr-maintainer\u002FSKILL.md",[],[217,197,218,219,220,221,222,223,224,225,226,227,34,110,228,229,230,231,232,146],"clawhub pr maintainer","pr","github","pull requests","github issues","issues","pull","ui","ci","decisions","context","proof","close","requests","labels","author"]