[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B95QYWMM2T4N5M3EASC2MK":3,"skill-same:01M7B95QYWMM2T4N5M3EASC2MK":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},"01M7B95QYWMM2T4N5M3EASC2MK","prioritizing-vulnerabilities-with-cvss-scoring",null,"The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity. CVSS v4.0 (r","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\u002Fprioritizing-vulnerabilities-with-cvss-scoring\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fprioritizing-vulnerabilities-with-cvss-scoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: prioritizing-vulnerabilities-with-cvss-scoring\ndescription: The Common Vulnerability Scoring System (CVSS) is the industry standard\n  framework maintained by FIRST (Forum of Incident Response and Security Teams) for\n  assessing vulnerability severity. CVSS v4.0 (r\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- vulnerability-management\n- cve\n- cvss\n- risk\n- prioritization\n- nist\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# Prioritizing Vulnerabilities with CVSS Scoring\n\n## Overview\nThe Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity. CVSS v4.0 (released November 2023) introduces refined metrics for more accurate scoring. This skill covers calculating CVSS scores, interpreting vector strings, and using CVSS alongside contextual factors like EPSS and CISA KEV for effective vulnerability prioritization.\n\n\n## When to Use\n\n- When managing security operations that require prioritizing vulnerabilities with cvss scoring\n- When improving security program maturity and operational processes\n- When establishing standardized procedures for security team workflows\n- When integrating threat intelligence or vulnerability data into operations\n\n## Prerequisites\n- Understanding of common vulnerability types (buffer overflow, injection, XSS, etc.)\n- Familiarity with networking concepts (attack vectors, protocols)\n- Access to NVD (National Vulnerability Database) for CVE lookups\n- Vulnerability scan results requiring prioritization\n\n## Core Concepts\n\n### CVSS v4.0 Metric Groups\n\n#### 1. Base Metrics (Intrinsic Severity)\nRepresent the inherent characteristics of a vulnerability:\n\n**Exploitability Metrics:**\n- **Attack Vector (AV)**: Network (N), Adjacent (A), Local (L), Physical (P)\n- **Attack Complexity (AC)**: Low (L), High (H)\n- **Attack Requirements (AT)**: None (N), Present (P) - NEW in v4.0\n- **Privileges Required (PR)**: None (N), Low (L), High (H)\n- **User Interaction (UI)**: None (N), Passive (P), Active (A) - Expanded in v4.0\n\n**Impact Metrics (Vulnerable System):**\n- **Confidentiality (VC)**: None (N), Low (L), High (H)\n- **Integrity (VI)**: None (N), Low (L), High (H)\n- **Availability (VA)**: None (N), Low (L), High (H)\n\n**Impact Metrics (Subsequent System):**\n- **Confidentiality (SC)**: None (N), Low (L), High (H)\n- **Integrity (SI)**: None (N), Low (L), High (H)\n- **Availability (SA)**: None (N), Low (L), High (H)\n\n#### 2. Threat Metrics (Dynamic Context)\n- **Exploit Maturity (E)**: Attacked (A), POC (P), Unreported (U)\n\n#### 3. Environmental Metrics (Organization-Specific)\nModified versions of base metrics reflecting local deployment context, plus:\n- **Confidentiality Requirement (CR)**: High (H), Medium (M), Low (L)\n- **Integrity Requirement (IR)**: High (H), Medium (M), Low (L)\n- **Availability Requirement (AR)**: High (H), Medium (M), Low (L)\n\n#### 4. Supplemental Metrics (Advisory Information)\n- **Safety (S)**: Present (P), Negligible (X)\n- **Automatable (AU)**: Yes (Y), No (N)\n- **Recovery (R)**: Automatic (A), User (U), Irrecoverable (I)\n- **Value Density (V)**: Diffuse (D), Concentrated (C)\n- **Vulnerability Response Effort (RE)**: Low (L), Moderate (M), High (H)\n- **Provider Urgency (U)**: Red, Amber, Green, Clear\n\n### CVSS v4.0 Severity Ratings\n| Score Range | Severity |\n|-------------|----------|\n| 0.0 | None |\n| 0.1 - 3.9 | Low |\n| 4.0 - 6.9 | Medium |\n| 7.0 - 8.9 | High |\n| 9.0 - 10.0 | Critical |\n\n### CVSS v4.0 Vector String Format\n```\nCVSS:4.0\u002FAV:N\u002FAC:L\u002FAT:N\u002FPR:N\u002FUI:N\u002FVC:H\u002FVI:H\u002FVA:H\u002FSC:N\u002FSI:N\u002FSA:N\n```\nThis example represents a network-exploitable vulnerability requiring no privileges, no user interaction, no attack requirements, with high impact on confidentiality, integrity, and availability of the vulnerable system.\n\n## Workflow\n\n### Step 1: Assess Base Metrics\nFor each vulnerability, evaluate:\n\n```\nExample: CVE-2024-3094 (XZ Utils Backdoor)\n\nAttack Vector:        Network (N)     - Exploitable over network\nAttack Complexity:    High (H)        - Specific conditions required\nAttack Requirements:  Present (P)     - Specific build\u002Fconfig needed\nPrivileges Required:  None (N)        - No authentication needed\nUser Interaction:     None (N)        - No victim action needed\n\nVulnerable System Impact:\n  Confidentiality:    High (H)        - Complete access to SSH keys\n  Integrity:          High (H)        - Arbitrary code execution\n  Availability:       High (H)        - Full system compromise\n\nSubsequent System Impact:\n  Confidentiality:    High (H)        - Lateral movement possible\n  Integrity:          High (H)        - Network-wide compromise\n  Availability:       None (N)        - No downstream availability impact\n\nVector: CVSS:4.0\u002FAV:N\u002FAC:H\u002FAT:P\u002FPR:N\u002FUI:N\u002FVC:H\u002FVI:H\u002FVA:H\u002FSC:H\u002FSI:H\u002FSA:N\n```\n\n### Step 2: Apply Threat Intelligence Context\nEnrich CVSS with real-world threat data:\n\n```\nExploit Maturity:     Attacked (A)    - Active exploitation in the wild\nEPSS Score:           0.94            - 94% probability of exploitation in 30 days\nCISA KEV:            Listed           - Mandatory remediation for federal agencies\n```\n\n### Step 3: Calculate Environmental Score\nAdjust for organizational context:\n\n```\nConfidentiality Req:  High (H)        - Handles PII\u002Ffinancial data\nIntegrity Req:        High (H)        - Critical business process\nAvailability Req:     Medium (M)      - Has DR\u002Ffailover capability\n\nModified Attack Vector: Network (N)   - Internet-facing deployment\n```\n\n### Step 4: Multi-Factor Prioritization Matrix\n\nCombine CVSS with additional prioritization factors:\n\n| Factor | Weight | Source |\n|--------|--------|--------|\n| CVSS Base Score | 25% | NVD\u002FScanner |\n| EPSS Score | 25% | FIRST EPSS API |\n| Asset Criticality | 20% | Asset inventory\u002FCMDB |\n| CISA KEV Listed | 15% | CISA catalog |\n| Network Exposure | 15% | Network segmentation data |\n\n### Step 5: Define Remediation SLAs\n\n| Priority Level | CVSS Range | EPSS | Asset Tier | SLA |\n|---------------|------------|------|------------|-----|\n| P1 - Emergency | 9.0-10.0 | >0.5 | Tier 1 | 24-48 hours |\n| P2 - Critical | 7.0-8.9 | >0.3 | Tier 1-2 | 7 days |\n| P3 - High | 7.0-8.9 | \u003C0.3 | Tier 2-3 | 14 days |\n| P4 - Medium | 4.0-6.9 | Any | Any | 30 days |\n| P5 - Low | 0.1-3.9 | Any | Any | 90 days |\n\n## Best Practices\n1. Never rely solely on CVSS base score for prioritization\n2. Always incorporate threat intelligence (EPSS, KEV, exploit databases)\n3. Maintain accurate asset criticality ratings in your CMDB\n4. Adjust environmental metrics for your specific deployment context\n5. Use CVSS v4.0 vector strings for precise communication between teams\n6. Document scoring rationale for audit trail and consistency\n7. Re-evaluate scores when new threat intelligence becomes available\n8. Train remediation teams on interpreting CVSS metrics and vector strings\n\n## Common Pitfalls\n- Treating CVSS base score as the sole prioritization factor\n- Ignoring environmental metrics that reflect organizational risk\n- Not updating threat metrics when exploit maturity changes\n- Confusing CVSS severity with actual organizational risk\n- Using outdated CVSS v2.0 scores instead of v3.1\u002Fv4.0\n- Over-relying on scanner-provided scores without validation\n\n## Related Skills\n- prioritizing-patches-with-exploit-prediction-scoring\n- implementing-risk-based-vulnerability-management\n- implementing-vulnerability-remediation-sla\n","# Prioritizing Vulnerabilities with CVSS Scoring\n\n## Overview\nThe Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity. CVSS v4.0 (released November 2023) introduces refined metrics for more accurate scoring. This skill covers calculating CVSS scores, interpreting vector strings, and using CVSS alongside contextual factors like EPSS and CISA KEV for effective vulnerability prioritization.\n\n\n## When to Use\n\n- When managing security operations that require prioritizing vulnerabilities with cvss scoring\n- When improving security program maturity and operational processes\n- When establishing standardized procedures for security team workflows\n- When integrating threat intelligence or vulnerability data into operations\n\n## Prerequisites\n- Understanding of common vulnerability types (buffer overflow, injection, XSS, etc.)\n- Familiarity with networking concepts (attack vectors, protocols)\n- Access to NVD (National Vulnerability Database) for CVE lookups\n- Vulnerability scan results requiring prioritization\n\n## Core Concepts\n\n### CVSS v4.0 Metric Groups\n\n#### 1. Base Metrics (Intrinsic Severity)\nRepresent the inherent characteristics of a vulnerability:\n\n**Exploitability Metrics:**\n- **Attack Vector (AV)**: Network (N), Adjacent (A), Local (L), Physical (P)\n- **Attack Complexity (AC)**: Low (L), High (H)\n- **Attack Requirements (AT)**: None (N), Present (P) - NEW in v4.0\n- **Privileges Required (PR)**: None (N), Low (L), High (H)\n- **User Interaction (UI)**: None (N), Passive (P), Active (A) - Expanded in v4.0\n\n**Impact Metrics (Vulnerable System):**\n- **Confidentiality (VC)**: None (N), Low (L), High (H)\n- **Integrity (VI)**: None (N), Low (L), High (H)\n- **Availability (VA)**: None (N), Low (L), High (H)\n\n**Impact Metrics (Subsequent System):**\n- **Confidentiality (SC)**: None (N), Low (L), High (H)\n- **Integrity (SI)**: None (N), Low (L), High (H)\n- **Availability (SA)**: None (N), Low (L), High (H)\n\n#### 2. Threat Metrics (Dynamic Context)\n- **Exploit Maturity (E)**: Attacked (A), POC (P), Unreported (U)\n\n#### 3. Environmental Metrics (Organization-Specific)\nModified versions of base metrics reflecting local deployment context, plus:\n- **Confidentiality Requirement (CR)**: High (H), Medium (M), Low (L)\n- **Integrity Requirement (IR)**: High (H), Medium (M), Low (L)\n- **Availability Requirement (AR)**: High (H), Medium (M), Low (L)\n\n#### 4. Supplemental Metrics (Advisory Information)\n- **Safety (S)**: Present (P), Negligible (X)\n- **Automatable (AU)**: Yes (Y), No (N)\n- **Recovery (R)**: Automatic (A), User (U), Irrecoverable (I)\n- **Value Density (V)**: Diffuse (D), Concentrated (C)\n- **Vulnerability Response Effort (RE)**: Low (L), Moderate (M), High (H)\n- **Provider Urgency (U)**: Red, Amber, Green, Clear\n\n### CVSS v4.0 Severity Ratings\n| Score Range | Severity |\n|-------------|----------|\n| 0.0 | None |\n| 0.1 - 3.9 | Low |\n| 4.0 - 6.9 | Medium |\n| 7.0 - 8.9 | High |\n| 9.0 - 10.0 | Critical |\n\n### CVSS v4.0 Vector String Format\n```\nCVSS:4.0\u002FAV:N\u002FAC:L\u002FAT:N\u002FPR:N\u002FUI:N\u002FVC:H\u002FVI:H\u002FVA:H\u002FSC:N\u002FSI:N\u002FSA:N\n```\nThis example represents a network-exploitable vulnerability requiring no privileges, no user interaction, no attack requirements, with high impact on confidentiality, integrity, and availability of the vulnerable system.\n\n## Workflow\n\n### Step 1: Assess Base Metrics\nFor each vulnerability, evaluate:\n\n```\nExample: CVE-2024-3094 (XZ Utils Backdoor)\n\nAttack Vector:        Network (N)     - Exploitable over network\nAttack Complexity:    High (H)        - Specific conditions required\nAttack Requirements:  Present (P)     - Specific build\u002Fconfig needed\nPrivileges Required:  None (N)        - No authentication needed\nUser Interaction:     None (N)        - No victim action needed\n\nVulnerable System Impact:\n  Confidentiality:    High (H)        - Complete access to SSH keys\n  Integrity:          High (H)        - Arbitrary code execution\n  Availability:       High (H)        - Full system compromise\n\nSubsequent System Impact:\n  Confidentiality:    High (H)        - Lateral movement possible\n  Integrity:          High (H)        - Network-wide compromise\n  Availability:       None (N)        - No downstream availability impact\n\nVector: CVSS:4.0\u002FAV:N\u002FAC:H\u002FAT:P\u002FPR:N\u002FUI:N\u002FVC:H\u002FVI:H\u002FVA:H\u002FSC:H\u002FSI:H\u002FSA:N\n```\n\n### Step 2: Apply Threat Intelligence Context\nEnrich CVSS with real-world threat data:\n\n```\nExploit Maturity:     Attacked (A)    - Active exploitation in the wild\nEPSS Score:           0.94            - 94% probability of exploitation in 30 days\nCISA KEV:            Listed           - Mandatory remediation for federal agencies\n```\n\n### Step 3: Calculate Environmental Score\nAdjust for organizational context:\n\n```\nConfidentiality Req:  High (H)        - Handles PII\u002Ffinancial data\nIntegrity Req:        High (H)        - Critical business process\nAvailability Req:     Medium (M)      - Has DR\u002Ffailover capability\n\nModified Attack Vector: Network (N)   - Internet-facing deployment\n```\n\n### Step 4: Multi-Factor Prioritization Matrix\n\nCombine CVSS with additional prioritization factors:\n\n| Factor | Weight | Source |\n|--------|--------|--------|\n| CVSS Base Score | 25% | NVD\u002FScanner |\n| EPSS Score | 25% | FIRST EPSS API |\n| Asset Criticality | 20% | Asset inventory\u002FCMDB |\n| CISA KEV Listed | 15% | CISA catalog |\n| Network Exposure | 15% | Network segmentation data |\n\n### Step 5: Define Remediation SLAs\n\n| Priority Level | CVSS Range | EPSS | Asset Tier | SLA |\n|---------------|------------|------|------------|-----|\n| P1 - Emergency | 9.0-10.0 | >0.5 | Tier 1 | 24-48 hours |\n| P2 - Critical | 7.0-8.9 | >0.3 | Tier 1-2 | 7 days |\n| P3 - High | 7.0-8.9 | \u003C0.3 | Tier 2-3 | 14 days |\n| P4 - Medium | 4.0-6.9 | Any | Any | 30 days |\n| P5 - Low | 0.1-3.9 | Any | Any | 90 days |\n\n## Best Practices\n1. Never rely solely on CVSS base score for prioritization\n2. Always incorporate threat intelligence (EPSS, KEV, exploit databases)\n3. Maintain accurate asset criticality ratings in your CMDB\n4. Adjust environmental metrics for your specific deployment context\n5. Use CVSS v4.0 vector strings for precise communication between teams\n6. Document scoring rationale for audit trail and consistency\n7. Re-evaluate scores when new threat intelligence becomes available\n8. Train remediation teams on interpreting CVSS metrics and vector strings\n\n## Common Pitfalls\n- Treating CVSS base score as the sole prioritization factor\n- Ignoring environmental metrics that reflect organizational risk\n- Not updating threat metrics when exploit maturity changes\n- Confusing CVSS severity with actual organizational risk\n- Using outdated CVSS v2.0 scores instead of v3.1\u002Fv4.0\n- Over-relying on scanner-provided scores without validation\n\n## Related Skills\n- prioritizing-patches-with-exploit-prediction-scoring\n- implementing-risk-based-vulnerability-management\n- implementing-vulnerability-remediation-sla\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","cvss","risk","prioritization","nist","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\u002Fprioritizing-vulnerabilities-with-cvss-scoring","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 prioritizing-vulnerabilities-with-cvss-scoring",{"tool":55,"command":56},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill prioritizing-vulnerabilities-with-cvss-scoring",{"tool":58,"command":59},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill prioritizing-vulnerabilities-with-cvss-scoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fprioritizing-vulnerabilities-with-cvss-scoring\u002FSKILL.md",true,[63,69,73,79,83,87,93],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"assets\u002Ftemplate.md","ASSET","资产文件",1417,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fprioritizing-vulnerabilities-with-cvss-scoring\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","参考文档",1916,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fprioritizing-vulnerabilities-with-cvss-scoring\u002Freferences\u002Fapi-reference.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fstandards.md",1766,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fprioritizing-vulnerabilities-with-cvss-scoring\u002Freferences\u002Fstandards.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fworkflows.md",2874,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fprioritizing-vulnerabilities-with-cvss-scoring\u002Freferences\u002Fworkflows.md",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fagent.py","SCRIPT","脚本",6031,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fprioritizing-vulnerabilities-with-cvss-scoring\u002Fscripts\u002Fagent.py",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fprocess.py",15396,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fprioritizing-vulnerabilities-with-cvss-scoring\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",[],[]]