[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADK4948PPN482TJ06GAMMT":3,"skill-same:01M6ADK4948PPN482TJ06GAMMT":96},{"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":28,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6ADK4948PPN482TJ06GAMMT","foundry-agent-sync",null,"Create and synchronize prompt-based AI agents directly within Azure AI Foundry via REST API, from a local JSON manifest. Unlike scaffolding skills that only generate local code, this skill registers agents in the Foundry service itself — making them immediately available for invocation. Use when the user asks to create agents in Foundry, sync, deploy, register, or push agents to Foundry, update agent instructions, or scaffold the manifest and sync script for a new repository. Triggers: 'create agent in foundry', 'sync foundry agents', 'deploy agents to foundry', 'register agents in foundry', 'push agents', 'create foundry agent manifest', 'scaffold agent sync'.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Ffoundry-agent-sync\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"foundry","sync","agent sync","foundry agent sync","new","ai agents","when","agent instructions","local","scaffolding","update agent instructions","update agent","only","api","repository","push","azure ai foundry","code","update","generate","create","azure","scaffold","deploy","azure ai","create agent","2026-11-10 10:12:30",false,"---\nname: foundry-agent-sync\ndescription: \"Create and synchronize prompt-based AI agents directly within Azure AI Foundry via REST API, from a local JSON manifest. Unlike scaffolding skills that only generate local code, this skill registers agents in the Foundry service itself — making them immediately available for invocation. Use when the user asks to create agents in Foundry, sync, deploy, register, or push agents to Foundry, update agent instructions, or scaffold the manifest and sync script for a new repository. Triggers: 'create agent in foundry', 'sync foundry agents', 'deploy agents to foundry', 'register agents in foundry', 'push agents', 'create foundry agent manifest', 'scaffold agent sync'.\"\n---\n\n# Foundry Agent Sync\n\n## Overview\n\nCreate and synchronize prompt-based AI agents directly within Azure AI Foundry via the Agent Service REST API. This skill registers agents in the Foundry service itself — making them immediately available for invocation, evaluation, and management through the Foundry portal or API. Each agent is created or updated idempotently via a named POST call, using definitions from a local JSON manifest file.\n\n> **Key distinction:** This skill creates agents inside AI Foundry (server-side). It does not scaffold local agent code or container images — for that, use the `microsoft-foundry` skill's `create` sub-skill.\n\n## Prerequisites\n\nThe user must have:\n\n1. An Azure AI Foundry project with a deployed model (e.g. `gpt-5-4`)\n2. Azure CLI (`az`) authenticated with access to the Foundry project\n3. The **Azure AI User** role (or higher) on the Foundry project resource\n\nCollect these values before proceeding:\n\n| Value | How to get it |\n|---|---|\n| **Foundry project endpoint** | Azure Portal → AI Foundry project → Overview → Endpoint, or `az resource show` |\n| **Subscription ID** | `az account show --query id -o tsv` |\n| **Model deployment name** | The model name deployed in the Foundry project (e.g. `gpt-5-4`) |\n\n## Manifest Format\n\nThe manifest is a JSON array where each entry defines one agent. Look for it at common paths: `infra\u002Ffoundry-agents.json`, `foundry-agents.json`, or `.foundry\u002Fagents.json`. If none exists, scaffold one.\n\n```json\n[\n  {\n    \"useCaseId\": \"alert-triage\",\n    \"description\": \"Short description of what this agent does.\",\n    \"baseInstruction\": \"You are an assistant that... \u003Csystem prompt for the agent>\"\n  }\n]\n```\n\n### Field Reference\n\n| Field | Required | Description |\n|---|---|---|\n| `useCaseId` | Yes | Kebab-case identifier; used to build the agent name (`{prefix}-{useCaseId}`) |\n| `description` | Yes | Human-readable description stored as agent metadata |\n| `baseInstruction` | Yes | System prompt \u002F base instructions for the agent |\n\n## Sync Script\n\n### PowerShell (interactive \u002F CI)\n\nCreate or locate the sync script. The canonical path is `infra\u002Fscripts\u002Fsync-foundry-agents.ps1` but adapt to the repo layout.\n\n```powershell\nparam(\n  [Parameter(Mandatory)]\n  [string]$SubscriptionId,\n\n  [Parameter(Mandatory)]\n  [string]$ProjectEndpoint,\n\n  [string]$ManifestPath = (Join-Path $PSScriptRoot '..\\foundry-agents.json'),\n  [string]$ModelName = 'gpt-5-4',\n  [string]$AgentNamePrefix = 'myproject',\n  [string]$ApiVersion = '2025-11-15-preview'\n)\n\n$ErrorActionPreference = 'Stop'\n\n# Optional: append a common instruction suffix to every agent\n$commonSuffix = ''\n\naz account set --subscription $SubscriptionId | Out-Null\n$accessToken = az account get-access-token --resource https:\u002F\u002Fai.azure.com\u002F --query accessToken -o tsv\nif (-not $accessToken) { throw 'Failed to acquire Foundry access token.' }\n\n$definitions = Get-Content -Raw -Path $ManifestPath | ConvertFrom-Json\n$headers = @{ Authorization = \"Bearer $accessToken\" }\n$results = @()\n\nforeach ($def in $definitions) {\n  $agentName = \"$AgentNamePrefix-$($def.useCaseId)\"\n  $instructions = if ($commonSuffix) { \"$($def.baseInstruction)`n`n$commonSuffix\" } else { $def.baseInstruction }\n  $body = @{\n    definition  = @{ kind = 'prompt'; model = $ModelName; instructions = $instructions }\n    description = $def.description\n    metadata    = @{ useCaseId = $def.useCaseId; managedBy = 'foundry-agent-sync' }\n  } | ConvertTo-Json -Depth 8\n\n  $uri = \"$($ProjectEndpoint.TrimEnd('\u002F'))\u002Fagents\u002F$agentName`?api-version=$ApiVersion\"\n  $resp = Invoke-RestMethod -Method Post -Uri $uri -Headers $headers -ContentType 'application\u002Fjson' -Body $body\n  $version = $resp.version ?? $resp.latest_version ?? $resp.id ?? 'unknown'\n  Write-Host \"Synced $agentName ($version)\"\n  $results += [pscustomobject]@{ name = $agentName; version = $version }\n}\n\n$results | Format-Table -AutoSize\n```\n\n### Bash (Bicep deployment script \u002F CI)\n\nFor automated deployment via `Microsoft.Resources\u002FdeploymentScripts`, use a bash script that:\n\n1. Authenticates with a managed identity: `az login --identity --username \"$CLIENT_ID\"`\n2. Acquires a Foundry token: `az account get-access-token --resource https:\u002F\u002Fai.azure.com\u002F`\n3. Iterates definitions from the `FOUNDRY_AGENT_DEFINITIONS` environment variable (JSON string)\n4. POSTs each agent to `{endpoint}\u002Fagents\u002F{name}?api-version=2025-11-15-preview`\n\n## Bicep Integration (optional)\n\nTo run the sync automatically during infrastructure deployment:\n\n1. **Load the manifest** at compile time:\n   ```bicep\n   var agentDefinitions = loadJsonContent('foundry-agents.json')\n   ```\n\n2. **Create a User-Assigned Managed Identity** with the **Azure AI User** role on the Foundry project.\n\n3. **Create a `Microsoft.Resources\u002FdeploymentScripts`** resource (kind `AzureCLI`) that:\n   - Uses the managed identity\n   - Loads the bash sync script via `loadTextContent`\n   - Passes the project endpoint, definitions, and model as environment variables\n\nGate behind a `deployFoundryAgents` parameter so teams can opt in\u002Fout.\n\n## Workflow\n\n### Step 1 — Locate or scaffold the manifest\n\nSearch the repo for `foundry-agents.json`. If it doesn't exist, ask the user what agents they need and create the manifest.\n\n### Step 2 — Locate or scaffold the sync script\n\nSearch for `sync-foundry-agents.ps1` or `foundry-agent-sync.sh`. If missing, create the PowerShell script using the template above, adapting:\n- `$AgentNamePrefix` to match the project name\n- `$ModelName` to the user's deployed model\n- `$ManifestPath` to the actual manifest location\n\n### Step 3 — Collect parameters\n\nAsk the user for:\n- Foundry project endpoint\n- Subscription ID\n- Model deployment name (default: `gpt-5-4`)\n- Agent name prefix (default: repo name in kebab-case)\n\n### Step 4 — Run the sync\n\nExecute the PowerShell script with the collected parameters:\n\n```powershell\n.\\infra\\scripts\\sync-foundry-agents.ps1 `\n  -SubscriptionId '\u003Csub-id>' `\n  -ProjectEndpoint '\u003Cendpoint>' `\n  -ModelName '\u003Cmodel>' `\n  -AgentNamePrefix '\u003Cprefix>'\n```\n\n### Step 5 — Verify\n\nConfirm synced agents by listing them:\n\n```powershell\n$token = az account get-access-token --resource https:\u002F\u002Fai.azure.com\u002F --query accessToken -o tsv\n$endpoint = '\u003Cproject-endpoint>'\nInvoke-RestMethod -Uri \"$endpoint\u002Fagents?api-version=2025-11-15-preview\" `\n  -Headers @{ Authorization = \"Bearer $token\" }\n```\n\n## REST API Reference\n\n| Operation | Method | URL |\n|---|---|---|\n| Create\u002Fupdate agent | POST | `{projectEndpoint}\u002Fagents\u002F{agentName}?api-version=2025-11-15-preview` |\n| List agents | GET | `{projectEndpoint}\u002Fagents?api-version=2025-11-15-preview` |\n| Get agent | GET | `{projectEndpoint}\u002Fagents\u002F{agentName}?api-version=2025-11-15-preview` |\n| Delete agent | DELETE | `{projectEndpoint}\u002Fagents\u002F{agentName}?api-version=2025-11-15-preview` |\n\n### Create\u002FUpdate Payload\n\n```json\n{\n  \"definition\": {\n    \"kind\": \"prompt\",\n    \"model\": \"\u003Cdeployed-model-name>\",\n    \"instructions\": \"\u003Csystem prompt>\"\n  },\n  \"description\": \"\u003Cagent description>\",\n  \"metadata\": {\n    \"useCaseId\": \"\u003Cuse-case-id>\",\n    \"managedBy\": \"foundry-agent-sync\"\n  }\n}\n```\n\n## Troubleshooting\n\n| Symptom | Cause | Fix |\n|---|---|---|\n| `401 Unauthorized` | Token expired or wrong audience | Re-run `az account get-access-token --resource https:\u002F\u002Fai.azure.com\u002F` |\n| `403 Forbidden` | Missing Azure AI User role | Assign the role on the Foundry project scope |\n| `404 Not Found` | Wrong project endpoint | Verify endpoint includes `\u002Fapi\u002Fprojects\u002F{projectName}` |\n| Model not found | Model not deployed in project | Deploy the model in AI Foundry portal first |\n| Empty definitions | Manifest path wrong | Check `-ManifestPath` points to the JSON file |\n","# Foundry Agent Sync\n\n## Overview\n\nCreate and synchronize prompt-based AI agents directly within Azure AI Foundry via the Agent Service REST API. This skill registers agents in the Foundry service itself — making them immediately available for invocation, evaluation, and management through the Foundry portal or API. Each agent is created or updated idempotently via a named POST call, using definitions from a local JSON manifest file.\n\n> **Key distinction:** This skill creates agents inside AI Foundry (server-side). It does not scaffold local agent code or container images — for that, use the `microsoft-foundry` skill's `create` sub-skill.\n\n## Prerequisites\n\nThe user must have:\n\n1. An Azure AI Foundry project with a deployed model (e.g. `gpt-5-4`)\n2. Azure CLI (`az`) authenticated with access to the Foundry project\n3. The **Azure AI User** role (or higher) on the Foundry project resource\n\nCollect these values before proceeding:\n\n| Value | How to get it |\n|---|---|\n| **Foundry project endpoint** | Azure Portal → AI Foundry project → Overview → Endpoint, or `az resource show` |\n| **Subscription ID** | `az account show --query id -o tsv` |\n| **Model deployment name** | The model name deployed in the Foundry project (e.g. `gpt-5-4`) |\n\n## Manifest Format\n\nThe manifest is a JSON array where each entry defines one agent. Look for it at common paths: `infra\u002Ffoundry-agents.json`, `foundry-agents.json`, or `.foundry\u002Fagents.json`. If none exists, scaffold one.\n\n```json\n[\n  {\n    \"useCaseId\": \"alert-triage\",\n    \"description\": \"Short description of what this agent does.\",\n    \"baseInstruction\": \"You are an assistant that... \u003Csystem prompt for the agent>\"\n  }\n]\n```\n\n### Field Reference\n\n| Field | Required | Description |\n|---|---|---|\n| `useCaseId` | Yes | Kebab-case identifier; used to build the agent name (`{prefix}-{useCaseId}`) |\n| `description` | Yes | Human-readable description stored as agent metadata |\n| `baseInstruction` | Yes | System prompt \u002F base instructions for the agent |\n\n## Sync Script\n\n### PowerShell (interactive \u002F CI)\n\nCreate or locate the sync script. The canonical path is `infra\u002Fscripts\u002Fsync-foundry-agents.ps1` but adapt to the repo layout.\n\n```powershell\nparam(\n  [Parameter(Mandatory)]\n  [string]$SubscriptionId,\n\n  [Parameter(Mandatory)]\n  [string]$ProjectEndpoint,\n\n  [string]$ManifestPath = (Join-Path $PSScriptRoot '..\\foundry-agents.json'),\n  [string]$ModelName = 'gpt-5-4',\n  [string]$AgentNamePrefix = 'myproject',\n  [string]$ApiVersion = '2025-11-15-preview'\n)\n\n$ErrorActionPreference = 'Stop'\n\n# Optional: append a common instruction suffix to every agent\n$commonSuffix = ''\n\naz account set --subscription $SubscriptionId | Out-Null\n$accessToken = az account get-access-token --resource https:\u002F\u002Fai.azure.com\u002F --query accessToken -o tsv\nif (-not $accessToken) { throw 'Failed to acquire Foundry access token.' }\n\n$definitions = Get-Content -Raw -Path $ManifestPath | ConvertFrom-Json\n$headers = @{ Authorization = \"Bearer $accessToken\" }\n$results = @()\n\nforeach ($def in $definitions) {\n  $agentName = \"$AgentNamePrefix-$($def.useCaseId)\"\n  $instructions = if ($commonSuffix) { \"$($def.baseInstruction)`n`n$commonSuffix\" } else { $def.baseInstruction }\n  $body = @{\n    definition  = @{ kind = 'prompt'; model = $ModelName; instructions = $instructions }\n    description = $def.description\n    metadata    = @{ useCaseId = $def.useCaseId; managedBy = 'foundry-agent-sync' }\n  } | ConvertTo-Json -Depth 8\n\n  $uri = \"$($ProjectEndpoint.TrimEnd('\u002F'))\u002Fagents\u002F$agentName`?api-version=$ApiVersion\"\n  $resp = Invoke-RestMethod -Method Post -Uri $uri -Headers $headers -ContentType 'application\u002Fjson' -Body $body\n  $version = $resp.version ?? $resp.latest_version ?? $resp.id ?? 'unknown'\n  Write-Host \"Synced $agentName ($version)\"\n  $results += [pscustomobject]@{ name = $agentName; version = $version }\n}\n\n$results | Format-Table -AutoSize\n```\n\n### Bash (Bicep deployment script \u002F CI)\n\nFor automated deployment via `Microsoft.Resources\u002FdeploymentScripts`, use a bash script that:\n\n1. Authenticates with a managed identity: `az login --identity --username \"$CLIENT_ID\"`\n2. Acquires a Foundry token: `az account get-access-token --resource https:\u002F\u002Fai.azure.com\u002F`\n3. Iterates definitions from the `FOUNDRY_AGENT_DEFINITIONS` environment variable (JSON string)\n4. POSTs each agent to `{endpoint}\u002Fagents\u002F{name}?api-version=2025-11-15-preview`\n\n## Bicep Integration (optional)\n\nTo run the sync automatically during infrastructure deployment:\n\n1. **Load the manifest** at compile time:\n   ```bicep\n   var agentDefinitions = loadJsonContent('foundry-agents.json')\n   ```\n\n2. **Create a User-Assigned Managed Identity** with the **Azure AI User** role on the Foundry project.\n\n3. **Create a `Microsoft.Resources\u002FdeploymentScripts`** resource (kind `AzureCLI`) that:\n   - Uses the managed identity\n   - Loads the bash sync script via `loadTextContent`\n   - Passes the project endpoint, definitions, and model as environment variables\n\nGate behind a `deployFoundryAgents` parameter so teams can opt in\u002Fout.\n\n## Workflow\n\n### Step 1 — Locate or scaffold the manifest\n\nSearch the repo for `foundry-agents.json`. If it doesn't exist, ask the user what agents they need and create the manifest.\n\n### Step 2 — Locate or scaffold the sync script\n\nSearch for `sync-foundry-agents.ps1` or `foundry-agent-sync.sh`. If missing, create the PowerShell script using the template above, adapting:\n- `$AgentNamePrefix` to match the project name\n- `$ModelName` to the user's deployed model\n- `$ManifestPath` to the actual manifest location\n\n### Step 3 — Collect parameters\n\nAsk the user for:\n- Foundry project endpoint\n- Subscription ID\n- Model deployment name (default: `gpt-5-4`)\n- Agent name prefix (default: repo name in kebab-case)\n\n### Step 4 — Run the sync\n\nExecute the PowerShell script with the collected parameters:\n\n```powershell\n.\\infra\\scripts\\sync-foundry-agents.ps1 `\n  -SubscriptionId '\u003Csub-id>' `\n  -ProjectEndpoint '\u003Cendpoint>' `\n  -ModelName '\u003Cmodel>' `\n  -AgentNamePrefix '\u003Cprefix>'\n```\n\n### Step 5 — Verify\n\nConfirm synced agents by listing them:\n\n```powershell\n$token = az account get-access-token --resource https:\u002F\u002Fai.azure.com\u002F --query accessToken -o tsv\n$endpoint = '\u003Cproject-endpoint>'\nInvoke-RestMethod -Uri \"$endpoint\u002Fagents?api-version=2025-11-15-preview\" `\n  -Headers @{ Authorization = \"Bearer $token\" }\n```\n\n## REST API Reference\n\n| Operation | Method | URL |\n|---|---|---|\n| Create\u002Fupdate agent | POST | `{projectEndpoint}\u002Fagents\u002F{agentName}?api-version=2025-11-15-preview` |\n| List agents | GET | `{projectEndpoint}\u002Fagents?api-version=2025-11-15-preview` |\n| Get agent | GET | `{projectEndpoint}\u002Fagents\u002F{agentName}?api-version=2025-11-15-preview` |\n| Delete agent | DELETE | `{projectEndpoint}\u002Fagents\u002F{agentName}?api-version=2025-11-15-preview` |\n\n### Create\u002FUpdate Payload\n\n```json\n{\n  \"definition\": {\n    \"kind\": \"prompt\",\n    \"model\": \"\u003Cdeployed-model-name>\",\n    \"instructions\": \"\u003Csystem prompt>\"\n  },\n  \"description\": \"\u003Cagent description>\",\n  \"metadata\": {\n    \"useCaseId\": \"\u003Cuse-case-id>\",\n    \"managedBy\": \"foundry-agent-sync\"\n  }\n}\n```\n\n## Troubleshooting\n\n| Symptom | Cause | Fix |\n|---|---|---|\n| `401 Unauthorized` | Token expired or wrong audience | Re-run `az account get-access-token --resource https:\u002F\u002Fai.azure.com\u002F` |\n| `403 Forbidden` | Missing Azure AI User role | Assign the role on the Foundry project scope |\n| `404 Not Found` | Wrong project endpoint | Verify endpoint includes `\u002Fapi\u002Fprojects\u002F{projectName}` |\n| Model not found | Model not deployed in project | Deploy the model in AI Foundry portal first |\n| Empty definitions | Manifest path wrong | Check `-ManifestPath` points to the JSON file |\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Ffoundry-agent-sync",5344,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-13 02:05:36",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add github\u002Fawesome-copilot --skill foundry-agent-sync",{"tool":76,"command":77},"bunx","bunx skills add github\u002Fawesome-copilot --skill foundry-agent-sync",{"tool":79,"command":80},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill foundry-agent-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Ffoundry-agent-sync\u002FSKILL.md",true,[84,90],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002FPOLICY.md","REFERENCE","参考文档",17,"https:\u002F\u002Fgithub.com\u002Fsorry510\u002Fgo_binance_futures\u002Fblob\u002Fmaster\u002Fagent\u002Fportableskill\u002Ftestdata\u002Fvalid-resources\u002Freferences\u002FPOLICY.md",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fcheck.sh","SCRIPT","脚本",29,"https:\u002F\u002Fgithub.com\u002Fsorry510\u002Fgo_binance_futures\u002Fblob\u002Fmaster\u002Fagent\u002Fportableskill\u002Ftestdata\u002Fvalid-resources\u002Fscripts\u002Fcheck.sh",[97,127,155,178,211,228],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":107,"publishedAt":55},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[103,106],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[108,109,110,111,112,35,113,114,115,116,117,118,119,120,121,122,123,124,125,126],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":55},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[133],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":55},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[162],{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[164,46,165,166,167,168,141,112,169,170,37,50,171,172,173,123,174,175,176,177],"custom","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":182,"sourceHtmlUrl":183,"categories":184,"keywords":189,"publishedAt":55},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[185,188],{"categoryNo":186,"categoryName":187,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[190,191,42,192,193,194,195,196,197,198,199,200,201,202,203,35,204,205,206,207,208,141,209,210],"winmd api search","search","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":215,"licenseFileUrl":216,"sourceHtmlUrl":217,"categories":218,"keywords":224,"publishedAt":55},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[219,220,223],{"categoryNo":186,"categoryName":187,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":221,"categoryName":222,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[225,138,198,226,227],"resemble detect","https","identity",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":215,"licenseFileUrl":232,"sourceHtmlUrl":233,"categories":234,"keywords":239,"publishedAt":55},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[235,238],{"categoryNo":236,"categoryName":237,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[240,241,242,243,46,113,9,137,244,245,226,246,247,248,249,250,251,252,253,254,255,256,121,257,258,259,260],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]