[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H9KCYSBHCPT2HNPB2FTXCK":3,"skill-same:01M6H9KCYSBHCPT2HNPB2FTXCK":103},{"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},"01M6H9KCYSBHCPT2HNPB2FTXCK","responding-to-security-incidents",null,"Analyze and guide security incident response, investigation, and remediation processes.\nUse when you need to handle security breaches, classify incidents, develop response playbooks, gather forensic evidence, or coordinate remediation efforts.\nTrigger with phrases like \"security incident response\", \"ransomware attack response\", \"data breach investigation\", \"incident playbook\", or \"security forensics\".","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\u002Fsecurity\u002Fsecurity-incident-responder\u002Fskills\u002Fresponding-to-security-incidents\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"incidents","Responding to Security Incidents","security","log","breach","you","with","trigger","io","incident","coordinate","evidence","use","analyze","Bash","analysis","ransomware","log-analysis","code","incident response","2026-11-10 10:12:30",false,"---\nname: responding-to-security-incidents\ndescription: |\n  Analyze and guide security incident response, investigation, and remediation processes.\n  Use when you need to handle security breaches, classify incidents, develop response playbooks, gather forensic evidence, or coordinate remediation efforts.\n  Trigger with phrases like \"security incident response\", \"ransomware attack response\", \"data breach investigation\", \"incident playbook\", or \"security forensics\".\n  \nallowed-tools: Read, Write, Edit, Grep, Glob, Bash(log-analysis:*), Bash(forensics:*), Bash(network-trace:*)\nversion: 1.0.0\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\nlicense: MIT\ncompatible-with: claude-code, codex, openclaw\n---\n# Responding To Security Incidents\n\n## Overview\n\nGuide the full NIST SP 800-61 incident response lifecycle: detection, containment, eradication, recovery, and post-incident analysis. Classify incidents by type (ransomware, data breach, DDoS, credential compromise, insider threat) and severity, then coordinate evidence preservation, threat containment, and root-cause investigation.\n\n## Prerequisites\n\n- System and application logs accessible in `${CLAUDE_SKILL_DIR}\u002Flogs\u002F` (auth logs, web server logs, database access logs)\n- Network traffic captures (PCAP) or SIEM alert exports available\n- Incident response team contact information and escalation paths documented\n- Backup systems operational and recovery procedures tested\n- Write permissions for incident documentation in `${CLAUDE_SKILL_DIR}\u002Fincidents\u002F`\n- Forensic tools available: Volatility (memory), Autopsy\u002FFTK Imager (disk), tcpdump\u002FWireshark (network)\n\n## Instructions\n\n1. **Classify the incident**: determine type (ransomware, data breach, DDoS, phishing, insider threat), assign severity (Critical\u002FHigh\u002FMedium\u002FLow), and record initial detection timestamp and method.\n2. **Scope affected systems**: identify all compromised hosts, user accounts, data stores, and network segments. Map the blast radius.\n3. **Preserve evidence before any changes**: capture memory dumps (`volatility -f memdump.raw imageinfo`), create disk images, export running process lists (`ps auxf`), and snapshot network connection state (`ss -tulnp`).\n4. **Collect log evidence**: gather authentication logs (successful and failed), application error logs, firewall\u002FIDS alerts, DNS query logs, and proxy server logs. Store originals in `${CLAUDE_SKILL_DIR}\u002Fincidents\u002Fevidence\u002F`.\n5. **Contain the threat**: isolate affected systems from the network, disable compromised accounts, block malicious IPs at the firewall, and revoke compromised API keys or tokens.\n6. **Investigate and reconstruct timeline**: identify initial access vector, map lateral movement, determine data exfiltration scope, locate persistence mechanisms (cron jobs, startup scripts, web shells), and document all IOCs (IPs, hashes, domains, file paths).\n7. **Eradicate the threat**: remove malware and backdoors, patch exploited vulnerabilities, reset all potentially compromised credentials, and update firewall rules.\n8. **Recover operations**: restore from verified clean backups, rebuild compromised systems from hardened images, validate system integrity, and monitor for reinfection with heightened alerting.\n9. **Document the incident**: produce a comprehensive report at `${CLAUDE_SKILL_DIR}\u002Fincidents\u002Fincident-YYYYMMDD-HHMM.md` containing executive summary, detailed timeline, root cause analysis, IOC list, and lessons learned.\n10. **Create remediation backlog**: list all follow-up actions (patch gaps, monitoring improvements, policy changes) with owners and deadlines.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md` for the seven-phase implementation workflow.\n\n## Output\n\n- **Incident Report**: `${CLAUDE_SKILL_DIR}\u002Fincidents\u002Fincident-YYYYMMDD-HHMM.md` with timeline, root cause, IOCs, and impact assessment\n- **IOC List**: machine-readable indicators (IP addresses, file hashes, domains, YARA rules)\n- **After-Action Review**: lessons learned, process gaps, and recommended improvements\n- **Remediation Backlog**: prioritized follow-up tasks with owners and deadlines\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Critical logs missing from `${CLAUDE_SKILL_DIR}\u002Flogs\u002F` | Log rotation, deletion, or attacker tampering | Work with available data; note gaps; improve logging retention for future incidents |\n| System state modified before evidence collection | First responder made changes before forensic capture | Document contamination; collect remaining evidence; prioritize network and SIEM logs |\n| Attacker still has active access during investigation | Ongoing compromise detected | Prioritize containment over investigation; implement emergency network isolation |\n| Permission denied accessing system memory | Insufficient forensic tool privileges | Escalate to obtain root\u002Fadmin access; fall back to available log and network data |\n| Backups encrypted or corrupted by ransomware | Attacker targeted backup infrastructure | Identify offline\u002Fair-gapped backups; assess rebuild-from-scratch feasibility |\n\n## Examples\n\n- \"Credential stuffing detected. Use logs in `${CLAUDE_SKILL_DIR}\u002Flogs\u002F` to triage the incident, scope affected accounts, and propose containment steps.\"\n- \"Create an incident response plan for a suspected data breach: list evidence to collect, containment actions, and notification requirements.\"\n- \"Investigate a web shell found at `\u002Fvar\u002Fwww\u002Fhtml\u002Fuploads\u002Fcmd.php`. Trace the initial access vector, identify persistence mechanisms, and produce an IOC list.\"\n\n## Resources\n\n- NIST SP 800-61r2 Computer Security Incident Handling Guide: https:\u002F\u002Fnvlpubs.nist.gov\u002Fnistpubs\u002FSpecialPublications\u002FNIST.SP.800-61r2.pdf\n- SANS Incident Handler's Handbook: https:\u002F\u002Fwww.sans.org\u002Fwhite-papers\u002F33901\u002F\n- CISA Incident Response Guide: https:\u002F\u002Fwww.cisa.gov\u002Fincident-response\n- Volatility Framework (memory forensics): https:\u002F\u002Fwww.volatilityfoundation.org\u002F\n- Autopsy (disk forensics): https:\u002F\u002Fwww.autopsy.com\u002F\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` -- full error handling reference\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` -- additional usage examples\n- https:\u002F\u002Fintentsolutions.io","# Responding To Security Incidents\n\n## Overview\n\nGuide the full NIST SP 800-61 incident response lifecycle: detection, containment, eradication, recovery, and post-incident analysis. Classify incidents by type (ransomware, data breach, DDoS, credential compromise, insider threat) and severity, then coordinate evidence preservation, threat containment, and root-cause investigation.\n\n## Prerequisites\n\n- System and application logs accessible in `${CLAUDE_SKILL_DIR}\u002Flogs\u002F` (auth logs, web server logs, database access logs)\n- Network traffic captures (PCAP) or SIEM alert exports available\n- Incident response team contact information and escalation paths documented\n- Backup systems operational and recovery procedures tested\n- Write permissions for incident documentation in `${CLAUDE_SKILL_DIR}\u002Fincidents\u002F`\n- Forensic tools available: Volatility (memory), Autopsy\u002FFTK Imager (disk), tcpdump\u002FWireshark (network)\n\n## Instructions\n\n1. **Classify the incident**: determine type (ransomware, data breach, DDoS, phishing, insider threat), assign severity (Critical\u002FHigh\u002FMedium\u002FLow), and record initial detection timestamp and method.\n2. **Scope affected systems**: identify all compromised hosts, user accounts, data stores, and network segments. Map the blast radius.\n3. **Preserve evidence before any changes**: capture memory dumps (`volatility -f memdump.raw imageinfo`), create disk images, export running process lists (`ps auxf`), and snapshot network connection state (`ss -tulnp`).\n4. **Collect log evidence**: gather authentication logs (successful and failed), application error logs, firewall\u002FIDS alerts, DNS query logs, and proxy server logs. Store originals in `${CLAUDE_SKILL_DIR}\u002Fincidents\u002Fevidence\u002F`.\n5. **Contain the threat**: isolate affected systems from the network, disable compromised accounts, block malicious IPs at the firewall, and revoke compromised API keys or tokens.\n6. **Investigate and reconstruct timeline**: identify initial access vector, map lateral movement, determine data exfiltration scope, locate persistence mechanisms (cron jobs, startup scripts, web shells), and document all IOCs (IPs, hashes, domains, file paths).\n7. **Eradicate the threat**: remove malware and backdoors, patch exploited vulnerabilities, reset all potentially compromised credentials, and update firewall rules.\n8. **Recover operations**: restore from verified clean backups, rebuild compromised systems from hardened images, validate system integrity, and monitor for reinfection with heightened alerting.\n9. **Document the incident**: produce a comprehensive report at `${CLAUDE_SKILL_DIR}\u002Fincidents\u002Fincident-YYYYMMDD-HHMM.md` containing executive summary, detailed timeline, root cause analysis, IOC list, and lessons learned.\n10. **Create remediation backlog**: list all follow-up actions (patch gaps, monitoring improvements, policy changes) with owners and deadlines.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md` for the seven-phase implementation workflow.\n\n## Output\n\n- **Incident Report**: `${CLAUDE_SKILL_DIR}\u002Fincidents\u002Fincident-YYYYMMDD-HHMM.md` with timeline, root cause, IOCs, and impact assessment\n- **IOC List**: machine-readable indicators (IP addresses, file hashes, domains, YARA rules)\n- **After-Action Review**: lessons learned, process gaps, and recommended improvements\n- **Remediation Backlog**: prioritized follow-up tasks with owners and deadlines\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Critical logs missing from `${CLAUDE_SKILL_DIR}\u002Flogs\u002F` | Log rotation, deletion, or attacker tampering | Work with available data; note gaps; improve logging retention for future incidents |\n| System state modified before evidence collection | First responder made changes before forensic capture | Document contamination; collect remaining evidence; prioritize network and SIEM logs |\n| Attacker still has active access during investigation | Ongoing compromise detected | Prioritize containment over investigation; implement emergency network isolation |\n| Permission denied accessing system memory | Insufficient forensic tool privileges | Escalate to obtain root\u002Fadmin access; fall back to available log and network data |\n| Backups encrypted or corrupted by ransomware | Attacker targeted backup infrastructure | Identify offline\u002Fair-gapped backups; assess rebuild-from-scratch feasibility |\n\n## Examples\n\n- \"Credential stuffing detected. Use logs in `${CLAUDE_SKILL_DIR}\u002Flogs\u002F` to triage the incident, scope affected accounts, and propose containment steps.\"\n- \"Create an incident response plan for a suspected data breach: list evidence to collect, containment actions, and notification requirements.\"\n- \"Investigate a web shell found at `\u002Fvar\u002Fwww\u002Fhtml\u002Fuploads\u002Fcmd.php`. Trace the initial access vector, identify persistence mechanisms, and produce an IOC list.\"\n\n## Resources\n\n- NIST SP 800-61r2 Computer Security Incident Handling Guide: https:\u002F\u002Fnvlpubs.nist.gov\u002Fnistpubs\u002FSpecialPublications\u002FNIST.SP.800-61r2.pdf\n- SANS Incident Handler's Handbook: https:\u002F\u002Fwww.sans.org\u002Fwhite-papers\u002F33901\u002F\n- CISA Incident Response Guide: https:\u002F\u002Fwww.cisa.gov\u002Fincident-response\n- Volatility Framework (memory forensics): https:\u002F\u002Fwww.volatilityfoundation.org\u002F\n- Autopsy (disk forensics): https:\u002F\u002Fwww.autopsy.com\u002F\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` -- full error handling reference\n- `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` -- additional usage examples\n- https:\u002F\u002Fintentsolutions.io",{"name":5,"author":43,"license":14,"version":44,"description":45,"allowed-tools":46,"compatible-with":47},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Analyze and guide security incident response, investigation, and remediation processes.\nUse when you need to handle security breaches, classify incidents, develop response playbooks, gather forensic evidence, or coordinate remediation efforts.\nTrigger with phrases like \"security incident response\", \"ransomware attack response\", \"data breach investigation\", \"incident playbook\", or \"security forensics\".\n","Read, Write, Edit, Grep, Glob, Bash(log-analysis:*), Bash(forensics:*), Bash(network-trace:*)","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsecurity\u002Fsecurity-incident-responder\u002Fskills\u002Fresponding-to-security-incidents",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 responding-to-security-incidents",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill responding-to-security-incidents",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill responding-to-security-incidents","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsecurity\u002Fsecurity-incident-responder\u002Fskills\u002Fresponding-to-security-incidents\u002FSKILL.md",true,[69,75,81,85,89,93,99],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002FREADME.md","ASSET","资产文件",364,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsecurity\u002Fsecurity-incident-responder\u002Fskills\u002Fresponding-to-security-incidents\u002Fassets\u002FREADME.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Ferrors.md","REFERENCE","参考文档",1105,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsecurity\u002Fsecurity-incident-responder\u002Fskills\u002Fresponding-to-security-incidents\u002Freferences\u002Ferrors.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fexamples.md",221,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsecurity\u002Fsecurity-incident-responder\u002Fskills\u002Fresponding-to-security-incidents\u002Freferences\u002Fexamples.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fimplementation.md",2493,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsecurity\u002Fsecurity-incident-responder\u002Fskills\u002Fresponding-to-security-incidents\u002Freferences\u002Fimplementation.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002FREADME.md",71,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsecurity\u002Fsecurity-incident-responder\u002Fskills\u002Fresponding-to-security-incidents\u002Freferences\u002FREADME.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fevidence_collector.sh","SCRIPT","脚本",2906,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsecurity\u002Fsecurity-incident-responder\u002Fskills\u002Fresponding-to-security-incidents\u002Fscripts\u002Fevidence_collector.sh",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002FREADME.md",423,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsecurity\u002Fsecurity-incident-responder\u002Fskills\u002Fresponding-to-security-incidents\u002Fscripts\u002FREADME.md",[104,141,170,189,209,234],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":120,"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",[110,115],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":155,"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",[147,148,151,154],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},{"categoryNo":149,"categoryName":150,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":152,"categoryName":153,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},[156,157,158,159,122,160,36,161,162,163,164,165,130,131,137,166,167,138,168,169],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":177,"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",[176],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},[178,179,180,20,122,125,130,131,181,30,182,183,184,185,186,138,187,188,169,140],"policy","authoring","apim policy authoring","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":197,"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",[195,196],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},[198,20,199,130,183,200,122,156,201,202,203,204,131,205,138,206,207,208,139,140],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"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",[],[216,217,218,158,219,220,221,222,130,223,224,225,226,227,228,229,230,231,232,233],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":238,"categories":239,"keywords":240,"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",[],[236,241,242,243,244,245,246,30,247,248],"npm","js","calculate","node","math","user","compute","errors"]