[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD7DXZN838XC05PGSNCEJR":3,"skill-same:01M6AD7DXZN838XC05PGSNCEJR":60},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6AD7DXZN838XC05PGSNCEJR","aws-cost-optimize",null,"Analyze AWS resources used in the app (IaC files and\u002For resources in a target account\u002Fregion) and optimize costs - creating GitHub issues for identified optimizations.","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\u002Faws-cost-optimize\u002FSKILL.md",[],[19,20,21,22,9,23,24,25,26,27,28,29,30],"aws cost optimize","aws","cost","optimize","github issues","issues","analyze","iac","files","app","resources","for","2026-11-10 10:12:30",false,"---\nname: aws-cost-optimize\ndescription: 'Analyze AWS resources used in the app (IaC files and\u002For resources in a target account\u002Fregion) and optimize costs - creating GitHub issues for identified optimizations.'\n---\n\n# AWS Cost Optimize\n\nThis workflow analyzes Infrastructure-as-Code (IaC) files and AWS resources to generate cost optimization recommendations. It creates individual GitHub issues for each optimization opportunity plus one EPIC issue to coordinate implementation, enabling efficient tracking and execution of cost savings initiatives.\n\n## Prerequisites\n- AWS CLI configured and authenticated (`aws sts get-caller-identity` succeeds)\n- GitHub MCP server configured and authenticated\n- Target GitHub repository identified\n- AWS resources deployed (IaC files optional but helpful)\n\n## Workflow Steps\n\n### Step 1: Get AWS Cost Optimization Best Practices\n**Action**: Retrieve cost optimization best practices before analysis\n**Tools**: `fetch` to retrieve AWS documentation\n**Process**:\n1. **Load Best Practices**:\n   - Fetch `https:\u002F\u002Fdocs.aws.amazon.com\u002Fcost-management\u002Flatest\u002Fuserguide\u002Fcost-optimization-best-practices.html`\n   - Fetch the AWS Well-Architected Cost Optimization pillar summary\n   - Use these practices to inform subsequent analysis and recommendations\n\n### Step 2: Discover AWS Infrastructure\n**Action**: Dynamically discover and analyze AWS resources and configurations\n**Tools**: AWS CLI + Local file system access\n**Process**:\n1. **Account & Region Discovery**:\n   - Execute `aws sts get-caller-identity` to confirm account\n   - Execute `aws configure get region` to determine default region\n\n2. **Resource Discovery** (per region):\n   - EC2 instances: `aws ec2 describe-instances --query 'Reservations[].Instances[].[InstanceId,InstanceType,State.Name,Tags]'`\n   - RDS instances: `aws rds describe-db-instances --query 'DBInstances[].[DBInstanceIdentifier,DBInstanceClass,Engine,MultiAZ]'`\n   - Lambda functions: `aws lambda list-functions --query 'Functions[].[FunctionName,Runtime,MemorySize,Architectures]'`\n   - ECS clusters\u002Fservices: `aws ecs list-clusters` then `aws ecs describe-services`\n   - S3 buckets: `aws s3api list-buckets --query 'Buckets[].Name'`\n   - ElastiCache clusters: `aws elasticache describe-cache-clusters`\n   - NAT Gateways: `aws ec2 describe-nat-gateways`\n   - Load Balancers: `aws elbv2 describe-load-balancers`\n\n3. **IaC Detection**:\n   - Scan for IaC files: `**\u002F*.tf`, `**\u002F*.yaml` (CloudFormation\u002FSAM), `**\u002F*.json` (CloudFormation), `**\u002Fcdk.json`, `lib\u002F**\u002F*.ts` (CDK)\n   - Parse resource definitions to understand intended configurations\n   - Do NOT use application code files — only IaC files as the source of truth\n   - If no IaC files found: STOP and report to user\n\n### Step 3: Collect Usage Metrics & Validate Current Costs\n**Action**: Gather utilization data and verify actual resource costs\n**Tools**: AWS CLI (CloudWatch, Cost Explorer)\n**Process**:\n1. **CloudWatch Metrics** (last 7 days):\n   ```bash\n   # EC2 CPU utilization\n   aws cloudwatch get-metric-statistics \\\n     --namespace AWS\u002FEC2 --metric-name CPUUtilization \\\n     --dimensions Name=InstanceId,Value=\u003Cid> \\\n     --start-time $(date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%SZ) \\\n     --end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \\\n     --period 3600 --statistics Average\n\n   # Lambda duration\n   aws cloudwatch get-metric-statistics \\\n     --namespace AWS\u002FLambda --metric-name Duration \\\n     --dimensions Name=FunctionName,Value=\u003Cname> \\\n     --start-time $(date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%SZ) \\\n     --end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \\\n     --period 86400 --statistics Average,Maximum\n   ```\n\n2. **AWS Cost Explorer**:\n   ```bash\n   aws ce get-cost-and-usage \\\n     --time-period Start=$(date -u -d '30 days ago' +%Y-%m-%d),End=$(date -u +%Y-%m-%d) \\\n     --granularity MONTHLY --metrics BlendedCost \\\n     --group-by Type=DIMENSION,Key=SERVICE\n   ```\n\n3. **Calculate Baseline Metrics**: CPU\u002FMemory averages, Lambda invocation rates, data transfer patterns, and a realistic current monthly total.\n\n### Step 4: Generate Cost Optimization Recommendations\n**Action**: Analyze resources to identify optimization opportunities\n**Process**:\n1. **Apply Optimization Patterns**:\n\n   **Compute**:\n   - EC2: Right-size based on CPU\u002Fmemory (\u003C20% average → downsize), convert On-Demand to Savings Plans, migrate to Graviton\u002FARM (up to 40% cheaper)\n   - Lambda: Reduce memory for idle functions, switch to `arm64` (20% cheaper)\n   - ECS\u002FEKS: Use Fargate Spot for dev\u002Fbatch workloads\n\n   **Database**:\n   - RDS: Right-size instance class, convert single-AZ for dev, use Aurora Serverless v2 for variable load\n   - DynamoDB: Switch Provisioned → On-Demand for unpredictable traffic\n   - ElastiCache: Right-size node type based on memory utilization\n\n   **Storage**:\n   - S3: Lifecycle policies (Standard → Standard-IA after 30d → Glacier after 90d), enable Intelligent-Tiering\n   - EBS: Delete unattached volumes, convert gp2 → gp3 (same performance, 20% cheaper)\n\n   **Network**:\n   - Consolidate NAT Gateways for non-production environments\n   - Use VPC endpoints for S3\u002FDynamoDB to avoid NAT Gateway charges\n\n2. **Calculate Priority Score**:\n   ```\n   Priority Score = (Value Score × Monthly Savings) \u002F (Risk Score × Implementation Days)\n   High: Score > 20 | Medium: Score 5-20 | Low: Score \u003C 5\n   ```\n\n### Step 5: User Confirmation\n**Action**: Present summary and get approval before creating GitHub issues\n\n```\n? AWS Cost Optimization Summary\n\n? Analysis Results:\n• Total Resources Analyzed: X\n• Current Monthly Cost: $X\n• Potential Monthly Savings: $Y\n• Optimization Opportunities: Z\n• High Priority Items: N\n\n? Recommendations:\n1. [Resource]: [Current] → [Target] = $X\u002Fmonth savings - [Risk] | [Effort]\n...\n\n? This will create Y individual GitHub issues + 1 EPIC issue.\n\n❓ Proceed with creating GitHub issues? (y\u002Fn)\n```\n\nWait for user confirmation before proceeding.\n\n### Step 6: Create Individual Optimization Issues\n**Action**: Create separate GitHub issues for each optimization. Label with \"cost-optimization\" (green) and \"aws\" (orange).\n\n**Title**: `[COST-OPT] [Resource Type] - [Brief Description] - $X\u002Fmonth savings`\n\n**Body**:\n````markdown\n## ? Cost Optimization: [Brief Title]\n\n**Monthly Savings**: $X | **Risk Level**: [Low\u002FMedium\u002FHigh] | **Effort**: X days\n\n### ? Description\n[Clear explanation of the optimization and why it's needed]\n\n### ? Implementation\n\n**IaC Files Detected**: [Yes\u002FNo]\n\n```bash\n# IaC modification (preferred) or AWS CLI fallback\n```\n\n### ? Evidence\n- Current Configuration: [details]\n- Usage Pattern: [evidence from CloudWatch]\n- Cost Impact: $X\u002Fmonth → $Y\u002Fmonth\n\n### ✅ Validation Steps\n- [ ] Test in non-production environment\n- [ ] Verify no performance degradation via CloudWatch\n- [ ] Confirm cost reduction in AWS Cost Explorer\n\n### ⚠️ Risks & Considerations\n- [Risk and mitigation]\n\n**Priority Score**: X | **Value**: X\u002F10 | **Risk**: X\u002F10\n````\n\n### Step 7: Create EPIC Coordinating Issue\n**Action**: Create master tracking issue. Label with \"cost-optimization\" (green), \"aws\" (orange), \"epic\" (purple).\n\n**Title**: `[EPIC] AWS Cost Optimization Initiative - $X\u002Fmonth potential savings`\n\n**Body**: Executive summary with account\u002Fregion details, Mermaid architecture diagram of current resources, prioritized checklist linking all individual issues (High → Medium → Low), progress tracking, and success criteria (>80% of estimated savings realized, no performance degradation).\n\n## Error Handling\n- **AWS Authentication Failure**: Guide through `aws configure`\n- **No Resources Found**: Create informational issue about AWS resource deployment\n- **Insufficient Permissions**: List required IAM read-only permissions\n- **GitHub Creation Failure**: Output formatted recommendations to console\n- **Cost Explorer Not Enabled**: Guide user to enable in AWS Console\n\n## Success Criteria\n- ✅ All cost estimates verified against actual configurations and AWS pricing\n- ✅ Individual GitHub issues created for each optimization\n- ✅ EPIC issue provides comprehensive coordination and tracking\n- ✅ All recommendations include specific AWS CLI or IaC commands\n- ✅ User confirmation obtained before creating issues\n","# AWS Cost Optimize\n\nThis workflow analyzes Infrastructure-as-Code (IaC) files and AWS resources to generate cost optimization recommendations. It creates individual GitHub issues for each optimization opportunity plus one EPIC issue to coordinate implementation, enabling efficient tracking and execution of cost savings initiatives.\n\n## Prerequisites\n- AWS CLI configured and authenticated (`aws sts get-caller-identity` succeeds)\n- GitHub MCP server configured and authenticated\n- Target GitHub repository identified\n- AWS resources deployed (IaC files optional but helpful)\n\n## Workflow Steps\n\n### Step 1: Get AWS Cost Optimization Best Practices\n**Action**: Retrieve cost optimization best practices before analysis\n**Tools**: `fetch` to retrieve AWS documentation\n**Process**:\n1. **Load Best Practices**:\n   - Fetch `https:\u002F\u002Fdocs.aws.amazon.com\u002Fcost-management\u002Flatest\u002Fuserguide\u002Fcost-optimization-best-practices.html`\n   - Fetch the AWS Well-Architected Cost Optimization pillar summary\n   - Use these practices to inform subsequent analysis and recommendations\n\n### Step 2: Discover AWS Infrastructure\n**Action**: Dynamically discover and analyze AWS resources and configurations\n**Tools**: AWS CLI + Local file system access\n**Process**:\n1. **Account & Region Discovery**:\n   - Execute `aws sts get-caller-identity` to confirm account\n   - Execute `aws configure get region` to determine default region\n\n2. **Resource Discovery** (per region):\n   - EC2 instances: `aws ec2 describe-instances --query 'Reservations[].Instances[].[InstanceId,InstanceType,State.Name,Tags]'`\n   - RDS instances: `aws rds describe-db-instances --query 'DBInstances[].[DBInstanceIdentifier,DBInstanceClass,Engine,MultiAZ]'`\n   - Lambda functions: `aws lambda list-functions --query 'Functions[].[FunctionName,Runtime,MemorySize,Architectures]'`\n   - ECS clusters\u002Fservices: `aws ecs list-clusters` then `aws ecs describe-services`\n   - S3 buckets: `aws s3api list-buckets --query 'Buckets[].Name'`\n   - ElastiCache clusters: `aws elasticache describe-cache-clusters`\n   - NAT Gateways: `aws ec2 describe-nat-gateways`\n   - Load Balancers: `aws elbv2 describe-load-balancers`\n\n3. **IaC Detection**:\n   - Scan for IaC files: `**\u002F*.tf`, `**\u002F*.yaml` (CloudFormation\u002FSAM), `**\u002F*.json` (CloudFormation), `**\u002Fcdk.json`, `lib\u002F**\u002F*.ts` (CDK)\n   - Parse resource definitions to understand intended configurations\n   - Do NOT use application code files — only IaC files as the source of truth\n   - If no IaC files found: STOP and report to user\n\n### Step 3: Collect Usage Metrics & Validate Current Costs\n**Action**: Gather utilization data and verify actual resource costs\n**Tools**: AWS CLI (CloudWatch, Cost Explorer)\n**Process**:\n1. **CloudWatch Metrics** (last 7 days):\n   ```bash\n   # EC2 CPU utilization\n   aws cloudwatch get-metric-statistics \\\n     --namespace AWS\u002FEC2 --metric-name CPUUtilization \\\n     --dimensions Name=InstanceId,Value=\u003Cid> \\\n     --start-time $(date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%SZ) \\\n     --end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \\\n     --period 3600 --statistics Average\n\n   # Lambda duration\n   aws cloudwatch get-metric-statistics \\\n     --namespace AWS\u002FLambda --metric-name Duration \\\n     --dimensions Name=FunctionName,Value=\u003Cname> \\\n     --start-time $(date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%SZ) \\\n     --end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \\\n     --period 86400 --statistics Average,Maximum\n   ```\n\n2. **AWS Cost Explorer**:\n   ```bash\n   aws ce get-cost-and-usage \\\n     --time-period Start=$(date -u -d '30 days ago' +%Y-%m-%d),End=$(date -u +%Y-%m-%d) \\\n     --granularity MONTHLY --metrics BlendedCost \\\n     --group-by Type=DIMENSION,Key=SERVICE\n   ```\n\n3. **Calculate Baseline Metrics**: CPU\u002FMemory averages, Lambda invocation rates, data transfer patterns, and a realistic current monthly total.\n\n### Step 4: Generate Cost Optimization Recommendations\n**Action**: Analyze resources to identify optimization opportunities\n**Process**:\n1. **Apply Optimization Patterns**:\n\n   **Compute**:\n   - EC2: Right-size based on CPU\u002Fmemory (\u003C20% average → downsize), convert On-Demand to Savings Plans, migrate to Graviton\u002FARM (up to 40% cheaper)\n   - Lambda: Reduce memory for idle functions, switch to `arm64` (20% cheaper)\n   - ECS\u002FEKS: Use Fargate Spot for dev\u002Fbatch workloads\n\n   **Database**:\n   - RDS: Right-size instance class, convert single-AZ for dev, use Aurora Serverless v2 for variable load\n   - DynamoDB: Switch Provisioned → On-Demand for unpredictable traffic\n   - ElastiCache: Right-size node type based on memory utilization\n\n   **Storage**:\n   - S3: Lifecycle policies (Standard → Standard-IA after 30d → Glacier after 90d), enable Intelligent-Tiering\n   - EBS: Delete unattached volumes, convert gp2 → gp3 (same performance, 20% cheaper)\n\n   **Network**:\n   - Consolidate NAT Gateways for non-production environments\n   - Use VPC endpoints for S3\u002FDynamoDB to avoid NAT Gateway charges\n\n2. **Calculate Priority Score**:\n   ```\n   Priority Score = (Value Score × Monthly Savings) \u002F (Risk Score × Implementation Days)\n   High: Score > 20 | Medium: Score 5-20 | Low: Score \u003C 5\n   ```\n\n### Step 5: User Confirmation\n**Action**: Present summary and get approval before creating GitHub issues\n\n```\n? AWS Cost Optimization Summary\n\n? Analysis Results:\n• Total Resources Analyzed: X\n• Current Monthly Cost: $X\n• Potential Monthly Savings: $Y\n• Optimization Opportunities: Z\n• High Priority Items: N\n\n? Recommendations:\n1. [Resource]: [Current] → [Target] = $X\u002Fmonth savings - [Risk] | [Effort]\n...\n\n? This will create Y individual GitHub issues + 1 EPIC issue.\n\n❓ Proceed with creating GitHub issues? (y\u002Fn)\n```\n\nWait for user confirmation before proceeding.\n\n### Step 6: Create Individual Optimization Issues\n**Action**: Create separate GitHub issues for each optimization. Label with \"cost-optimization\" (green) and \"aws\" (orange).\n\n**Title**: `[COST-OPT] [Resource Type] - [Brief Description] - $X\u002Fmonth savings`\n\n**Body**:\n````markdown\n## ? Cost Optimization: [Brief Title]\n\n**Monthly Savings**: $X | **Risk Level**: [Low\u002FMedium\u002FHigh] | **Effort**: X days\n\n### ? Description\n[Clear explanation of the optimization and why it's needed]\n\n### ? Implementation\n\n**IaC Files Detected**: [Yes\u002FNo]\n\n```bash\n# IaC modification (preferred) or AWS CLI fallback\n```\n\n### ? Evidence\n- Current Configuration: [details]\n- Usage Pattern: [evidence from CloudWatch]\n- Cost Impact: $X\u002Fmonth → $Y\u002Fmonth\n\n### ✅ Validation Steps\n- [ ] Test in non-production environment\n- [ ] Verify no performance degradation via CloudWatch\n- [ ] Confirm cost reduction in AWS Cost Explorer\n\n### ⚠️ Risks & Considerations\n- [Risk and mitigation]\n\n**Priority Score**: X | **Value**: X\u002F10 | **Risk**: X\u002F10\n````\n\n### Step 7: Create EPIC Coordinating Issue\n**Action**: Create master tracking issue. Label with \"cost-optimization\" (green), \"aws\" (orange), \"epic\" (purple).\n\n**Title**: `[EPIC] AWS Cost Optimization Initiative - $X\u002Fmonth potential savings`\n\n**Body**: Executive summary with account\u002Fregion details, Mermaid architecture diagram of current resources, prioritized checklist linking all individual issues (High → Medium → Low), progress tracking, and success criteria (>80% of estimated savings realized, no performance degradation).\n\n## Error Handling\n- **AWS Authentication Failure**: Guide through `aws configure`\n- **No Resources Found**: Create informational issue about AWS resource deployment\n- **Insufficient Permissions**: List required IAM read-only permissions\n- **GitHub Creation Failure**: Output formatted recommendations to console\n- **Cost Explorer Not Enabled**: Guide user to enable in AWS Console\n\n## Success Criteria\n- ✅ All cost estimates verified against actual configurations and AWS pricing\n- ✅ Individual GitHub issues created for each optimization\n- ✅ EPIC issue provides comprehensive coordination and tracking\n- ✅ All recommendations include specific AWS CLI or IaC commands\n- ✅ User confirmation obtained before creating issues\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Faws-cost-optimize",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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add github\u002Fawesome-copilot --skill aws-cost-optimize",{"tool":52,"command":53},"bunx","bunx skills add github\u002Fawesome-copilot --skill aws-cost-optimize",{"tool":55,"command":56},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill aws-cost-optimize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Faws-cost-optimize\u002FSKILL.md",true,[],[61,96,123,153,187,204],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":75,"publishedAt":31},"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",[67,72],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000023","Skill与智能体开发",[76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":103,"publishedAt":31},"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",[102],{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[104,105,106,107,108,109,30,110,111,112,113,114,115,116,117,118,119,120,121,122],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":135,"publishedAt":31},"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",[130],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[136,137,138,139,140,141,30,80,142,143,144,145,146,147,148,92,149,150,151,152],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":157,"sourceHtmlUrl":158,"categories":159,"keywords":164,"publishedAt":31},"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",[160,163],{"categoryNo":161,"categoryName":162,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},[165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,81,180,181,182,183,184,30,185,186],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":200,"publishedAt":31},"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",[195,196,199],{"categoryNo":161,"categoryName":162,"taxonomyType":70,"taxonomyTypeDesc":71},{"categoryNo":197,"categoryName":198,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[201,107,174,202,203],"resemble detect","https","identity",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":191,"licenseFileUrl":208,"sourceHtmlUrl":209,"categories":210,"keywords":215,"publishedAt":31},"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",[211,214],{"categoryNo":212,"categoryName":213,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":73,"categoryName":74,"taxonomyType":70,"taxonomyTypeDesc":71},[216,217,218,219,137,82,9,106,220,221,202,222,223,224,225,226,227,228,229,230,231,232,90,233,234,235,236],"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"]