[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H6NWT6JM1CD9JVC0HZDMSD":3,"skill-same:01M6H6NWT6JM1CD9JVC0HZDMSD":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6H6NWT6JM1CD9JVC0HZDMSD","gamma-incident-runbook",null,"Manage incident response for Gamma integration issues.\nUse when experiencing production incidents, outages,\nor need systematic troubleshooting procedures.\nTrigger with phrases like \"gamma incident\", \"gamma outage\",\n\"gamma down\", \"gamma emergency\", \"gamma runbook\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fgamma-pack\u002Fskills\u002Fgamma-incident-runbook\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"gamma incident runbook","runbook","incident","gamma","manage","for","incidents","with","trigger","io","systematic","openclaw","use","edit","write","read","Bash","issues","code","incident response","2026-11-10 10:12:30",false,"---\nname: gamma-incident-runbook\ndescription: |\n  Manage incident response for Gamma integration issues.\n  Use when experiencing production incidents, outages,\n  or need systematic troubleshooting procedures.\n  Trigger with phrases like \"gamma incident\", \"gamma outage\",\n  \"gamma down\", \"gamma emergency\", \"gamma runbook\".\nallowed-tools: Read, Write, Edit, Bash(curl:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Gamma Incident Runbook\n\n## Overview\nSystematic procedures for responding to and resolving Gamma integration incidents.\n\n## Prerequisites\n- Access to monitoring dashboards\n- Access to application logs\n- On-call responsibilities defined\n- Communication channels established\n\n## Incident Severity Levels\n\n| Level | Description | Response Time | Escalation |\n|-------|-------------|---------------|------------|\n| P1 | Complete outage, no presentations | \u003C 15 min | Immediate |\n| P2 | Degraded, slow or partial failures | \u003C 30 min | 1 hour |\n| P3 | Minor issues, workaround available | \u003C 2 hours | 4 hours |\n| P4 | Cosmetic or non-urgent | \u003C 24 hours | None |\n\n## Quick Diagnostics\n\n### Step 1: Check Gamma Status\n```bash\nset -euo pipefail\n# Check Gamma status page\ncurl -s https:\u002F\u002Fstatus.gamma.app\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status'\n\n# Check our integration health\ncurl -s https:\u002F\u002Fyour-app.com\u002Fhealth\u002Fgamma | jq '.'\n\n# Quick connectivity test\ncurl -w \"\\nTime: %{time_total}s\\n\" \\\n  -H \"Authorization: Bearer $GAMMA_API_KEY\" \\\n  https:\u002F\u002Fapi.gamma.app\u002Fv1\u002Fping\n```\n\n### Step 2: Review Key Metrics\n```bash\nset -euo pipefail\n# Check error rate (Prometheus)\ncurl -s 'http:\u002F\u002Fprometheus:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(gamma_requests_total{status=~\"5..\"}[5m])' | jq '.data.result'  # 9090: Prometheus port\n\n# Check latency P95\ncurl -s 'http:\u002F\u002Fprometheus:9090\u002Fapi\u002Fv1\u002Fquery?query=histogram_quantile(0.95,rate(gamma_request_duration_seconds_bucket[5m]))' | jq '.data.result'  # Prometheus port\n\n# Check rate limit\ncurl -s 'http:\u002F\u002Fprometheus:9090\u002Fapi\u002Fv1\u002Fquery?query=gamma_rate_limit_remaining' | jq '.data.result'  # Prometheus port\n```\n\n### Step 3: Review Recent Logs\n```bash\n# Last 100 error logs\ngrep -i \"gamma.*error\" \u002Fvar\u002Flog\u002Fapp\u002Fgamma-*.log | tail -100\n\n# Rate limit hits\ngrep \"429\" \u002Fvar\u002Flog\u002Fapp\u002Fgamma-*.log | wc -l  # HTTP 429 Too Many Requests\n\n# Timeout errors\ngrep -i \"timeout\" \u002Fvar\u002Flog\u002Fapp\u002Fgamma-*.log | tail -50\n```\n\n## Incident Response Procedures\n\n### Scenario 1: API Returning 5xx Errors\n\n**Symptoms:**\n- High error rate in monitoring\n- Users reporting failed presentations\n- 500\u002F502\u002F503 responses from Gamma\n\n**Actions:**\n1. Verify Gamma status: https:\u002F\u002Fstatus.gamma.app\n2. If Gamma outage confirmed:\n   - Enable degraded mode \u002F show maintenance message\n   - Monitor status page for updates\n   - No action needed on our side\n\n3. If Gamma is operational:\n   ```bash\n   # Check our request patterns\n   grep \"5[0-9][0-9]\" \u002Fvar\u002Flog\u002Fapp\u002Fgamma-*.log | \\\n     awk '{print $1}' | sort | uniq -c | sort -rn\n\n   # Look for malformed requests\n   grep -B5 \"500\" \u002Fvar\u002Flog\u002Fapp\u002Fgamma-*.log | grep \"request\"\n   ```\n\n4. Rollback recent deployments if issue correlates\n\n### Scenario 2: Rate Limit Exceeded (429)\n\n**Symptoms:**\n- 429 responses in logs\n- Rate limit metrics at zero\n- Slow or queued requests\n\n**Actions:**\n1. Immediate mitigation:\n   ```bash\n   # Enable request throttling\n   curl -X POST http:\u002F\u002Flocalhost:8080\u002Fadmin\u002Fthrottle \\\n     -d '{\"gamma\": {\"rps\": 10}}'\n   ```\n\n2. Check for runaway processes:\n   ```bash\n   # Find high-volume clients\n   grep \"gamma\" \u002Fvar\u002Flog\u002Fapp\u002F*.log | \\\n     awk '{print $5}' | sort | uniq -c | sort -rn | head -20\n   ```\n\n3. Enable circuit breaker:\n   ```bash\n   curl -X POST http:\u002F\u002Flocalhost:8080\u002Fadmin\u002Fcircuit-breaker \\\n     -d '{\"service\": \"gamma\", \"state\": \"open\"}'\n   ```\n\n4. Long-term: Review rate limit tier with Gamma\n\n### Scenario 3: High Latency\n\n**Symptoms:**\n- Slow presentation creation\n- Timeouts in logs\n- P95 latency > 10s\n\n**Actions:**\n1. Check Gamma latency vs our latency:\n   ```bash\n   # Direct Gamma latency\n   for i in {1..5}; do\n     curl -w \"%{time_total}\\n\" -o \u002Fdev\u002Fnull -s \\\n       -H \"Authorization: Bearer $GAMMA_API_KEY\" \\\n       https:\u002F\u002Fapi.gamma.app\u002Fv1\u002Fping\n   done\n   ```\n\n2. If Gamma is slow:\n   - Increase timeouts temporarily\n   - Enable async mode for non-critical operations\n   - Queue heavy operations\n\n3. If our infrastructure is slow:\n   - Check CPU\u002Fmemory on app servers\n   - Review connection pool settings\n   - Check network connectivity\n\n### Scenario 4: Authentication Failures (401\u002F403)\n\n**Symptoms:**\n- All requests failing with 401\n- \"Invalid API key\" errors\n- Sudden authentication failures\n\n**Actions:**\n1. Verify API key:\n   ```bash\n   # Test key directly\n   curl -H \"Authorization: Bearer $GAMMA_API_KEY\" \\\n     https:\u002F\u002Fapi.gamma.app\u002Fv1\u002Fping\n\n   # Check key format\n   echo $GAMMA_API_KEY | head -c 20\n   ```\n\n2. If key is invalid:\n   - Check if key was rotated\n   - Deploy backup key: `GAMMA_API_KEY_SECONDARY`\n   - Generate new key in Gamma dashboard\n\n3. Notify team and update secrets\n\n## Communication Templates\n\n### Internal Notification\n```\nINCIDENT: Gamma Integration Issue\n\nSeverity: P[X]\nStatus: Investigating \u002F Identified \u002F Mitigating \u002F Resolved\nImpact: [Description of user impact]\nStart Time: [ISO timestamp]\n\nSummary: [Brief description]\n\nCurrent Actions:\n- [Action 1]\n- [Action 2]\n\nNext Update: [Time]\n```\n\n### User-Facing Message\n```\nWe're currently experiencing issues with presentation generation.\nOur team is actively working to resolve this.\n\nWorkaround: [If available]\nStatus updates: [Link to status page]\nETA: [If known]\n```\n\n## Post-Incident Checklist\n\n- [ ] Incident timeline documented\n- [ ] Root cause identified\n- [ ] User impact quantified\n- [ ] Fix verified in production\n- [ ] Monitoring gaps identified\n- [ ] Preventive measures documented\n- [ ] Post-mortem scheduled (for P1\u002FP2)\n\n## Resources\n- [Gamma Status](https:\u002F\u002Fstatus.gamma.app)\n- [Gamma Support](https:\u002F\u002Fgamma.app\u002Fsupport)\n- [Internal Runbook Wiki]()\n- [On-Call Schedule]()\n\n## Next Steps\nProceed to `gamma-data-handling` for data management.\n\n## Instructions\n\n1. Assess the current state of the Gamma configuration\n2. Identify the specific requirements and constraints\n3. Apply the recommended patterns from this skill\n4. Validate the changes against expected behavior\n5. Document the configuration for team reference\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with Gamma |\n| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |\n| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |\n\n## Examples\n\n**Basic usage**: Apply gamma incident runbook to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize gamma incident runbook for production environments with multiple constraints and team-specific requirements.","# Gamma Incident Runbook\n\n## Overview\nSystematic procedures for responding to and resolving Gamma integration incidents.\n\n## Prerequisites\n- Access to monitoring dashboards\n- Access to application logs\n- On-call responsibilities defined\n- Communication channels established\n\n## Incident Severity Levels\n\n| Level | Description | Response Time | Escalation |\n|-------|-------------|---------------|------------|\n| P1 | Complete outage, no presentations | \u003C 15 min | Immediate |\n| P2 | Degraded, slow or partial failures | \u003C 30 min | 1 hour |\n| P3 | Minor issues, workaround available | \u003C 2 hours | 4 hours |\n| P4 | Cosmetic or non-urgent | \u003C 24 hours | None |\n\n## Quick Diagnostics\n\n### Step 1: Check Gamma Status\n```bash\nset -euo pipefail\n# Check Gamma status page\ncurl -s https:\u002F\u002Fstatus.gamma.app\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status'\n\n# Check our integration health\ncurl -s https:\u002F\u002Fyour-app.com\u002Fhealth\u002Fgamma | jq '.'\n\n# Quick connectivity test\ncurl -w \"\\nTime: %{time_total}s\\n\" \\\n  -H \"Authorization: Bearer $GAMMA_API_KEY\" \\\n  https:\u002F\u002Fapi.gamma.app\u002Fv1\u002Fping\n```\n\n### Step 2: Review Key Metrics\n```bash\nset -euo pipefail\n# Check error rate (Prometheus)\ncurl -s 'http:\u002F\u002Fprometheus:9090\u002Fapi\u002Fv1\u002Fquery?query=rate(gamma_requests_total{status=~\"5..\"}[5m])' | jq '.data.result'  # 9090: Prometheus port\n\n# Check latency P95\ncurl -s 'http:\u002F\u002Fprometheus:9090\u002Fapi\u002Fv1\u002Fquery?query=histogram_quantile(0.95,rate(gamma_request_duration_seconds_bucket[5m]))' | jq '.data.result'  # Prometheus port\n\n# Check rate limit\ncurl -s 'http:\u002F\u002Fprometheus:9090\u002Fapi\u002Fv1\u002Fquery?query=gamma_rate_limit_remaining' | jq '.data.result'  # Prometheus port\n```\n\n### Step 3: Review Recent Logs\n```bash\n# Last 100 error logs\ngrep -i \"gamma.*error\" \u002Fvar\u002Flog\u002Fapp\u002Fgamma-*.log | tail -100\n\n# Rate limit hits\ngrep \"429\" \u002Fvar\u002Flog\u002Fapp\u002Fgamma-*.log | wc -l  # HTTP 429 Too Many Requests\n\n# Timeout errors\ngrep -i \"timeout\" \u002Fvar\u002Flog\u002Fapp\u002Fgamma-*.log | tail -50\n```\n\n## Incident Response Procedures\n\n### Scenario 1: API Returning 5xx Errors\n\n**Symptoms:**\n- High error rate in monitoring\n- Users reporting failed presentations\n- 500\u002F502\u002F503 responses from Gamma\n\n**Actions:**\n1. Verify Gamma status: https:\u002F\u002Fstatus.gamma.app\n2. If Gamma outage confirmed:\n   - Enable degraded mode \u002F show maintenance message\n   - Monitor status page for updates\n   - No action needed on our side\n\n3. If Gamma is operational:\n   ```bash\n   # Check our request patterns\n   grep \"5[0-9][0-9]\" \u002Fvar\u002Flog\u002Fapp\u002Fgamma-*.log | \\\n     awk '{print $1}' | sort | uniq -c | sort -rn\n\n   # Look for malformed requests\n   grep -B5 \"500\" \u002Fvar\u002Flog\u002Fapp\u002Fgamma-*.log | grep \"request\"\n   ```\n\n4. Rollback recent deployments if issue correlates\n\n### Scenario 2: Rate Limit Exceeded (429)\n\n**Symptoms:**\n- 429 responses in logs\n- Rate limit metrics at zero\n- Slow or queued requests\n\n**Actions:**\n1. Immediate mitigation:\n   ```bash\n   # Enable request throttling\n   curl -X POST http:\u002F\u002Flocalhost:8080\u002Fadmin\u002Fthrottle \\\n     -d '{\"gamma\": {\"rps\": 10}}'\n   ```\n\n2. Check for runaway processes:\n   ```bash\n   # Find high-volume clients\n   grep \"gamma\" \u002Fvar\u002Flog\u002Fapp\u002F*.log | \\\n     awk '{print $5}' | sort | uniq -c | sort -rn | head -20\n   ```\n\n3. Enable circuit breaker:\n   ```bash\n   curl -X POST http:\u002F\u002Flocalhost:8080\u002Fadmin\u002Fcircuit-breaker \\\n     -d '{\"service\": \"gamma\", \"state\": \"open\"}'\n   ```\n\n4. Long-term: Review rate limit tier with Gamma\n\n### Scenario 3: High Latency\n\n**Symptoms:**\n- Slow presentation creation\n- Timeouts in logs\n- P95 latency > 10s\n\n**Actions:**\n1. Check Gamma latency vs our latency:\n   ```bash\n   # Direct Gamma latency\n   for i in {1..5}; do\n     curl -w \"%{time_total}\\n\" -o \u002Fdev\u002Fnull -s \\\n       -H \"Authorization: Bearer $GAMMA_API_KEY\" \\\n       https:\u002F\u002Fapi.gamma.app\u002Fv1\u002Fping\n   done\n   ```\n\n2. If Gamma is slow:\n   - Increase timeouts temporarily\n   - Enable async mode for non-critical operations\n   - Queue heavy operations\n\n3. If our infrastructure is slow:\n   - Check CPU\u002Fmemory on app servers\n   - Review connection pool settings\n   - Check network connectivity\n\n### Scenario 4: Authentication Failures (401\u002F403)\n\n**Symptoms:**\n- All requests failing with 401\n- \"Invalid API key\" errors\n- Sudden authentication failures\n\n**Actions:**\n1. Verify API key:\n   ```bash\n   # Test key directly\n   curl -H \"Authorization: Bearer $GAMMA_API_KEY\" \\\n     https:\u002F\u002Fapi.gamma.app\u002Fv1\u002Fping\n\n   # Check key format\n   echo $GAMMA_API_KEY | head -c 20\n   ```\n\n2. If key is invalid:\n   - Check if key was rotated\n   - Deploy backup key: `GAMMA_API_KEY_SECONDARY`\n   - Generate new key in Gamma dashboard\n\n3. Notify team and update secrets\n\n## Communication Templates\n\n### Internal Notification\n```\nINCIDENT: Gamma Integration Issue\n\nSeverity: P[X]\nStatus: Investigating \u002F Identified \u002F Mitigating \u002F Resolved\nImpact: [Description of user impact]\nStart Time: [ISO timestamp]\n\nSummary: [Brief description]\n\nCurrent Actions:\n- [Action 1]\n- [Action 2]\n\nNext Update: [Time]\n```\n\n### User-Facing Message\n```\nWe're currently experiencing issues with presentation generation.\nOur team is actively working to resolve this.\n\nWorkaround: [If available]\nStatus updates: [Link to status page]\nETA: [If known]\n```\n\n## Post-Incident Checklist\n\n- [ ] Incident timeline documented\n- [ ] Root cause identified\n- [ ] User impact quantified\n- [ ] Fix verified in production\n- [ ] Monitoring gaps identified\n- [ ] Preventive measures documented\n- [ ] Post-mortem scheduled (for P1\u002FP2)\n\n## Resources\n- [Gamma Status](https:\u002F\u002Fstatus.gamma.app)\n- [Gamma Support](https:\u002F\u002Fgamma.app\u002Fsupport)\n- [Internal Runbook Wiki]()\n- [On-Call Schedule]()\n\n## Next Steps\nProceed to `gamma-data-handling` for data management.\n\n## Instructions\n\n1. Assess the current state of the Gamma configuration\n2. Identify the specific requirements and constraints\n3. Apply the recommended patterns from this skill\n4. Validate the changes against expected behavior\n5. Document the configuration for team reference\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with Gamma |\n| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |\n| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |\n\n## Examples\n\n**Basic usage**: Apply gamma incident runbook to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize gamma incident runbook for production environments with multiple constraints and team-specific requirements.",{"name":5,"author":43,"license":14,"version":44,"description":45,"allowed-tools":46,"compatible-with":47},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Manage incident response for Gamma integration issues.\nUse when experiencing production incidents, outages,\nor need systematic troubleshooting procedures.\nTrigger with phrases like \"gamma incident\", \"gamma outage\",\n\"gamma down\", \"gamma emergency\", \"gamma runbook\".\n","Read, Write, Edit, Bash(curl:*), Grep","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fgamma-pack\u002Fskills\u002Fgamma-incident-runbook",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add micsapp\u002Fmicstec-skills --skill gamma-incident-runbook",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill gamma-incident-runbook",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill gamma-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fgamma-pack\u002Fskills\u002Fgamma-incident-runbook\u002FSKILL.md",true,[],[70,106,135,155,175,198],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":86,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[76,81],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,23],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":120,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[112,113,116,119],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":114,"categoryName":115,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":117,"categoryName":118,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[121,122,123,124,88,125,36,126,127,128,129,130,96,97,103,131,132,104,133,134],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[141],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[143,144,145,146,88,91,96,97,147,30,148,149,150,151,152,104,153,154,134,23],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":163,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[161,162],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[164,146,165,96,149,166,88,121,167,168,169,170,97,171,104,172,173,174,105,23],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[182,183,184,123,185,186,187,35,96,188,189,190,31,191,192,193,194,195,196,197],"cli","jira","jira cli","init","tasks","create","common","work","command","list","view","project","project work","token","line","sprints",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[200,205,206,207,208,209,210,30,211,212],"npm","js","calculate","node","math","user","compute","errors"]