[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GXBA2Q755TW91RDFERT54E":3,"skill-same:01M6GXBA2Q755TW91RDFERT54E":88},{"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":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6GXBA2Q755TW91RDFERT54E","deploying-decoy-files-for-ransomware-detection",null,"Deploys canary files (honeytokens) across file systems to detect ransomware encryption activity in real time. Uses strategically placed decoy documents monitored via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware modifies or encrypts them. Activates for requests involving ransomware canary deployment, honeyfile setup, deception-based ransomware detection, or file integrity monitoring for encryption.","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\u002Fdeploying-decoy-files-for-ransomware-detection\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"ransomware","detection","deploying decoy files for ransomware detection","files","detect","cybersecurity","trigger","alerts","across","time","canary deployment","integrity monitoring","canary","file-integrity","canary-files","encryption","monitoring","file","deployment","documents","2026-11-10 10:12:30",false,"---\nname: deploying-decoy-files-for-ransomware-detection\ndescription: >\n  Deploys canary files (honeytokens) across file systems to detect ransomware\n  encryption activity in real time. Uses strategically placed decoy documents\n  monitored via file integrity monitoring or OS-level watchdogs to trigger\n  alerts when ransomware modifies or encrypts them. Activates for requests\n  involving ransomware canary deployment, honeyfile setup, deception-based\n  ransomware detection, or file integrity monitoring for encryption.\ndomain: cybersecurity\nsubdomain: ransomware-defense\ntags: [ransomware, detection, canary-files, honeytokens, deception, file-integrity]\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\n---\n\n# Deploying Decoy Files for Ransomware Detection\n\n## When to Use\n\n- Setting up early-warning detection for ransomware on file servers or endpoints\n- Supplementing EDR\u002FAV with a deception-based detection layer that catches unknown ransomware variants\n- Creating high-fidelity ransomware alerts that have very low false-positive rates (legitimate users have no reason to touch decoy files)\n- Testing ransomware response procedures by validating that canary file modifications trigger the expected alerting pipeline\n- Protecting high-value file shares (finance, HR, legal) with tripwire files that indicate unauthorized encryption activity\n\n**Do not use** decoy files as the sole ransomware defense. They are a detection mechanism, not a prevention mechanism, and should complement backups, EDR, and access controls.\n\n## Prerequisites\n\n- Python 3.8+ with `watchdog` library for cross-platform file system monitoring\n- Administrative access to target file shares or endpoints for canary placement\n- File integrity monitoring (FIM) tool or SIEM integration for alert routing\n- Understanding of target directory structure to place canaries in high-value locations\n- Windows: NTFS change journal or ReadDirectoryChangesW API access\n- Linux: inotify support in kernel (standard in modern kernels)\n\n## Workflow\n\n### Step 1: Design Canary File Strategy\n\nPlan file placement for maximum detection coverage:\n\n```\nCanary File Placement Strategy:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nNaming Convention:\n  - Use names that sort FIRST and LAST alphabetically in each directory\n  - Ransomware typically enumerates directories A-Z or Z-A\n  - Examples: _AAAA_budget_2024.docx, ~zzzz_report_final.xlsx\n\nPlacement Locations:\n  - Root of every file share (\\\\server\\share\\_AAAA_canary.docx)\n  - Desktop, Documents, Downloads on each endpoint\n  - Department-specific shares (Finance, HR, Legal)\n  - Backup staging directories\n  - Home directories of high-privilege accounts\n\nFile Types:\n  - .docx, .xlsx, .pdf (most targeted by ransomware)\n  - .sql, .bak (database files, high value)\n  - Mix of file types to detect ransomware that targets specific extensions\n```\n\n### Step 2: Generate Realistic Canary Files\n\nCreate decoy files with realistic content and metadata:\n\n```python\nimport os\nimport time\n\ndef create_canary_docx(filepath, content=\"Q4 Financial Summary - Confidential\"):\n    \"\"\"Create a realistic .docx canary file using python-docx.\"\"\"\n    from docx import Document\n    doc = Document()\n    doc.add_heading(\"Financial Report - CONFIDENTIAL\", level=1)\n    doc.add_paragraph(content)\n    doc.add_paragraph(f\"Generated: {time.strftime('%Y-%m-%d')}\")\n    doc.save(filepath)\n\ndef create_canary_txt(filepath):\n    \"\"\"Create a simple text canary with known content for hash verification.\"\"\"\n    content = \"CANARY_TOKEN_DO_NOT_MODIFY\\n\"\n    content += f\"Created: {time.strftime('%Y-%m-%dT%H:%M:%S')}\\n\"\n    content += \"This file is monitored for unauthorized changes.\\n\"\n    with open(filepath, \"w\") as f:\n        f.write(content)\n```\n\n### Step 3: Deploy File System Watcher\n\nMonitor canary files for any modification, rename, or deletion:\n\n```python\nfrom watchdog.observers import Observer\nfrom watchdog.events import FileSystemEventHandler\n\nclass CanaryHandler(FileSystemEventHandler):\n    def __init__(self, canary_paths, alert_callback):\n        self.canary_paths = set(canary_paths)\n        self.alert_callback = alert_callback\n\n    def on_modified(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"MODIFIED\", event.src_path)\n\n    def on_deleted(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"DELETED\", event.src_path)\n\n    def on_moved(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"RENAMED\", event.src_path)\n```\n\n### Step 4: Configure Alerting and Response\n\nDefine automated responses when canary files are triggered:\n\n```\nAlert Response Matrix:\n━━━━━━━━━━━━━━━━━━━━━\nEvent: Canary MODIFIED\n  → Severity: CRITICAL\n  → Action: Alert SOC, identify modifying process (PID), isolate endpoint\n\nEvent: Canary DELETED\n  → Severity: HIGH\n  → Action: Alert SOC, check for ransomware note in same directory\n\nEvent: Canary RENAMED (new extension added)\n  → Severity: CRITICAL\n  → Action: Alert SOC, check extension against known ransomware extensions\n  → Automated: Kill modifying process, disable network interface\n\nEvent: Multiple canaries triggered within 60 seconds\n  → Severity: EMERGENCY\n  → Action: Network-wide isolation, activate incident response plan\n```\n\n### Step 5: Validate Detection Coverage\n\nTest that canary files detect actual ransomware behavior:\n\n```bash\n# Simulate ransomware encryption (safe test - modifies canary content)\necho \"ENCRYPTED_BY_TEST\" > \u002Fpath\u002Fto\u002Fcanary\u002F_AAAA_budget.docx\n\n# Simulate ransomware rename (adds extension)\nmv \u002Fpath\u002Fto\u002Fcanary\u002Freport.xlsx \u002Fpath\u002Fto\u002Fcanary\u002Freport.xlsx.locked\n\n# Verify alerts were generated in SIEM\u002Falerting system\n```\n\n## Verification\n\n- Confirm all canary files are present and unmodified using stored hash baselines\n- Verify that modifying any canary file generates an alert within the expected timeframe (under 30 seconds)\n- Test that alert routing to SOC\u002FSIEM is functional with a controlled modification\n- Validate that automated response actions (process kill, network isolation) execute correctly\n- Check that canary files survive normal backup and restore operations\n- Ensure legitimate users and processes are excluded from false-positive alerts (backup agents, AV scans)\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Canary File** | A decoy file placed in a directory that is monitored for any access or modification, serving as a tripwire for unauthorized activity |\n| **Honeytoken** | A broader category of deception artifacts (files, credentials, database records) designed to alert when accessed |\n| **File Integrity Monitoring** | Continuous monitoring of file attributes (hash, size, permissions, timestamps) to detect unauthorized changes |\n| **ReadDirectoryChangesW** | Windows API for monitoring file system changes in a directory; used by the watchdog library on Windows |\n| **inotify** | Linux kernel subsystem for monitoring file system events; provides near-instant notification of file changes |\n\n## Tools & Systems\n\n- **watchdog (Python)**: Cross-platform file system event monitoring library supporting Windows, Linux, and macOS\n- **Canarytokens (Thinkst)**: Free hosted service for generating various types of canary tokens including files, URLs, and DNS tokens\n- **OSSEC\u002FWazuh**: Open-source HIDS with built-in file integrity monitoring and alerting capabilities\n- **Elastic Endpoint**: Uses canary files internally for ransomware protection and key capture\n- **Sysmon**: Windows system monitor that logs file creation events (Event ID 11) for canary file monitoring\n","# Deploying Decoy Files for Ransomware Detection\n\n## When to Use\n\n- Setting up early-warning detection for ransomware on file servers or endpoints\n- Supplementing EDR\u002FAV with a deception-based detection layer that catches unknown ransomware variants\n- Creating high-fidelity ransomware alerts that have very low false-positive rates (legitimate users have no reason to touch decoy files)\n- Testing ransomware response procedures by validating that canary file modifications trigger the expected alerting pipeline\n- Protecting high-value file shares (finance, HR, legal) with tripwire files that indicate unauthorized encryption activity\n\n**Do not use** decoy files as the sole ransomware defense. They are a detection mechanism, not a prevention mechanism, and should complement backups, EDR, and access controls.\n\n## Prerequisites\n\n- Python 3.8+ with `watchdog` library for cross-platform file system monitoring\n- Administrative access to target file shares or endpoints for canary placement\n- File integrity monitoring (FIM) tool or SIEM integration for alert routing\n- Understanding of target directory structure to place canaries in high-value locations\n- Windows: NTFS change journal or ReadDirectoryChangesW API access\n- Linux: inotify support in kernel (standard in modern kernels)\n\n## Workflow\n\n### Step 1: Design Canary File Strategy\n\nPlan file placement for maximum detection coverage:\n\n```\nCanary File Placement Strategy:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nNaming Convention:\n  - Use names that sort FIRST and LAST alphabetically in each directory\n  - Ransomware typically enumerates directories A-Z or Z-A\n  - Examples: _AAAA_budget_2024.docx, ~zzzz_report_final.xlsx\n\nPlacement Locations:\n  - Root of every file share (\\\\server\\share\\_AAAA_canary.docx)\n  - Desktop, Documents, Downloads on each endpoint\n  - Department-specific shares (Finance, HR, Legal)\n  - Backup staging directories\n  - Home directories of high-privilege accounts\n\nFile Types:\n  - .docx, .xlsx, .pdf (most targeted by ransomware)\n  - .sql, .bak (database files, high value)\n  - Mix of file types to detect ransomware that targets specific extensions\n```\n\n### Step 2: Generate Realistic Canary Files\n\nCreate decoy files with realistic content and metadata:\n\n```python\nimport os\nimport time\n\ndef create_canary_docx(filepath, content=\"Q4 Financial Summary - Confidential\"):\n    \"\"\"Create a realistic .docx canary file using python-docx.\"\"\"\n    from docx import Document\n    doc = Document()\n    doc.add_heading(\"Financial Report - CONFIDENTIAL\", level=1)\n    doc.add_paragraph(content)\n    doc.add_paragraph(f\"Generated: {time.strftime('%Y-%m-%d')}\")\n    doc.save(filepath)\n\ndef create_canary_txt(filepath):\n    \"\"\"Create a simple text canary with known content for hash verification.\"\"\"\n    content = \"CANARY_TOKEN_DO_NOT_MODIFY\\n\"\n    content += f\"Created: {time.strftime('%Y-%m-%dT%H:%M:%S')}\\n\"\n    content += \"This file is monitored for unauthorized changes.\\n\"\n    with open(filepath, \"w\") as f:\n        f.write(content)\n```\n\n### Step 3: Deploy File System Watcher\n\nMonitor canary files for any modification, rename, or deletion:\n\n```python\nfrom watchdog.observers import Observer\nfrom watchdog.events import FileSystemEventHandler\n\nclass CanaryHandler(FileSystemEventHandler):\n    def __init__(self, canary_paths, alert_callback):\n        self.canary_paths = set(canary_paths)\n        self.alert_callback = alert_callback\n\n    def on_modified(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"MODIFIED\", event.src_path)\n\n    def on_deleted(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"DELETED\", event.src_path)\n\n    def on_moved(self, event):\n        if event.src_path in self.canary_paths:\n            self.alert_callback(\"RENAMED\", event.src_path)\n```\n\n### Step 4: Configure Alerting and Response\n\nDefine automated responses when canary files are triggered:\n\n```\nAlert Response Matrix:\n━━━━━━━━━━━━━━━━━━━━━\nEvent: Canary MODIFIED\n  → Severity: CRITICAL\n  → Action: Alert SOC, identify modifying process (PID), isolate endpoint\n\nEvent: Canary DELETED\n  → Severity: HIGH\n  → Action: Alert SOC, check for ransomware note in same directory\n\nEvent: Canary RENAMED (new extension added)\n  → Severity: CRITICAL\n  → Action: Alert SOC, check extension against known ransomware extensions\n  → Automated: Kill modifying process, disable network interface\n\nEvent: Multiple canaries triggered within 60 seconds\n  → Severity: EMERGENCY\n  → Action: Network-wide isolation, activate incident response plan\n```\n\n### Step 5: Validate Detection Coverage\n\nTest that canary files detect actual ransomware behavior:\n\n```bash\n# Simulate ransomware encryption (safe test - modifies canary content)\necho \"ENCRYPTED_BY_TEST\" > \u002Fpath\u002Fto\u002Fcanary\u002F_AAAA_budget.docx\n\n# Simulate ransomware rename (adds extension)\nmv \u002Fpath\u002Fto\u002Fcanary\u002Freport.xlsx \u002Fpath\u002Fto\u002Fcanary\u002Freport.xlsx.locked\n\n# Verify alerts were generated in SIEM\u002Falerting system\n```\n\n## Verification\n\n- Confirm all canary files are present and unmodified using stored hash baselines\n- Verify that modifying any canary file generates an alert within the expected timeframe (under 30 seconds)\n- Test that alert routing to SOC\u002FSIEM is functional with a controlled modification\n- Validate that automated response actions (process kill, network isolation) execute correctly\n- Check that canary files survive normal backup and restore operations\n- Ensure legitimate users and processes are excluded from false-positive alerts (backup agents, AV scans)\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Canary File** | A decoy file placed in a directory that is monitored for any access or modification, serving as a tripwire for unauthorized activity |\n| **Honeytoken** | A broader category of deception artifacts (files, credentials, database records) designed to alert when accessed |\n| **File Integrity Monitoring** | Continuous monitoring of file attributes (hash, size, permissions, timestamps) to detect unauthorized changes |\n| **ReadDirectoryChangesW** | Windows API for monitoring file system changes in a directory; used by the watchdog library on Windows |\n| **inotify** | Linux kernel subsystem for monitoring file system events; provides near-instant notification of file changes |\n\n## Tools & Systems\n\n- **watchdog (Python)**: Cross-platform file system event monitoring library supporting Windows, Linux, and macOS\n- **Canarytokens (Thinkst)**: Free hosted service for generating various types of canary tokens including files, URLs, and DNS tokens\n- **OSSEC\u002FWazuh**: Open-source HIDS with built-in file integrity monitoring and alerting capabilities\n- **Elastic Endpoint**: Uses canary files internally for ransomware protection and key capture\n- **Sysmon**: Windows system monitor that logs file creation events (Event ID 11) for canary file monitoring\n",{"name":5,"tags":43,"author":46,"domain":23,"license":14,"version":47,"subdomain":48,"description":49},[18,19,32,44,45,31],"honeytokens","deception","mahipal","1.0.0","ransomware-defense","Deploys canary files (honeytokens) across file systems to detect ransomware encryption activity in real time. Uses strategically placed decoy documents monitored via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware modifies or encrypts them. Activates for requests involving ransomware canary deployment, honeyfile setup, deception-based ransomware detection, or file integrity monitoring for encryption.\n","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add micsapp\u002Fmicstec-skills --skill deploying-decoy-files-for-ransomware-detection",{"tool":63,"command":64},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill deploying-decoy-files-for-ransomware-detection",{"tool":66,"command":67},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill deploying-decoy-files-for-ransomware-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection\u002FSKILL.md",true,[71,76,82],{"path":72,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection\u002FLICENSE",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fapi-reference.md","REFERENCE","参考文档",3201,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection\u002Freferences\u002Fapi-reference.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fagent.py","SCRIPT","脚本",9424,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fdeploying-decoy-files-for-ransomware-detection\u002Fscripts\u002Fagent.py",[89,127,156,177,197,222],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":106,"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",[96,101],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126],"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":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":141,"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",[133,134,137,140],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":135,"categoryName":136,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":138,"categoryName":139,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[36,142,143,144,108,145,146,147,148,149,150,151,116,117,123,152,153,124,154,155],"apiops deployment","workflows","azure devops","infrastructure","code","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"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",[162],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},[164,165,166,167,108,111,116,117,168,169,170,171,172,173,174,124,175,176,155,126],"policy","authoring","apim policy authoring","security","access","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":185,"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",[183,184],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[186,167,187,116,171,188,108,36,189,190,191,192,117,193,124,194,195,196,125,126],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":203,"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",[],[204,205,206,143,207,208,209,210,116,211,212,213,214,215,216,217,218,219,220,221],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":228,"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",[],[224,229,230,231,232,233,234,169,235,236],"npm","js","calculate","node","math","user","compute","errors"]