[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GWM2C19CJPWTY83NMRKS90":3,"skill-same:01M6GWM2C19CJPWTY83NMRKS90":91},{"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":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6GWM2C19CJPWTY83NMRKS90","analyzing-indicators-of-compromise",null,"Analyzes indicators of compromise (IOCs) including IP addresses, domains, file hashes, URLs, and email artifacts to determine maliciousness confidence, campaign attribution, and blocking priority. Use when triaging IOCs from phishing emails, security alerts, or external threat feeds; enriching raw IOCs with multi-source intelligence; or making block\u002Fmonitor\u002Fwhitelist decisions. Activates for requests involving VirusTotal, AbuseIPDB, MalwareBazaar, MISP, or IOC enrichment pipelines.","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fanalyzing-indicators-of-compromise\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"analyzing indicators of compromise","analyzing","indicators","NIST","addresses","domains","ip","alerts","intelligence","campaign","threat","feeds","security","NIST-CSF","ioc","threat-intelligence","email","campaign attribution","security alerts","cybersecurity","2026-11-10 10:12:30",false,"---\nname: analyzing-indicators-of-compromise\ndescription: >\n  Analyzes indicators of compromise (IOCs) including IP addresses, domains, file hashes, URLs,\n  and email artifacts to determine maliciousness confidence, campaign attribution, and blocking\n  priority. Use when triaging IOCs from phishing emails, security alerts, or external threat feeds;\n  enriching raw IOCs with multi-source intelligence; or making block\u002Fmonitor\u002Fwhitelist decisions.\n  Activates for requests involving VirusTotal, AbuseIPDB, MalwareBazaar, MISP, or IOC enrichment pipelines.\ndomain: cybersecurity\nsubdomain: threat-intelligence\ntags: [IOC, VirusTotal, AbuseIPDB, MalwareBazaar, MISP, threat-intelligence, STIX, NIST-CSF]\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\n---\n# Analyzing Indicators of Compromise\n\n## When to Use\n\nUse this skill when:\n- A phishing email or alert generates IOCs (URLs, IP addresses, file hashes) requiring rapid triage\n- Automated feeds deliver bulk IOCs that need confidence scoring before ingestion into blocking controls\n- An incident investigation requires contextual enrichment of observed network artifacts\n\n**Do not use** this skill in isolation for high-stakes blocking decisions — always combine automated enrichment with analyst judgment, especially for shared infrastructure (CDNs, cloud providers).\n\n## Prerequisites\n\n- VirusTotal API key (free or Enterprise) for multi-AV and sandbox lookup\n- AbuseIPDB API key for IP reputation checks\n- MISP instance or TIP for cross-referencing against known campaigns\n- Python with `requests` and `vt-py` libraries, or SOAR platform with pre-built connectors\n\n## Workflow\n\n### Step 1: Normalize and Classify IOC Types\n\nBefore enriching, classify each IOC:\n- **IPv4\u002FIPv6 address**: Check if RFC 1918 private (skip external enrichment), validate format\n- **Domain\u002FFQDN**: Defang for safe handling (`evil[.]com`), extract registered domain via tldextract\n- **URL**: Extract domain + path separately; check for redirectors\n- **File hash**: Identify hash type (MD5\u002FSHA-1\u002FSHA-256); prefer SHA-256 for uniqueness\n- **Email address**: Split into domain (check MX\u002FDMARC) and local part for pattern analysis\n\nDefang IOCs in documentation (replace `.` with `[.]` and `:\u002F\u002F` with `[:\u002F\u002F]`) to prevent accidental clicks.\n\n### Step 2: Multi-Source Enrichment\n\n**VirusTotal (file hash, URL, IP, domain)**:\n```python\nimport vt\n\nclient = vt.Client(\"YOUR_VT_API_KEY\")\n\n# File hash lookup\nfile_obj = client.get_object(f\"\u002Ffiles\u002F{sha256_hash}\")\ndetections = file_obj.last_analysis_stats\nprint(f\"Malicious: {detections['malicious']}\u002F{sum(detections.values())}\")\n\n# Domain analysis\ndomain_obj = client.get_object(f\"\u002Fdomains\u002F{domain}\")\nprint(domain_obj.last_analysis_stats)\nprint(domain_obj.reputation)\nclient.close()\n```\n\n**AbuseIPDB (IP addresses)**:\n```python\nimport requests\n\nresponse = requests.get(\n    \"https:\u002F\u002Fapi.abuseipdb.com\u002Fapi\u002Fv2\u002Fcheck\",\n    headers={\"Key\": \"YOUR_KEY\", \"Accept\": \"application\u002Fjson\"},\n    params={\"ipAddress\": \"1.2.3.4\", \"maxAgeInDays\": 90}\n)\ndata = response.json()[\"data\"]\nprint(f\"Confidence: {data['abuseConfidenceScore']}%, Reports: {data['totalReports']}\")\n```\n\n**MalwareBazaar (file hashes)**:\n```python\nresponse = requests.post(\n    \"https:\u002F\u002Fmb-api.abuse.ch\u002Fapi\u002Fv1\u002F\",\n    data={\"query\": \"get_info\", \"hash\": sha256_hash}\n)\nresult = response.json()\nif result[\"query_status\"] == \"ok\":\n    print(result[\"data\"][0][\"tags\"], result[\"data\"][0][\"signature\"])\n```\n\n### Step 3: Contextualize with Campaign Attribution\n\nQuery MISP for existing events matching the IOC:\n```python\nfrom pymisp import PyMISP\n\nmisp = PyMISP(\"https:\u002F\u002Fmisp.example.com\", \"API_KEY\")\nresults = misp.search(value=\"evil-domain.com\", type_attribute=\"domain\")\nfor event in results:\n    print(event[\"Event\"][\"info\"], event[\"Event\"][\"threat_level_id\"])\n```\n\nCheck Shodan for IP context (hosting provider, open ports, banners) to identify if the IP belongs to bulletproof hosting or a legitimate cloud provider (false positive risk).\n\n### Step 4: Assign Confidence Score and Disposition\n\nApply a tiered decision framework:\n- **Block (High Confidence ≥ 70%)**: ≥15 AV detections on VT, AbuseIPDB score ≥70, matches known malware family or campaign\n- **Monitor\u002FAlert (Medium 40–69%)**: 5–14 AV detections, moderate AbuseIPDB score, no campaign attribution\n- **Whitelist\u002FInvestigate (Low \u003C40%)**: ≤4 AV detections, no abuse reports, legitimate service (Google, Cloudflare CDN IPs)\n- **False Positive**: Legitimate business service incorrectly flagged; document and exclude from future alerts\n\n### Step 5: Document and Distribute\n\nRecord findings in TIP\u002FMISP with:\n- All enrichment data collected (timestamps, source, score)\n- Disposition decision and rationale\n- Blocking actions taken (firewall, proxy, DNS sinkhole)\n- Related incident ticket number\n\nExport to STIX indicator object with confidence field set appropriately.\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **IOC** | Indicator of Compromise — observable network or host artifact indicating potential compromise |\n| **Enrichment** | Process of adding contextual data to a raw IOC from multiple intelligence sources |\n| **Defanging** | Modifying IOCs (replacing `.` with `[.]`) to prevent accidental activation in documentation |\n| **False Positive Rate** | Percentage of benign artifacts incorrectly flagged as malicious; critical for tuning block thresholds |\n| **Sinkhole** | DNS server redirecting malicious domain lookups to a benign IP for detection without blocking traffic entirely |\n| **TTL** | Time-to-live for an IOC in blocking controls; IP indicators should expire after 30 days, domains after 90 days |\n\n## Tools & Systems\n\n- **VirusTotal**: Multi-engine malware scanner and threat intelligence platform with 70+ AV engines, sandbox reports, and community comments\n- **AbuseIPDB**: Community-maintained IP reputation database with 90-day abuse report history\n- **MalwareBazaar (abuse.ch)**: Free malware hash repository with YARA rule associations and malware family tagging\n- **URLScan.io**: Free URL analysis service that captures screenshots, DOM, and network requests for phishing URL triage\n- **Shodan**: Internet-wide scan data providing hosting provider, open ports, and banner information for IP enrichment\n\n## Common Pitfalls\n\n- **Blocking shared infrastructure**: CDN IPs (Cloudflare 104.21.x.x, AWS CloudFront) may legitimately host malicious content but blocking the IP disrupts thousands of legitimate sites.\n- **VT score obsession**: Low VT detection count does not mean benign — zero-day malware and custom APT tools often score 0 initially. Check sandbox behavior, MISP, and passive DNS.\n- **Missing defanging**: Pasting live IOCs in emails or Confluence docs can trigger automated URL scanners or phishing tools.\n- **No expiration policy**: IOCs without TTLs accumulate in blocklists indefinitely, generating false positives as infrastructure is repurposed by legitimate users.\n- **Over-relying on single source**: VirusTotal aggregates AV opinions — all may be wrong or lag behind emerging malware. Use 3+ independent sources for high-stakes decisions.\n","# Analyzing Indicators of Compromise\n\n## When to Use\n\nUse this skill when:\n- A phishing email or alert generates IOCs (URLs, IP addresses, file hashes) requiring rapid triage\n- Automated feeds deliver bulk IOCs that need confidence scoring before ingestion into blocking controls\n- An incident investigation requires contextual enrichment of observed network artifacts\n\n**Do not use** this skill in isolation for high-stakes blocking decisions — always combine automated enrichment with analyst judgment, especially for shared infrastructure (CDNs, cloud providers).\n\n## Prerequisites\n\n- VirusTotal API key (free or Enterprise) for multi-AV and sandbox lookup\n- AbuseIPDB API key for IP reputation checks\n- MISP instance or TIP for cross-referencing against known campaigns\n- Python with `requests` and `vt-py` libraries, or SOAR platform with pre-built connectors\n\n## Workflow\n\n### Step 1: Normalize and Classify IOC Types\n\nBefore enriching, classify each IOC:\n- **IPv4\u002FIPv6 address**: Check if RFC 1918 private (skip external enrichment), validate format\n- **Domain\u002FFQDN**: Defang for safe handling (`evil[.]com`), extract registered domain via tldextract\n- **URL**: Extract domain + path separately; check for redirectors\n- **File hash**: Identify hash type (MD5\u002FSHA-1\u002FSHA-256); prefer SHA-256 for uniqueness\n- **Email address**: Split into domain (check MX\u002FDMARC) and local part for pattern analysis\n\nDefang IOCs in documentation (replace `.` with `[.]` and `:\u002F\u002F` with `[:\u002F\u002F]`) to prevent accidental clicks.\n\n### Step 2: Multi-Source Enrichment\n\n**VirusTotal (file hash, URL, IP, domain)**:\n```python\nimport vt\n\nclient = vt.Client(\"YOUR_VT_API_KEY\")\n\n# File hash lookup\nfile_obj = client.get_object(f\"\u002Ffiles\u002F{sha256_hash}\")\ndetections = file_obj.last_analysis_stats\nprint(f\"Malicious: {detections['malicious']}\u002F{sum(detections.values())}\")\n\n# Domain analysis\ndomain_obj = client.get_object(f\"\u002Fdomains\u002F{domain}\")\nprint(domain_obj.last_analysis_stats)\nprint(domain_obj.reputation)\nclient.close()\n```\n\n**AbuseIPDB (IP addresses)**:\n```python\nimport requests\n\nresponse = requests.get(\n    \"https:\u002F\u002Fapi.abuseipdb.com\u002Fapi\u002Fv2\u002Fcheck\",\n    headers={\"Key\": \"YOUR_KEY\", \"Accept\": \"application\u002Fjson\"},\n    params={\"ipAddress\": \"1.2.3.4\", \"maxAgeInDays\": 90}\n)\ndata = response.json()[\"data\"]\nprint(f\"Confidence: {data['abuseConfidenceScore']}%, Reports: {data['totalReports']}\")\n```\n\n**MalwareBazaar (file hashes)**:\n```python\nresponse = requests.post(\n    \"https:\u002F\u002Fmb-api.abuse.ch\u002Fapi\u002Fv1\u002F\",\n    data={\"query\": \"get_info\", \"hash\": sha256_hash}\n)\nresult = response.json()\nif result[\"query_status\"] == \"ok\":\n    print(result[\"data\"][0][\"tags\"], result[\"data\"][0][\"signature\"])\n```\n\n### Step 3: Contextualize with Campaign Attribution\n\nQuery MISP for existing events matching the IOC:\n```python\nfrom pymisp import PyMISP\n\nmisp = PyMISP(\"https:\u002F\u002Fmisp.example.com\", \"API_KEY\")\nresults = misp.search(value=\"evil-domain.com\", type_attribute=\"domain\")\nfor event in results:\n    print(event[\"Event\"][\"info\"], event[\"Event\"][\"threat_level_id\"])\n```\n\nCheck Shodan for IP context (hosting provider, open ports, banners) to identify if the IP belongs to bulletproof hosting or a legitimate cloud provider (false positive risk).\n\n### Step 4: Assign Confidence Score and Disposition\n\nApply a tiered decision framework:\n- **Block (High Confidence ≥ 70%)**: ≥15 AV detections on VT, AbuseIPDB score ≥70, matches known malware family or campaign\n- **Monitor\u002FAlert (Medium 40–69%)**: 5–14 AV detections, moderate AbuseIPDB score, no campaign attribution\n- **Whitelist\u002FInvestigate (Low \u003C40%)**: ≤4 AV detections, no abuse reports, legitimate service (Google, Cloudflare CDN IPs)\n- **False Positive**: Legitimate business service incorrectly flagged; document and exclude from future alerts\n\n### Step 5: Document and Distribute\n\nRecord findings in TIP\u002FMISP with:\n- All enrichment data collected (timestamps, source, score)\n- Disposition decision and rationale\n- Blocking actions taken (firewall, proxy, DNS sinkhole)\n- Related incident ticket number\n\nExport to STIX indicator object with confidence field set appropriately.\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **IOC** | Indicator of Compromise — observable network or host artifact indicating potential compromise |\n| **Enrichment** | Process of adding contextual data to a raw IOC from multiple intelligence sources |\n| **Defanging** | Modifying IOCs (replacing `.` with `[.]`) to prevent accidental activation in documentation |\n| **False Positive Rate** | Percentage of benign artifacts incorrectly flagged as malicious; critical for tuning block thresholds |\n| **Sinkhole** | DNS server redirecting malicious domain lookups to a benign IP for detection without blocking traffic entirely |\n| **TTL** | Time-to-live for an IOC in blocking controls; IP indicators should expire after 30 days, domains after 90 days |\n\n## Tools & Systems\n\n- **VirusTotal**: Multi-engine malware scanner and threat intelligence platform with 70+ AV engines, sandbox reports, and community comments\n- **AbuseIPDB**: Community-maintained IP reputation database with 90-day abuse report history\n- **MalwareBazaar (abuse.ch)**: Free malware hash repository with YARA rule associations and malware family tagging\n- **URLScan.io**: Free URL analysis service that captures screenshots, DOM, and network requests for phishing URL triage\n- **Shodan**: Internet-wide scan data providing hosting provider, open ports, and banner information for IP enrichment\n\n## Common Pitfalls\n\n- **Blocking shared infrastructure**: CDN IPs (Cloudflare 104.21.x.x, AWS CloudFront) may legitimately host malicious content but blocking the IP disrupts thousands of legitimate sites.\n- **VT score obsession**: Low VT detection count does not mean benign — zero-day malware and custom APT tools often score 0 initially. Check sandbox behavior, MISP, and passive DNS.\n- **Missing defanging**: Pasting live IOCs in emails or Confluence docs can trigger automated URL scanners or phishing tools.\n- **No expiration policy**: IOCs without TTLs accumulate in blocklists indefinitely, generating false positives as infrastructure is repurposed by legitimate users.\n- **Over-relying on single source**: VirusTotal aggregates AV opinions — all may be wrong or lag behind emerging malware. Use 3+ independent sources for high-stakes decisions.\n",{"name":5,"tags":43,"author":50,"domain":37,"license":14,"version":51,"subdomain":33,"description":52},[44,45,46,47,48,33,49,31],"IOC","VirusTotal","AbuseIPDB","MalwareBazaar","MISP","STIX","mahipal","1.0.0","Analyzes indicators of compromise (IOCs) including IP addresses, domains, file hashes, URLs, and email artifacts to determine maliciousness confidence, campaign attribution, and blocking priority. Use when triaging IOCs from phishing emails, security alerts, or external threat feeds; enriching raw IOCs with multi-source intelligence; or making block\u002Fmonitor\u002Fwhitelist decisions. Activates for requests involving VirusTotal, AbuseIPDB, MalwareBazaar, MISP, or IOC enrichment pipelines.\n","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","_universal\u002Fcybersecurity-skills\u002Fskills\u002Fanalyzing-indicators-of-compromise",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add micsapp\u002Fmicstec-skills --skill analyzing-indicators-of-compromise",{"tool":66,"command":67},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill analyzing-indicators-of-compromise",{"tool":69,"command":70},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill analyzing-indicators-of-compromise","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fanalyzing-indicators-of-compromise\u002FSKILL.md",true,[74,79,85],{"path":75,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fanalyzing-indicators-of-compromise\u002FLICENSE",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fapi-reference.md","REFERENCE","参考文档",2926,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fanalyzing-indicators-of-compromise\u002Freferences\u002Fapi-reference.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fagent.py","SCRIPT","脚本",8985,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fanalyzing-indicators-of-compromise\u002Fscripts\u002Fagent.py",[92,130,160,180,200,225],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":109,"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.","MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[99,104],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129],"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":144,"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",[136,137,140,143],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":138,"categoryName":139,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":141,"categoryName":142,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[145,146,147,148,111,149,150,151,152,153,154,155,119,120,126,156,157,127,158,159],"deployment","apiops deployment","workflows","azure devops","infrastructure","code","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"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",[166],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},[168,169,170,30,111,114,119,120,171,172,173,174,175,176,177,127,178,179,159,129],"policy","authoring","apim policy authoring","access","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":188,"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",[186,187],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[189,30,190,119,174,191,111,145,192,193,194,195,120,196,127,197,198,199,128,129],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":206,"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",[],[207,208,209,147,210,211,212,213,119,214,215,216,217,218,219,220,221,222,223,224],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":231,"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",[],[227,232,233,234,235,236,237,172,238,239],"npm","js","calculate","node","math","user","compute","errors"]