[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD7GN00X1PHT53624ZMA08":3,"skill-same:01M6AD7GN00X1PHT53624ZMA08":72},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6AD7GN00X1PHT53624ZMA08","aws-resource-health-diagnose",null,"Analyze AWS resource health, diagnose issues from CloudWatch logs and metrics, and create a remediation plan for identified problems.","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-resource-health-diagnose\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"diagnose","aws resource health diagnose","aws","health","create","issues","metrics","logs","remediation","plan","analyze","cloudwatch","remediation plan","for","2026-11-10 10:12:30",false,"---\nname: aws-resource-health-diagnose\ndescription: 'Analyze AWS resource health, diagnose issues from CloudWatch logs and metrics, and create a remediation plan for identified problems.'\n---\n\n# AWS Resource Health & Issue Diagnosis\n\nThis workflow analyzes a specific AWS resource to assess its health status, diagnose potential issues using CloudWatch logs and metrics, and develop a comprehensive remediation plan for any problems discovered.\n\n## Prerequisites\n- AWS CLI configured and authenticated\n- Target AWS resource identified (name, type, and optionally region\u002Faccount)\n- CloudWatch logging and metrics enabled on the target resource\n\n## Workflow Steps\n\n### Step 1: Get AWS Diagnostic Best Practices\nFetch `https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonCloudWatch\u002Flatest\u002Fmonitoring\u002F` for monitoring and troubleshooting guidance to inform the diagnostic approach.\n\n### Step 2: Resource Discovery & Identification\nLocate the target resource using the appropriate AWS CLI command for its type:\n\n```bash\n# EC2\naws ec2 describe-instances --filters \"Name=tag:Name,Values=\u003Cname>\"\n# Lambda\naws lambda get-function --function-name \u003Cname>\n# RDS\naws rds describe-db-instances --db-instance-identifier \u003Cname>\n# ECS\naws ecs describe-services --cluster \u003Ccluster> --services \u003Cname>\n# ALB\naws elbv2 describe-load-balancers --names \u003Cname>\n# DynamoDB\naws dynamodb describe-table --table-name \u003Cname>\n# SQS\naws sqs get-queue-attributes --queue-url \u003Curl> --attribute-names All\n# API Gateway\naws apigatewayv2 get-apis\n```\n\nIf multiple matches are found, prompt the user to specify region\u002Faccount.\n\n### Step 3: Health Status Assessment\nRun service-specific health checks:\n\n```bash\n# EC2\naws ec2 describe-instance-status --instance-ids \u003Cid>\n\n# RDS\naws rds describe-db-instances --db-instance-identifier \u003Cname> \\\n  --query 'DBInstances[0].DBInstanceStatus'\n\n# Lambda - error rate over 24h\naws cloudwatch get-metric-statistics --namespace AWS\u002FLambda \\\n  --metric-name Errors --dimensions Name=FunctionName,Value=\u003Cname> \\\n  --start-time $(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ) \\\n  --end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \\\n  --period 3600 --statistics Sum\n\n# ECS\naws ecs describe-services --cluster \u003Ccluster> --services \u003Cname> \\\n  --query 'services[0].[status,runningCount,desiredCount,pendingCount]'\n```\n\nKey health indicators by service type:\n- **Lambda**: Error rate, throttle rate, duration P99, concurrent executions\n- **RDS**: CPU utilization, FreeStorageSpace, DatabaseConnections, ReadLatency\u002FWriteLatency\n- **ECS**: Running vs desired task count, task stop reason\n- **ALB**: TargetResponseTime, HTTPCode_ELB_5XX_Count, UnHealthyHostCount\n- **SQS**: ApproximateNumberOfMessagesNotVisible, ApproximateAgeOfOldestMessage\n- **DynamoDB**: ConsumedReadCapacityUnits, ThrottledRequests, SuccessfulRequestLatency\n\n### Step 4: Log & Metrics Analysis\nFind log groups and run CloudWatch Logs Insights queries:\n\n```bash\n# Find log groups\naws logs describe-log-groups --log-group-name-prefix \u002Faws\u002F\u003Cservice>\u002F\u003Cname>\n\n# Start a query (last 24h errors)\naws logs start-query \\\n  --log-group-name \u002Faws\u002Flambda\u002F\u003Cname> \\\n  --start-time $(date -u -d '24 hours ago' +%s) \\\n  --end-time $(date -u +%s) \\\n  --query-string 'filter @message like \u002FERROR\u002F | stats count(*) as errorCount by bin(1h)'\n\n# Get results\naws logs get-query-results --query-id \u003Cid>\n\n# Lambda cold starts\naws logs start-query \\\n  --log-group-name \u002Faws\u002Flambda\u002F\u003Cname> \\\n  --start-time $(date -u -d '24 hours ago' +%s) \\\n  --end-time $(date -u +%s) \\\n  --query-string 'filter @type = \"REPORT\" | filter @initDuration > 0 | stats count() as coldStarts by bin(1h)'\n\n# RDS Performance Insights (if enabled)\naws pi get-resource-metrics \\\n  --service-type RDS --identifier db:\u003Cidentifier> \\\n  --metric-queries '[{\"Metric\":\"db.load.avg\"}]' \\\n  --start-time $(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ) \\\n  --end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \\\n  --period-in-seconds 3600\n```\n\nIdentify: recurring error patterns, correlation with deployments (CloudTrail), performance trends, dependency failures.\n\n### Step 5: Issue Classification & Root Cause Analysis\n**Severity**:\n- **Critical**: Service unavailable, data loss, security incidents\n- **High**: Performance degradation, error rates >5%, intermittent failures\n- **Medium**: Warnings, suboptimal configuration, minor performance issues\n- **Low**: Informational alerts, optimization opportunities\n\n**Root Cause Categories**:\n- Configuration Issues: wrong settings, missing env vars, IAM permission denials\n- Resource Constraints: CPU\u002Fmemory\u002Fdisk limits, Lambda throttling, RDS connection exhaustion\n- Network Issues: security group rules, VPC routing, DNS, NACLs\n- Application Issues: code bugs, memory leaks, unhandled exceptions, slow queries\n- Dependency Issues: downstream timeouts, SQS\u002FSNS failures, external API limits\n- Security Issues: KMS key issues, certificate expiration\n\n### Step 6: Generate Remediation Plan\n\n**Immediate Actions** (Critical):\n```bash\n# Lambda throttling — increase reserved concurrency\naws lambda put-reserved-concurrency \\\n  --function-name \u003Cname> --reserved-concurrent-executions 100\n\n# RDS connection exhaustion — reboot to reset connections\naws rds reboot-db-instance --db-instance-identifier \u003Cname>\n```\n\n**Short-term Fixes** (High\u002FMedium): Configuration adjustments, right-sizing, CloudWatch alarm improvements, IAM corrections.\n\n**Long-term Improvements**: Architectural changes for resilience, preventive monitoring, enable AWS Health Dashboard notifications via EventBridge.\n\n### Step 7: Report & User Confirmation\n\nPresent findings:\n```\n? AWS Resource Health Assessment\n\n? Resource Overview:\n• Resource: [Name] ([Type])\n• Status: [Healthy\u002FWarning\u002FCritical]\n• Region: [Region] | Account: [Account ID]\n\n? Issues Identified:\n• Critical: X | High: Y | Medium: Z | Low: N\n\n? Top Issues:\n1. [Issue]: [Description] — Impact: [High\u002FMedium\u002FLow]\n2. [Issue]: [Description] — Impact: [High\u002FMedium\u002FLow]\n\n?️ Remediation: X immediate, Y short-term, Z long-term actions\n\n❓ Proceed with detailed remediation plan? (y\u002Fn)\n```\n\nThen generate a full markdown report covering: health metrics, issues with root cause analysis, phased remediation steps with AWS CLI commands, CloudWatch alarm recommendations, and validation checklist.\n\n## Error Handling\n- **Resource Not Found**: Ask user to clarify name\u002Fregion\n- **Authentication Issues**: Guide through `aws configure`\n- **Insufficient Permissions**: List required IAM actions (`logs:*`, `cloudwatch:*`, `pi:*`)\n- **No Logs Available**: Suggest enabling CloudWatch logging for the resource type\n- **Query Timeouts**: Use shorter time windows\n\n## Success Criteria\n- ✅ Resource health accurately assessed across all key metrics\n- ✅ All significant issues identified and classified by severity\n- ✅ Root cause analysis completed for major problems\n- ✅ Actionable remediation plan with AWS CLI commands\n- ✅ CloudWatch monitoring recommendations included\n- ✅ Implementation steps include validation and rollback procedures\n","# AWS Resource Health & Issue Diagnosis\n\nThis workflow analyzes a specific AWS resource to assess its health status, diagnose potential issues using CloudWatch logs and metrics, and develop a comprehensive remediation plan for any problems discovered.\n\n## Prerequisites\n- AWS CLI configured and authenticated\n- Target AWS resource identified (name, type, and optionally region\u002Faccount)\n- CloudWatch logging and metrics enabled on the target resource\n\n## Workflow Steps\n\n### Step 1: Get AWS Diagnostic Best Practices\nFetch `https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonCloudWatch\u002Flatest\u002Fmonitoring\u002F` for monitoring and troubleshooting guidance to inform the diagnostic approach.\n\n### Step 2: Resource Discovery & Identification\nLocate the target resource using the appropriate AWS CLI command for its type:\n\n```bash\n# EC2\naws ec2 describe-instances --filters \"Name=tag:Name,Values=\u003Cname>\"\n# Lambda\naws lambda get-function --function-name \u003Cname>\n# RDS\naws rds describe-db-instances --db-instance-identifier \u003Cname>\n# ECS\naws ecs describe-services --cluster \u003Ccluster> --services \u003Cname>\n# ALB\naws elbv2 describe-load-balancers --names \u003Cname>\n# DynamoDB\naws dynamodb describe-table --table-name \u003Cname>\n# SQS\naws sqs get-queue-attributes --queue-url \u003Curl> --attribute-names All\n# API Gateway\naws apigatewayv2 get-apis\n```\n\nIf multiple matches are found, prompt the user to specify region\u002Faccount.\n\n### Step 3: Health Status Assessment\nRun service-specific health checks:\n\n```bash\n# EC2\naws ec2 describe-instance-status --instance-ids \u003Cid>\n\n# RDS\naws rds describe-db-instances --db-instance-identifier \u003Cname> \\\n  --query 'DBInstances[0].DBInstanceStatus'\n\n# Lambda - error rate over 24h\naws cloudwatch get-metric-statistics --namespace AWS\u002FLambda \\\n  --metric-name Errors --dimensions Name=FunctionName,Value=\u003Cname> \\\n  --start-time $(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ) \\\n  --end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \\\n  --period 3600 --statistics Sum\n\n# ECS\naws ecs describe-services --cluster \u003Ccluster> --services \u003Cname> \\\n  --query 'services[0].[status,runningCount,desiredCount,pendingCount]'\n```\n\nKey health indicators by service type:\n- **Lambda**: Error rate, throttle rate, duration P99, concurrent executions\n- **RDS**: CPU utilization, FreeStorageSpace, DatabaseConnections, ReadLatency\u002FWriteLatency\n- **ECS**: Running vs desired task count, task stop reason\n- **ALB**: TargetResponseTime, HTTPCode_ELB_5XX_Count, UnHealthyHostCount\n- **SQS**: ApproximateNumberOfMessagesNotVisible, ApproximateAgeOfOldestMessage\n- **DynamoDB**: ConsumedReadCapacityUnits, ThrottledRequests, SuccessfulRequestLatency\n\n### Step 4: Log & Metrics Analysis\nFind log groups and run CloudWatch Logs Insights queries:\n\n```bash\n# Find log groups\naws logs describe-log-groups --log-group-name-prefix \u002Faws\u002F\u003Cservice>\u002F\u003Cname>\n\n# Start a query (last 24h errors)\naws logs start-query \\\n  --log-group-name \u002Faws\u002Flambda\u002F\u003Cname> \\\n  --start-time $(date -u -d '24 hours ago' +%s) \\\n  --end-time $(date -u +%s) \\\n  --query-string 'filter @message like \u002FERROR\u002F | stats count(*) as errorCount by bin(1h)'\n\n# Get results\naws logs get-query-results --query-id \u003Cid>\n\n# Lambda cold starts\naws logs start-query \\\n  --log-group-name \u002Faws\u002Flambda\u002F\u003Cname> \\\n  --start-time $(date -u -d '24 hours ago' +%s) \\\n  --end-time $(date -u +%s) \\\n  --query-string 'filter @type = \"REPORT\" | filter @initDuration > 0 | stats count() as coldStarts by bin(1h)'\n\n# RDS Performance Insights (if enabled)\naws pi get-resource-metrics \\\n  --service-type RDS --identifier db:\u003Cidentifier> \\\n  --metric-queries '[{\"Metric\":\"db.load.avg\"}]' \\\n  --start-time $(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ) \\\n  --end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \\\n  --period-in-seconds 3600\n```\n\nIdentify: recurring error patterns, correlation with deployments (CloudTrail), performance trends, dependency failures.\n\n### Step 5: Issue Classification & Root Cause Analysis\n**Severity**:\n- **Critical**: Service unavailable, data loss, security incidents\n- **High**: Performance degradation, error rates >5%, intermittent failures\n- **Medium**: Warnings, suboptimal configuration, minor performance issues\n- **Low**: Informational alerts, optimization opportunities\n\n**Root Cause Categories**:\n- Configuration Issues: wrong settings, missing env vars, IAM permission denials\n- Resource Constraints: CPU\u002Fmemory\u002Fdisk limits, Lambda throttling, RDS connection exhaustion\n- Network Issues: security group rules, VPC routing, DNS, NACLs\n- Application Issues: code bugs, memory leaks, unhandled exceptions, slow queries\n- Dependency Issues: downstream timeouts, SQS\u002FSNS failures, external API limits\n- Security Issues: KMS key issues, certificate expiration\n\n### Step 6: Generate Remediation Plan\n\n**Immediate Actions** (Critical):\n```bash\n# Lambda throttling — increase reserved concurrency\naws lambda put-reserved-concurrency \\\n  --function-name \u003Cname> --reserved-concurrent-executions 100\n\n# RDS connection exhaustion — reboot to reset connections\naws rds reboot-db-instance --db-instance-identifier \u003Cname>\n```\n\n**Short-term Fixes** (High\u002FMedium): Configuration adjustments, right-sizing, CloudWatch alarm improvements, IAM corrections.\n\n**Long-term Improvements**: Architectural changes for resilience, preventive monitoring, enable AWS Health Dashboard notifications via EventBridge.\n\n### Step 7: Report & User Confirmation\n\nPresent findings:\n```\n? AWS Resource Health Assessment\n\n? Resource Overview:\n• Resource: [Name] ([Type])\n• Status: [Healthy\u002FWarning\u002FCritical]\n• Region: [Region] | Account: [Account ID]\n\n? Issues Identified:\n• Critical: X | High: Y | Medium: Z | Low: N\n\n? Top Issues:\n1. [Issue]: [Description] — Impact: [High\u002FMedium\u002FLow]\n2. [Issue]: [Description] — Impact: [High\u002FMedium\u002FLow]\n\n?️ Remediation: X immediate, Y short-term, Z long-term actions\n\n❓ Proceed with detailed remediation plan? (y\u002Fn)\n```\n\nThen generate a full markdown report covering: health metrics, issues with root cause analysis, phased remediation steps with AWS CLI commands, CloudWatch alarm recommendations, and validation checklist.\n\n## Error Handling\n- **Resource Not Found**: Ask user to clarify name\u002Fregion\n- **Authentication Issues**: Guide through `aws configure`\n- **Insufficient Permissions**: List required IAM actions (`logs:*`, `cloudwatch:*`, `pi:*`)\n- **No Logs Available**: Suggest enabling CloudWatch logging for the resource type\n- **Query Timeouts**: Use shorter time windows\n\n## Success Criteria\n- ✅ Resource health accurately assessed across all key metrics\n- ✅ All significant issues identified and classified by severity\n- ✅ Root cause analysis completed for major problems\n- ✅ Actionable remediation plan with AWS CLI commands\n- ✅ CloudWatch monitoring recommendations included\n- ✅ Implementation steps include validation and rollback procedures\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Faws-resource-health-diagnose",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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add github\u002Fawesome-copilot --skill aws-resource-health-diagnose",{"tool":54,"command":55},"bunx","bunx skills add github\u002Fawesome-copilot --skill aws-resource-health-diagnose",{"tool":57,"command":58},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill aws-resource-health-diagnose","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Faws-resource-health-diagnose\u002FSKILL.md",true,[62,68],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fprompting.md","REFERENCE","参考文档",3166,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fpoteto-help\u002Freferences\u002Fprompting.md",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Frecipes.md",3661,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fpoteto-help\u002Freferences\u002Frecipes.md",[73,108,135,165,199,216],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":87,"publishedAt":33},"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",[79,84],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":85,"categoryName":86,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000023","Skill与智能体开发",[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":33},"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",[114],{"categoryNo":85,"categoryName":86,"taxonomyType":82,"taxonomyTypeDesc":83},[116,117,118,119,120,121,32,122,123,124,125,126,127,128,129,130,131,132,133,134],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":147,"publishedAt":33},"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",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[148,149,150,151,152,153,32,92,154,155,156,157,158,159,160,104,161,162,163,164],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":176,"publishedAt":33},"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",[172,175],{"categoryNo":173,"categoryName":174,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},[177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,93,192,193,194,195,196,32,197,198],"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":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":203,"licenseFileUrl":204,"sourceHtmlUrl":205,"categories":206,"keywords":212,"publishedAt":33},"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",[207,208,211],{"categoryNo":173,"categoryName":174,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":209,"categoryName":210,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":85,"categoryName":86,"taxonomyType":82,"taxonomyTypeDesc":83},[213,119,186,214,215],"resemble detect","https","identity",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":203,"licenseFileUrl":220,"sourceHtmlUrl":221,"categories":222,"keywords":227,"publishedAt":33},"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",[223,226],{"categoryNo":224,"categoryName":225,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":85,"categoryName":86,"taxonomyType":82,"taxonomyTypeDesc":83},[228,229,230,231,149,94,9,118,232,233,214,234,235,236,237,238,239,240,241,242,243,244,102,245,246,247,248],"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"]