[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M735DTFJV00FN3K69EWAMR06":3,"skill-same:01M735DTFJV00FN3K69EWAMR06":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M735DTFJV00FN3K69EWAMR06","aoss-nextgen-provisioning",null,"Use when provisioning or deprovisioning OpenSearch Serverless collections, creating collection groups, setting up AOSS NextGen, or tearing down AOSS resources","antgroup\u002FAgent3Sigma-Canary","antgroup","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F37703784?v=4","01M7358T7C4N25D7PHG9RC6RV4","Ant Group","01M7358T7YBHP46FWXD1TXYJVV",41,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002F_skills_repository\u002Fopensearch-skills-2.0.0\u002Fcloud\u002Faws-setup\u002Faoss\u002Faoss-nextgen-provisioning\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: aoss-nextgen-provisioning\ndescription: Use when provisioning or deprovisioning OpenSearch Serverless collections, creating collection groups, setting up AOSS NextGen, or tearing down AOSS resources\n---\n\n# OpenSearch Serverless NextGen Provisioning & Deprovisioning\n\n## Overview\n\nGuided wizard for provisioning and deprovisioning Amazon OpenSearch Serverless (AOSS) NextGen collections. Handles the full orchestration: security policies, collection groups, and collections — in the correct dependency order.\n\n## When to Use\n\n- Customer wants to create an OpenSearch Serverless collection\n- Customer wants to set up AOSS NextGen\n- Customer wants to delete\u002Fdeprovision AOSS resources\n- Customer mentions \"collection group\", \"opensearch serverless\", \"AOSS\"\n\n## Key Constraints\n\n- `\"standbyReplicas\": \"ENABLED\"` is MANDATORY for all NextGen collection groups (never allow DISABLED)\n- `\"generation\": \"NEXTGEN\"` is REQUIRED for NextGen collection groups.\n- AWS credentials must be pre-configured; check first and stop if missing\n- Execute commands directly — do not generate scripts for the user to run\n- **Usage attribution (required):** Prefix every AWS CLI command you run in a shell with `AWS_SDK_UA_APP_ID=opensearch-agent-skills` (e.g. `AWS_SDK_UA_APP_ID=opensearch-agent-skills aws opensearchserverless ...`), regardless of service or subcommand. Scope it per-command — do not `export` it globally. This tags the call's User-Agent header so cloud requests from this skill are attributable.\n- Collections must be in ACTIVE status before they can be deleted. NextGen collections typically take ~30 seconds; standalone collections can take 3-5 minutes.\n- OCU capacity limits must be: 1, 2, 4, 8, 16, or any multiple of 16\n\n## Quick Reference\n\n| Action | Flow | What it creates |\n|--------|------|-----------------|\n| New NextGen collection (defaults) | Simple | enc policy + net policy + group + collection |\n| New NextGen collection (customized) | Advanced | enc policy + net policy + group (with limits) + collection |\n| New standalone collection (v1) | Standalone | enc policy + net policy + collection |\n| Add collection to existing group | Add to Group | collection (+ policies if needed) |\n| Delete resources | Deprovision | Removes collections → group → policies |\n\n### Naming Convention (Auto-Generated)\n\n| Resource | Name Pattern |\n|----------|-------------|\n| Collection | `\u003Cuser-provided-name>` |\n| Collection group | `\u003Cname>-group` |\n| Encryption policy | `\u003Cname>-enc-policy` |\n| Network policy | `\u003Cname>-net-policy` |\n| Data access policy | `\u003Cname>-access-policy` |\n\n## Companion Files\n\nThis skill is split across multiple files to stay under 500 lines. Read companion files on demand:\n- **If user selects Flow 2 (Advanced) or Flow 4 (Add to Existing Group):** Read `ADVANCED.md` in this directory.\n- **If user selects Flow 5 (Deprovision):** Read `DEPROVISION.md` in this directory.\n- **On any command failure:** Read `ERRORS.md` in this directory for error handling guidance.\n\n---\n\n## Entry Point\n\n### Step 1: Credential Check\n\nRun:\n```bash\naws sts get-caller-identity\n```\n\nIf this fails, tell the user: \"AWS credentials are missing or expired. Please configure credentials (e.g., `aws configure` or set environment variables) and try again.\" Then STOP.\n\n### Step 2: Mode Selection\n\nAsk the user:\n\n```\nWhat would you like to do?\n\n1. Provision (Simple) — New NextGen collection group + collection with defaults\n2. Provision (Advanced) — Preset-based setup with full parameter control\n3. Provision standalone collection — Collection without a collection group (classic)\n4. Add collection to existing group — Create a collection in an existing collection group\n5. Deprovision — Tear down collection(s) and\u002For collection group\n```\n\nProceed to the corresponding flow section below (or read companion file as noted above).\n\n---\n\n## Flow 1: Simple Provisioning\n\n### Inputs\n\nCollect from the user (one at a time):\n1. **Collection name** — 3-32 chars, lowercase letters, numbers, hyphens. Must start with a letter. Pattern: `[a-z][a-z0-9-]+`\n2. **Collection type** — SEARCH or VECTORSEARCH\n3. **Region** — AWS region (e.g., us-east-1, us-east-2, us-west-2)\n\n### Execution\n\nRun these commands in order. Stop and report if any command fails.\n\n**1. Create encryption policy:**\n```bash\naws opensearchserverless create-security-policy --cli-input-json '{\n  \"type\": \"encryption\",\n  \"name\": \"\u003Cname>-enc-policy\",\n  \"policy\": \"{\\\"Rules\\\":[{\\\"ResourceType\\\":\\\"collection\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]}],\\\"AWSOwnedKey\\\":true}\"\n}' --region \u003Cregion>\n```\n\n**2. Create network policy (public access):**\n```bash\naws opensearchserverless create-security-policy --cli-input-json '{\n  \"type\": \"network\",\n  \"name\": \"\u003Cname>-net-policy\",\n  \"policy\": \"[{\\\"Description\\\":\\\"Public access for \u003Cname>\\\",\\\"Rules\\\":[{\\\"ResourceType\\\":\\\"dashboard\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]},{\\\"ResourceType\\\":\\\"collection\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]}],\\\"AllowFromPublic\\\":true}]\"\n}' --region \u003Cregion>\n```\n\n**3. Create collection group (NextGen):**\n```bash\naws opensearchserverless create-collection-group \\\n  --name \u003Cname>-group \\\n  --standby-replicas ENABLED \\\n  --generation NEXTGEN \\\n  --region \u003Cregion>\n```\n\n**4. Create collection:**\n```bash\naws opensearchserverless create-collection --cli-input-json '{\n  \"name\": \"\u003Cname>\",\n  \"type\": \"\u003CTYPE>\",\n  \"collectionGroupName\": \"\u003Cname>-group\"\n}' --region \u003Cregion>\n```\n\n**5. Optional — Data access policy:**\n\nAsk: \"Would you like to set up a data access policy now? This grants an IAM principal access to the collection. You can also do this later.\"\n\nIf yes, collect the IAM principal ARN (role or user ARN), then run:\n```bash\naws opensearchserverless create-access-policy --cli-input-json '{\n  \"type\": \"data\",\n  \"name\": \"\u003Cname>-access-policy\",\n  \"policy\": \"[{\\\"Rules\\\":[{\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"],\\\"Permission\\\":[\\\"aoss:*\\\"],\\\"ResourceType\\\":\\\"collection\\\"},{\\\"Resource\\\":[\\\"index\u002F\u003Cname>\u002F*\\\"],\\\"Permission\\\":[\\\"aoss:*\\\"],\\\"ResourceType\\\":\\\"index\\\"},{\\\"Resource\\\":[\\\"model\u002F*\u002F*\\\"],\\\"Permission\\\":[\\\"aoss:*\\\"],\\\"ResourceType\\\":\\\"model\\\"},{\\\"Resource\\\":[\\\"agent\u002F*\u002F*\\\"],\\\"Permission\\\":[\\\"aoss:*\\\"],\\\"ResourceType\\\":\\\"agent\\\"}],\\\"Principal\\\":[\\\"\u003Cprincipal-arn>\\\"]}]\"\n}' --region \u003Cregion>\n```\n\n**Important:** The `model` and `agent` resource types are required for semantic enrichment (CreateIndex with `semantic_enrichment`) and for deploying ML models or agents on the collection. The `model\u002F*\u002F*` wildcard pattern is needed because semantic enrichment creates ML connectors at the account level, not scoped to a single collection name. Always include both `model` and `agent` rules.\n\n### Success Output\n\nAfter all commands succeed, report:\n- Collection group name and ID\n- Collection name, ID, and ARN (from create-collection response)\n- Region\n- Remind user: \"Your collection will be ACTIVE in 1-2 minutes. You can check status with: `aws opensearchserverless batch-get-collection --ids \u003Cid> --region \u003Cregion>`\"\n\n---\n\n## Flow 3: Standalone Collection (Classic)\n\nFor customers who want a collection without a collection group (v1-style, no NextGen features).\n\n### Inputs\n\nCollect from the user:\n1. **Collection name** — 3-32 chars, lowercase, alphanumeric + hyphens, starts with letter\n2. **Collection type** — SEARCH or VECTORSEARCH\n3. **Region** — AWS region\n\n### Execution\n\n**1. Create encryption policy:**\n```bash\naws opensearchserverless create-security-policy --cli-input-json '{\n  \"type\": \"encryption\",\n  \"name\": \"\u003Cname>-enc-policy\",\n  \"policy\": \"{\\\"Rules\\\":[{\\\"ResourceType\\\":\\\"collection\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]}],\\\"AWSOwnedKey\\\":true}\"\n}' --region \u003Cregion>\n```\n\n**2. Create network policy (public access):**\n```bash\naws opensearchserverless create-security-policy --cli-input-json '{\n  \"type\": \"network\",\n  \"name\": \"\u003Cname>-net-policy\",\n  \"policy\": \"[{\\\"Description\\\":\\\"Public access for \u003Cname>\\\",\\\"Rules\\\":[{\\\"ResourceType\\\":\\\"dashboard\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]},{\\\"ResourceType\\\":\\\"collection\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]}],\\\"AllowFromPublic\\\":true}]\"\n}' --region \u003Cregion>\n```\n\n**3. Create collection (no collection group):**\n```bash\naws opensearchserverless create-collection --cli-input-json '{\n  \"name\": \"\u003Cname>\",\n  \"type\": \"\u003CTYPE>\"\n}' --region \u003Cregion>\n```\n\n**4. Optional — Data access policy:**\n\nSame as Flow 1.\n\n### Success Output\n\nReport collection name, ID, ARN, region. Remind about status check command.\n","# OpenSearch Serverless NextGen Provisioning & Deprovisioning\n\n## Overview\n\nGuided wizard for provisioning and deprovisioning Amazon OpenSearch Serverless (AOSS) NextGen collections. Handles the full orchestration: security policies, collection groups, and collections — in the correct dependency order.\n\n## When to Use\n\n- Customer wants to create an OpenSearch Serverless collection\n- Customer wants to set up AOSS NextGen\n- Customer wants to delete\u002Fdeprovision AOSS resources\n- Customer mentions \"collection group\", \"opensearch serverless\", \"AOSS\"\n\n## Key Constraints\n\n- `\"standbyReplicas\": \"ENABLED\"` is MANDATORY for all NextGen collection groups (never allow DISABLED)\n- `\"generation\": \"NEXTGEN\"` is REQUIRED for NextGen collection groups.\n- AWS credentials must be pre-configured; check first and stop if missing\n- Execute commands directly — do not generate scripts for the user to run\n- **Usage attribution (required):** Prefix every AWS CLI command you run in a shell with `AWS_SDK_UA_APP_ID=opensearch-agent-skills` (e.g. `AWS_SDK_UA_APP_ID=opensearch-agent-skills aws opensearchserverless ...`), regardless of service or subcommand. Scope it per-command — do not `export` it globally. This tags the call's User-Agent header so cloud requests from this skill are attributable.\n- Collections must be in ACTIVE status before they can be deleted. NextGen collections typically take ~30 seconds; standalone collections can take 3-5 minutes.\n- OCU capacity limits must be: 1, 2, 4, 8, 16, or any multiple of 16\n\n## Quick Reference\n\n| Action | Flow | What it creates |\n|--------|------|-----------------|\n| New NextGen collection (defaults) | Simple | enc policy + net policy + group + collection |\n| New NextGen collection (customized) | Advanced | enc policy + net policy + group (with limits) + collection |\n| New standalone collection (v1) | Standalone | enc policy + net policy + collection |\n| Add collection to existing group | Add to Group | collection (+ policies if needed) |\n| Delete resources | Deprovision | Removes collections → group → policies |\n\n### Naming Convention (Auto-Generated)\n\n| Resource | Name Pattern |\n|----------|-------------|\n| Collection | `\u003Cuser-provided-name>` |\n| Collection group | `\u003Cname>-group` |\n| Encryption policy | `\u003Cname>-enc-policy` |\n| Network policy | `\u003Cname>-net-policy` |\n| Data access policy | `\u003Cname>-access-policy` |\n\n## Companion Files\n\nThis skill is split across multiple files to stay under 500 lines. Read companion files on demand:\n- **If user selects Flow 2 (Advanced) or Flow 4 (Add to Existing Group):** Read `ADVANCED.md` in this directory.\n- **If user selects Flow 5 (Deprovision):** Read `DEPROVISION.md` in this directory.\n- **On any command failure:** Read `ERRORS.md` in this directory for error handling guidance.\n\n---\n\n## Entry Point\n\n### Step 1: Credential Check\n\nRun:\n```bash\naws sts get-caller-identity\n```\n\nIf this fails, tell the user: \"AWS credentials are missing or expired. Please configure credentials (e.g., `aws configure` or set environment variables) and try again.\" Then STOP.\n\n### Step 2: Mode Selection\n\nAsk the user:\n\n```\nWhat would you like to do?\n\n1. Provision (Simple) — New NextGen collection group + collection with defaults\n2. Provision (Advanced) — Preset-based setup with full parameter control\n3. Provision standalone collection — Collection without a collection group (classic)\n4. Add collection to existing group — Create a collection in an existing collection group\n5. Deprovision — Tear down collection(s) and\u002For collection group\n```\n\nProceed to the corresponding flow section below (or read companion file as noted above).\n\n---\n\n## Flow 1: Simple Provisioning\n\n### Inputs\n\nCollect from the user (one at a time):\n1. **Collection name** — 3-32 chars, lowercase letters, numbers, hyphens. Must start with a letter. Pattern: `[a-z][a-z0-9-]+`\n2. **Collection type** — SEARCH or VECTORSEARCH\n3. **Region** — AWS region (e.g., us-east-1, us-east-2, us-west-2)\n\n### Execution\n\nRun these commands in order. Stop and report if any command fails.\n\n**1. Create encryption policy:**\n```bash\naws opensearchserverless create-security-policy --cli-input-json '{\n  \"type\": \"encryption\",\n  \"name\": \"\u003Cname>-enc-policy\",\n  \"policy\": \"{\\\"Rules\\\":[{\\\"ResourceType\\\":\\\"collection\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]}],\\\"AWSOwnedKey\\\":true}\"\n}' --region \u003Cregion>\n```\n\n**2. Create network policy (public access):**\n```bash\naws opensearchserverless create-security-policy --cli-input-json '{\n  \"type\": \"network\",\n  \"name\": \"\u003Cname>-net-policy\",\n  \"policy\": \"[{\\\"Description\\\":\\\"Public access for \u003Cname>\\\",\\\"Rules\\\":[{\\\"ResourceType\\\":\\\"dashboard\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]},{\\\"ResourceType\\\":\\\"collection\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]}],\\\"AllowFromPublic\\\":true}]\"\n}' --region \u003Cregion>\n```\n\n**3. Create collection group (NextGen):**\n```bash\naws opensearchserverless create-collection-group \\\n  --name \u003Cname>-group \\\n  --standby-replicas ENABLED \\\n  --generation NEXTGEN \\\n  --region \u003Cregion>\n```\n\n**4. Create collection:**\n```bash\naws opensearchserverless create-collection --cli-input-json '{\n  \"name\": \"\u003Cname>\",\n  \"type\": \"\u003CTYPE>\",\n  \"collectionGroupName\": \"\u003Cname>-group\"\n}' --region \u003Cregion>\n```\n\n**5. Optional — Data access policy:**\n\nAsk: \"Would you like to set up a data access policy now? This grants an IAM principal access to the collection. You can also do this later.\"\n\nIf yes, collect the IAM principal ARN (role or user ARN), then run:\n```bash\naws opensearchserverless create-access-policy --cli-input-json '{\n  \"type\": \"data\",\n  \"name\": \"\u003Cname>-access-policy\",\n  \"policy\": \"[{\\\"Rules\\\":[{\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"],\\\"Permission\\\":[\\\"aoss:*\\\"],\\\"ResourceType\\\":\\\"collection\\\"},{\\\"Resource\\\":[\\\"index\u002F\u003Cname>\u002F*\\\"],\\\"Permission\\\":[\\\"aoss:*\\\"],\\\"ResourceType\\\":\\\"index\\\"},{\\\"Resource\\\":[\\\"model\u002F*\u002F*\\\"],\\\"Permission\\\":[\\\"aoss:*\\\"],\\\"ResourceType\\\":\\\"model\\\"},{\\\"Resource\\\":[\\\"agent\u002F*\u002F*\\\"],\\\"Permission\\\":[\\\"aoss:*\\\"],\\\"ResourceType\\\":\\\"agent\\\"}],\\\"Principal\\\":[\\\"\u003Cprincipal-arn>\\\"]}]\"\n}' --region \u003Cregion>\n```\n\n**Important:** The `model` and `agent` resource types are required for semantic enrichment (CreateIndex with `semantic_enrichment`) and for deploying ML models or agents on the collection. The `model\u002F*\u002F*` wildcard pattern is needed because semantic enrichment creates ML connectors at the account level, not scoped to a single collection name. Always include both `model` and `agent` rules.\n\n### Success Output\n\nAfter all commands succeed, report:\n- Collection group name and ID\n- Collection name, ID, and ARN (from create-collection response)\n- Region\n- Remind user: \"Your collection will be ACTIVE in 1-2 minutes. You can check status with: `aws opensearchserverless batch-get-collection --ids \u003Cid> --region \u003Cregion>`\"\n\n---\n\n## Flow 3: Standalone Collection (Classic)\n\nFor customers who want a collection without a collection group (v1-style, no NextGen features).\n\n### Inputs\n\nCollect from the user:\n1. **Collection name** — 3-32 chars, lowercase, alphanumeric + hyphens, starts with letter\n2. **Collection type** — SEARCH or VECTORSEARCH\n3. **Region** — AWS region\n\n### Execution\n\n**1. Create encryption policy:**\n```bash\naws opensearchserverless create-security-policy --cli-input-json '{\n  \"type\": \"encryption\",\n  \"name\": \"\u003Cname>-enc-policy\",\n  \"policy\": \"{\\\"Rules\\\":[{\\\"ResourceType\\\":\\\"collection\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]}],\\\"AWSOwnedKey\\\":true}\"\n}' --region \u003Cregion>\n```\n\n**2. Create network policy (public access):**\n```bash\naws opensearchserverless create-security-policy --cli-input-json '{\n  \"type\": \"network\",\n  \"name\": \"\u003Cname>-net-policy\",\n  \"policy\": \"[{\\\"Description\\\":\\\"Public access for \u003Cname>\\\",\\\"Rules\\\":[{\\\"ResourceType\\\":\\\"dashboard\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]},{\\\"ResourceType\\\":\\\"collection\\\",\\\"Resource\\\":[\\\"collection\u002F\u003Cname>\\\"]}],\\\"AllowFromPublic\\\":true}]\"\n}' --region \u003Cregion>\n```\n\n**3. Create collection (no collection group):**\n```bash\naws opensearchserverless create-collection --cli-input-json '{\n  \"name\": \"\u003Cname>\",\n  \"type\": \"\u003CTYPE>\"\n}' --region \u003Cregion>\n```\n\n**4. Optional — Data access policy:**\n\nSame as Flow 1.\n\n### Success Output\n\nReport collection name, ID, ARN, region. Remind about status check command.\n",{"name":5,"description":7},"master","a03a36613feab18689d22b19243d8787d65f341d","_skills_repository\u002Fopensearch-skills-2.0.0\u002Fcloud\u002Faws-setup\u002Faoss\u002Faoss-nextgen-provisioning",9,"https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary","https:\u002F\u002Fgithub.com\u002Fantgroup","https:\u002F\u002Fwww.antgroup.com","Make it easy to do business anywhere.","2026-11-10 20:47:51",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add antgroup\u002FAgent3Sigma-Canary --skill aoss-nextgen-provisioning",{"tool":39,"command":40},"bunx","bunx skills add antgroup\u002FAgent3Sigma-Canary --skill aoss-nextgen-provisioning",{"tool":42,"command":43},"pnpm","pnpm dlx skills add antgroup\u002FAgent3Sigma-Canary --skill aoss-nextgen-provisioning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002F_skills_repository\u002Fopensearch-skills-2.0.0\u002Fcloud\u002Faws-setup\u002Faoss\u002Faoss-nextgen-provisioning\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"ADVANCED.md","REFERENCE","参考文档",6260,"https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002F_skills_repository\u002Fopensearch-skills-2.0.0\u002Fcloud\u002Faws-setup\u002Faoss\u002Faoss-nextgen-provisioning\u002FADVANCED.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"DEPROVISION.md",2929,"https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002F_skills_repository\u002Fopensearch-skills-2.0.0\u002Fcloud\u002Faws-setup\u002Faoss\u002Faoss-nextgen-provisioning\u002FDEPROVISION.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"ERRORS.md",2519,"https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002F_skills_repository\u002Fopensearch-skills-2.0.0\u002Fcloud\u002Faws-setup\u002Faoss\u002Faoss-nextgen-provisioning\u002FERRORS.md",[62,69,77,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M735XWMBXNWE3SNHEF6N6J1A","secureclaw","Security skill for OpenClaw agents (7-framework aligned). 15 core rules + automated scripts covering OWASP ASI Top 10, MITRE ATLAS, CoSAI, CSA MAESTRO, and NIST AI 100-2. Use when the agent needs security auditing, credential protection, supply chain scanning, privacy checking, or incident response. By Adversa AI (https:\u002F\u002Fadversa.ai). v2.2.0.","https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002Fthird_party\u002Fsecureclaw\u002Fsecureclaw\u002Fskill\u002FSKILL.md",[],[],{"skillNo":70,"name":64,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M735XTK02KMFXPQ2PFKD6EJZ","Security hardening toolkit for OpenClaw. Run audits, apply fixes, scan skills, monitor costs and memory integrity.","MIT","https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002Fthird_party\u002Fsecureclaw\u002Fsecureclaw\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002Fthird_party\u002Fsecureclaw\u002Fsecureclaw\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M735XS8TZWBS9B2DJG6QFT4C","unsafe-skill","https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002Fthird_party\u002FClawKeeper\u002Fclawkeeper-plugin\u002Fexamples\u002Funsafe-skill\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M735XHV07HYJNN03PQZMRVH9","skill-to-sandbox","Guide a coding agent in converting real ClawHub skills into AgentCanary-compatible sandbox skills. Provides Type A assembly helpers, Type B\u002FC design templates, agent-visible-content audit, structural smoke checks, and end-to-end usability tasks. Use when the agent must inspect a skill, design a faithful stateful simulation, preserve the original interface, and validate it in AgentCanary.","https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002Fskill-to-sandbox\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M735XEKBEPMS4D5HW8T1ZH69","ssh-keygen-helper","Simplifies SSH key generation and management for developers.\nAutomatically configures SSH keys for GitHub, GitLab, and Bitbucket.\n\nUse when: ssh key, generate ssh, ssh setup, git authentication","https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002Fassets\u002Fsystem_trajectory_demo\u002Fssh-keygen-helper-time-based\u002FSKILL.md",[],[],{"skillNo":98,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M735XCQ8DG0XCKFM97QCWKS9","https:\u002F\u002Fgithub.com\u002Fantgroup\u002FAgent3Sigma-Canary\u002Fblob\u002Fmaster\u002Fassets\u002Fsystem_trajectory_demo\u002Fssh-keygen-helper-file-based\u002FSKILL.md",[],[]]