[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79GPARBNTJ6B4HZK34PES5N":3,"skill-same:01M79GPARBNTJ6B4HZK34PES5N":111},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79GPARBNTJ6B4HZK34PES5N","cloud-api-operations",null,"Operate Tencent Cloud control-plane resources (monitoring\u002Falarms, CLB, CAM roles, COS, MySQL, SCF) via cloud APIs when no dedicated MCP tool covers the task. Use when a task needs control-plane operations beyond CloudBase's own tooling, or when a callCloudApi call failed and needs classifying. Also covers enterprise platform integration: wrapping CloudBase MCP into an organization-specific MCP (tool trimming, dangerous-action interception, per-user API Key distribution, audit) — use when the user mentions 企业接入 \u002F 封装 MCP \u002F 企业专属 MCP \u002F 多租户凭证下发 \u002F platform MCP wrapping. See recipes\u002Fenterprise-mcp-wrapper.md.","infometa\u002Fworkbuddyskills","infometa","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F109397516?v=4","01M79FS3XQK361MJFWQ2GFK95C","01M79FS3YPWKZYW9EPAAP2BFBJ",447,"MIT","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloud-api-operations\ndescription: \"Operate Tencent Cloud control-plane resources (monitoring\u002Falarms, CLB, CAM roles, COS, MySQL, SCF) via cloud APIs when no dedicated MCP tool covers the task. Use when a task needs control-plane operations beyond CloudBase's own tooling, or when a callCloudApi call failed and needs classifying. Also covers enterprise platform integration: wrapping CloudBase MCP into an organization-specific MCP (tool trimming, dangerous-action interception, per-user API Key distribution, audit) — use when the user mentions 企业接入 \u002F 封装 MCP \u002F 企业专属 MCP \u002F 多租户凭证下发 \u002F platform MCP wrapping. See recipes\u002Fenterprise-mcp-wrapper.md.\"\nversion: 2.36.2\nlicense: MIT\n---\n\n# Cloud API Operations\n\nOperate Tencent Cloud resources that CloudBase depends on but that no dedicated MCP tool covers (monitoring & alarms, CLB, CAM roles, cross-product infra). Two goals: **find the right API without guessing**, and **reuse proven workflows instead of re-exploring**.\n\n## Sibling skills (local only)\n\nSibling CloudBase skills ship beside this skill. Use local relative paths such as `..\u002Fcloudbase-platform\u002FSKILL.md`.\n\nIf a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do **not** HTTP-fetch remote skill or protocol markdown into the agent context.\n\n## When to use\n\n- The user asks to manage\u002Foperate Tencent Cloud resources beyond CloudBase's dedicated MCP tools (e.g. configure alarm policies, inspect CLB, attach CAM policies).\n- The user wants to control these resources from code and asks which API\u002FSDK to use.\n- A callCloudApi call failed and you need to classify the error (wrong Action \u002F wrong params \u002F missing CAM permission) and recover.\n\n## Workflow\n\n### 1. Discover the API — resolve names from a documented source\n\n1. **Read the API index first**: https:\u002F\u002Fdocs.cloudbase.net\u002Fai\u002Fcloudbase-ai-toolkit\u002Fapi-reference.md — auto-synced daily, action-level coverage (TCB 105 + dependency products: MySQL \u002F SCF \u002F COS). Check rate limits there too. The index check is a quick grep — run it in parallel with step 2\u002F3 fetches, do not serialize.\n2. If the index does not cover the target product, go to the product's official API docs (e.g. monitor: https:\u002F\u002Fcloud.tencent.com\u002Fdocument\u002Fproduct\u002F649\u002F30343) and confirm the exact Action name, Version, and parameters.\n3. For machine-readable parameter schema, fetch the official SDK models source directly — see `.\u002Freferences\u002Fcalling-methods.md` §2 item 4.\n\n**Done when**: the Action name, Version, and full parameter shape each trace to the index, official product docs, or SDK models source — nothing from memory. A call that still returns `action ... is invalid or not found` means a name was not resolved this way; classify and recover via the error table in `.\u002Freferences\u002Fcalling-methods.md` §1.\n\n> **API first：公开 API 概览就是契约边界。** 索引里查不到某个能力，它就不在公开契约内 —— 不要拿某个 SDK 的封装方法反推未公开的 Action 名去调（这类 Action 不受公开文档保护，非该语言的使用者也无从照做）。此时改用有公开 API 的等价路径，或把缺口明确告诉用户。本 skill 的 recipes 只收录公开 API 覆盖的场景。\n\n### 2. Choose the calling path\n\n| Scenario | Path | Reference |\n| --- | --- | --- |\n| Interactive ops inside this session | MCP `callCloudApi` | `.\u002Freferences\u002Fcalling-methods.md` §1 |\n| Picking the `service` identifier \u002F deciding whether `version` is needed | MCP `callCloudApi` | `.\u002Freferences\u002Fservice-versions.md` |\n| User's code \u002F scripts | Official SDKs (TC3-HMAC-SHA256) or `@cloudbase\u002Fmanager-node` | `.\u002Freferences\u002Fcalling-methods.md` §2 |\n| Quick one-off verification | API Explorer (https:\u002F\u002Fconsole.cloud.tencent.com\u002Fapi\u002Fexplorer) | — |\n\nPriority rule: if `@cloudbase\u002Fmanager-node` has a matching method, use it; drop to raw cloud API only when it does not.\n\n### 3. Check credentials before the first call\n\n**Three identities produce the same error text.** Before reading anything into an `UnauthorizedOperation`, find out which one you are holding:\n\n| Identity | How it is reached | CAM \u002F CloudAudit |\n| --- | --- | --- |\n| Account-level login (`federated-user\u002F\u003Cid>`) | Device-code \u002F web login, or account-level SecretId + Key | reachable, subject to that identity's CAM policies |\n| `TCB_QcsRole` service role | what CLI \u002F MCP **become** after calling a CloudBase product API | refused (`resource (...) has no permission`) |\n| Environment API Key (`\u003Cuin>:TCB-CAPI-Configured-idaas-apikey`) | `--cloudbase-api-key -e \u003CenvId>` | refused — the API Key model has no channel to attach arbitrary CAM policies |\n\nConfirm the identity with `sts GetCallerIdentity` (`--api-version 2018-08-13`) before concluding anything: the refusal text is identical across all three rows, so it cannot tell you which row you are in.\n\n**Order matters.** Calling a CloudBase product API swaps the identity to `TCB_QcsRole` for the rest of the session, so a CAM \u002F CloudAudit call issued *after* any product call is refused even though the login is account-level. Do the CAM \u002F audit work **first**.\n\n- Read the current credential scope from `auth` tools: `credential_scope: account` = account-level, reaches control-plane APIs subject to that identity's CAM policies; `env` = API Key, scoped to one environment's data plane plus the fixed TCB policies.\n- Permission comes from a different place per credential identity: the account-level identity's own policies, the API Key model (no channel to attach arbitrary CAM policies), or the TCB service role that CLI \u002F MCP assume. Which cross-product capabilities that role family already covers is not fixed — read the attached policies (`ListAttachedRolePolicies` + `GetPolicy`) instead of assuming, and treat `UnauthorizedOperation` as \"this identity lacks this action\", never as a broken setup.\n- On `UnauthorizedOperation` \u002F `AuthFailure`, hand the user a **one-click CAM grant link** (role name + policy name + `principal`) instead of telling them to go find the policy in the console, then retry the original call. Role targets, the `principal` values, and which preset policy covers what: `.\u002Freferences\u002Fcalling-methods.md` §3.\n\n**Done when**: the credential identity has been confirmed with `sts GetCallerIdentity` (not inferred from the error text), and every permission error has been converted into a clickable authorization link carrying a concrete policy name before any retry.\n\n### 4. Follow a proven recipe when one exists\n\nRecipes encode the exact call sequence, required parameters, and empirically discovered pitfalls so the flow works on the first pass. One scenario per file — start from the index `.\u002Freferences\u002Frecipes\u002FREADME.md`, whose 状态 column records how far each recipe has been verified:\n\n- **PostgreSQL storage-usage alarm**: `.\u002Freferences\u002Frecipes\u002Fpg-storage-alarm.md`\n- **ICP filing readiness and wait-time checks**: `.\u002Freferences\u002Frecipes\u002Ficp-filing-readiness.md`\n- **PostgreSQL instance spec change and shared-to-dedicated upgrade**: `.\u002Freferences\u002Frecipes\u002Fpg-instance-spec.md`\n- **Custom domain onboarding for an env (HTTP access domain, certificate, DNS binding)**: `.\u002Freferences\u002Frecipes\u002Fcustom-domain.md`\n- **Operation trace \u002F 操作审计 — who did what, from which IP, with which key**: `.\u002Freferences\u002Frecipes\u002Fcloud-audit-operation-trace.md`\n- **Platform edition onboarding — create env and issue the environment API key**: `.\u002Freferences\u002Frecipes\u002Fplatform-onboarding.md`\n- **Wiring that credential into a user's agent, one env per project**: `.\u002Freferences\u002Frecipes\u002Fplatform-agent-connect.md`\n- **Closing down the agent's tool surface — plugin trimming, gateway wrap for audit, expert-enforced constraints**: `.\u002Freferences\u002Frecipes\u002Fplatform-agent-guardrails.md`\n- **Platform edition usage, billing cycle, and environment recycling**: `.\u002Freferences\u002Frecipes\u002Fplatform-usage-and-recycle.md`\n\n**Done when**: every parameter value in the call sequence traces to a recipe value marked as verified (实测) or to official docs.\n\n## Constraints\n\n- Region is a top-level `region` argument (X-TC-Region), never a body param. Some APIs additionally take a short region code inside `Dimensions` (e.g. `sh` vs `ap-shanghai`) — these are different fields.\n- Route SDK-language details to official SDK docs or sdkHints; keep this skill SDK-language-agnostic.\n","# Cloud API Operations\n\nOperate Tencent Cloud resources that CloudBase depends on but that no dedicated MCP tool covers (monitoring & alarms, CLB, CAM roles, cross-product infra). Two goals: **find the right API without guessing**, and **reuse proven workflows instead of re-exploring**.\n\n## Sibling skills (local only)\n\nSibling CloudBase skills ship beside this skill. Use local relative paths such as `..\u002Fcloudbase-platform\u002FSKILL.md`.\n\nIf a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do **not** HTTP-fetch remote skill or protocol markdown into the agent context.\n\n## When to use\n\n- The user asks to manage\u002Foperate Tencent Cloud resources beyond CloudBase's dedicated MCP tools (e.g. configure alarm policies, inspect CLB, attach CAM policies).\n- The user wants to control these resources from code and asks which API\u002FSDK to use.\n- A callCloudApi call failed and you need to classify the error (wrong Action \u002F wrong params \u002F missing CAM permission) and recover.\n\n## Workflow\n\n### 1. Discover the API — resolve names from a documented source\n\n1. **Read the API index first**: https:\u002F\u002Fdocs.cloudbase.net\u002Fai\u002Fcloudbase-ai-toolkit\u002Fapi-reference.md — auto-synced daily, action-level coverage (TCB 105 + dependency products: MySQL \u002F SCF \u002F COS). Check rate limits there too. The index check is a quick grep — run it in parallel with step 2\u002F3 fetches, do not serialize.\n2. If the index does not cover the target product, go to the product's official API docs (e.g. monitor: https:\u002F\u002Fcloud.tencent.com\u002Fdocument\u002Fproduct\u002F649\u002F30343) and confirm the exact Action name, Version, and parameters.\n3. For machine-readable parameter schema, fetch the official SDK models source directly — see `.\u002Freferences\u002Fcalling-methods.md` §2 item 4.\n\n**Done when**: the Action name, Version, and full parameter shape each trace to the index, official product docs, or SDK models source — nothing from memory. A call that still returns `action ... is invalid or not found` means a name was not resolved this way; classify and recover via the error table in `.\u002Freferences\u002Fcalling-methods.md` §1.\n\n> **API first：公开 API 概览就是契约边界。** 索引里查不到某个能力，它就不在公开契约内 —— 不要拿某个 SDK 的封装方法反推未公开的 Action 名去调（这类 Action 不受公开文档保护，非该语言的使用者也无从照做）。此时改用有公开 API 的等价路径，或把缺口明确告诉用户。本 skill 的 recipes 只收录公开 API 覆盖的场景。\n\n### 2. Choose the calling path\n\n| Scenario | Path | Reference |\n| --- | --- | --- |\n| Interactive ops inside this session | MCP `callCloudApi` | `.\u002Freferences\u002Fcalling-methods.md` §1 |\n| Picking the `service` identifier \u002F deciding whether `version` is needed | MCP `callCloudApi` | `.\u002Freferences\u002Fservice-versions.md` |\n| User's code \u002F scripts | Official SDKs (TC3-HMAC-SHA256) or `@cloudbase\u002Fmanager-node` | `.\u002Freferences\u002Fcalling-methods.md` §2 |\n| Quick one-off verification | API Explorer (https:\u002F\u002Fconsole.cloud.tencent.com\u002Fapi\u002Fexplorer) | — |\n\nPriority rule: if `@cloudbase\u002Fmanager-node` has a matching method, use it; drop to raw cloud API only when it does not.\n\n### 3. Check credentials before the first call\n\n**Three identities produce the same error text.** Before reading anything into an `UnauthorizedOperation`, find out which one you are holding:\n\n| Identity | How it is reached | CAM \u002F CloudAudit |\n| --- | --- | --- |\n| Account-level login (`federated-user\u002F\u003Cid>`) | Device-code \u002F web login, or account-level SecretId + Key | reachable, subject to that identity's CAM policies |\n| `TCB_QcsRole` service role | what CLI \u002F MCP **become** after calling a CloudBase product API | refused (`resource (...) has no permission`) |\n| Environment API Key (`\u003Cuin>:TCB-CAPI-Configured-idaas-apikey`) | `--cloudbase-api-key -e \u003CenvId>` | refused — the API Key model has no channel to attach arbitrary CAM policies |\n\nConfirm the identity with `sts GetCallerIdentity` (`--api-version 2018-08-13`) before concluding anything: the refusal text is identical across all three rows, so it cannot tell you which row you are in.\n\n**Order matters.** Calling a CloudBase product API swaps the identity to `TCB_QcsRole` for the rest of the session, so a CAM \u002F CloudAudit call issued *after* any product call is refused even though the login is account-level. Do the CAM \u002F audit work **first**.\n\n- Read the current credential scope from `auth` tools: `credential_scope: account` = account-level, reaches control-plane APIs subject to that identity's CAM policies; `env` = API Key, scoped to one environment's data plane plus the fixed TCB policies.\n- Permission comes from a different place per credential identity: the account-level identity's own policies, the API Key model (no channel to attach arbitrary CAM policies), or the TCB service role that CLI \u002F MCP assume. Which cross-product capabilities that role family already covers is not fixed — read the attached policies (`ListAttachedRolePolicies` + `GetPolicy`) instead of assuming, and treat `UnauthorizedOperation` as \"this identity lacks this action\", never as a broken setup.\n- On `UnauthorizedOperation` \u002F `AuthFailure`, hand the user a **one-click CAM grant link** (role name + policy name + `principal`) instead of telling them to go find the policy in the console, then retry the original call. Role targets, the `principal` values, and which preset policy covers what: `.\u002Freferences\u002Fcalling-methods.md` §3.\n\n**Done when**: the credential identity has been confirmed with `sts GetCallerIdentity` (not inferred from the error text), and every permission error has been converted into a clickable authorization link carrying a concrete policy name before any retry.\n\n### 4. Follow a proven recipe when one exists\n\nRecipes encode the exact call sequence, required parameters, and empirically discovered pitfalls so the flow works on the first pass. One scenario per file — start from the index `.\u002Freferences\u002Frecipes\u002FREADME.md`, whose 状态 column records how far each recipe has been verified:\n\n- **PostgreSQL storage-usage alarm**: `.\u002Freferences\u002Frecipes\u002Fpg-storage-alarm.md`\n- **ICP filing readiness and wait-time checks**: `.\u002Freferences\u002Frecipes\u002Ficp-filing-readiness.md`\n- **PostgreSQL instance spec change and shared-to-dedicated upgrade**: `.\u002Freferences\u002Frecipes\u002Fpg-instance-spec.md`\n- **Custom domain onboarding for an env (HTTP access domain, certificate, DNS binding)**: `.\u002Freferences\u002Frecipes\u002Fcustom-domain.md`\n- **Operation trace \u002F 操作审计 — who did what, from which IP, with which key**: `.\u002Freferences\u002Frecipes\u002Fcloud-audit-operation-trace.md`\n- **Platform edition onboarding — create env and issue the environment API key**: `.\u002Freferences\u002Frecipes\u002Fplatform-onboarding.md`\n- **Wiring that credential into a user's agent, one env per project**: `.\u002Freferences\u002Frecipes\u002Fplatform-agent-connect.md`\n- **Closing down the agent's tool surface — plugin trimming, gateway wrap for audit, expert-enforced constraints**: `.\u002Freferences\u002Frecipes\u002Fplatform-agent-guardrails.md`\n- **Platform edition usage, billing cycle, and environment recycling**: `.\u002Freferences\u002Frecipes\u002Fplatform-usage-and-recycle.md`\n\n**Done when**: every parameter value in the call sequence traces to a recipe value marked as verified (实测) or to official docs.\n\n## Constraints\n\n- Region is a top-level `region` argument (X-TC-Region), never a body param. Some APIs additionally take a short region code inside `Dimensions` (e.g. `sh` vs `ap-shanghai`) — these are different fields.\n- Route SDK-language details to official SDK docs or sdkHints; keep this skill SDK-language-agnostic.\n",{"name":5,"license":14,"version":23,"description":7},"2.36.2","main","33b6151ccee9aa0816c6f32d021be77d82772755","connectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations",138,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills","https:\u002F\u002Fgithub.com\u002Finfometa","2026-11-11 03:15:35",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add infometa\u002Fworkbuddyskills --skill cloud-api-operations",{"tool":37,"command":38},"bunx","bunx skills add infometa\u002Fworkbuddyskills --skill cloud-api-operations",{"tool":40,"command":41},"pnpm","pnpm dlx skills add infometa\u002Fworkbuddyskills --skill cloud-api-operations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002FSKILL.md",true,[45,51,55,59,63,67,71,75,79,83,87,91,95,99,103,107],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fcalling-methods.md","REFERENCE","参考文档",14707,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Fcalling-methods.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Frecipes\u002Fbilling-charges-explained.md",4965,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fbilling-charges-explained.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Frecipes\u002Fcloud-audit-operation-trace.md",20177,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fcloud-audit-operation-trace.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Frecipes\u002Fcredits-exhaustion.md",6906,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fcredits-exhaustion.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Frecipes\u002Fcustom-domain.md",31051,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fcustom-domain.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Frecipes\u002Fenterprise-mcp-wrapper.md",11212,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fenterprise-mcp-wrapper.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Frecipes\u002Ficp-filing-readiness.md",15989,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Ficp-filing-readiness.md",{"path":76,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Frecipes\u002Fpg-instance-spec.md",31561,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fpg-instance-spec.md",{"path":80,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Frecipes\u002Fpg-monitor-data.md",4863,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fpg-monitor-data.md",{"path":84,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Frecipes\u002Fpg-storage-alarm.md",6724,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fpg-storage-alarm.md",{"path":88,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Frecipes\u002Fplatform-agent-connect.md",5976,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fplatform-agent-connect.md",{"path":92,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Frecipes\u002Fplatform-agent-guardrails.md",6451,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fplatform-agent-guardrails.md",{"path":96,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Frecipes\u002Fplatform-onboarding.md",5095,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fplatform-onboarding.md",{"path":100,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Frecipes\u002Fplatform-usage-and-recycle.md",5297,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002Fplatform-usage-and-recycle.md",{"path":104,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Frecipes\u002FREADME.md",7012,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Frecipes\u002FREADME.md",{"path":108,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fservice-versions.md",4967,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloud-api-operations\u002Freferences\u002Fservice-versions.md",[112,119,126,133,140,149],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M7A1EC013S1PBBTSH2PA2S7D","yingmi-skill","当用户需要查询基金、策略、公告、财经资讯，做资产配置、组合诊断、风险回测、现金流分析，或生成图表、PDF 时，优先使用本 Skill 获取真实数据与可执行能力。","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fyingmi-skill\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":18},"01M7A194T67P6NRVYK8KCTH3CH","web-access","所有联网操作必须通过此 skill 处理，包括：搜索、网页抓取、登录后操作、网络交互等。","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-access\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":18},"01M7A14FATMDD6FK8QAGXY5GVR","tencentmap-map-assistant","腾讯位置服务·地图助手 Skill，一句自然语言调用腾讯地图全套能力，无需开发者账号、开箱即用。提供 AI 旅游攻略、地点搜索（含评分\u002F人均\u002F营业时间）、关键词提示、路线规划（驾车\u002F步行\u002F公交\u002F骑行）、地址解析与逆解析、行政区划、IP 定位、距离计算、天气查询，并可将行程或多 POI 渲染成网页地图。涉及找地点、规划路线、旅游行程、查天气、坐标转换等出行场景时使用。","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Ftencentmap-map-assistant\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":18},"01M7A0SX4XW5053MZ2S921EDH2","skill-scanner","Scan any agent skill for security risks before you install or use it. Powered by Tencent Zhuque Lab A.I.G (AI-Infra-Guard). 100% local static analysis — no file contents or credentials leave your device. Compatible with CodeBuddy, Cursor, Windsurf, Claude Code, OpenClaw and more. Triggers on: 这个 skill 安全吗, skill 安全扫描, 检查 skill 安全, audit skill, scan skill, check skill safety, analyze skill, inspect skill, verify skill, skill security, skill supply chain. Do NOT trigger for general agent usage, full system health checks, project debugging, or normal development.","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-scanner\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":144,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":18},"01M7A0SQC2CZB3450G8471673M","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends agent capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":18},"01M7A0RHV7BKS7DFQF9X9QCCNN","shader-dev","Comprehensive GLSL shader techniques for creating stunning visual effects — ray marching, SDF modeling, fluid simulation, particle systems, procedural generation, lighting, post-processing, and more.","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fshader-dev\u002FSKILL.md",[],[]]