[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B5GKPX2VT5G5M8J2FCX4WD":3,"skill-same:01M7B5GKPX2VT5G5M8J2FCX4WD":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},"01M7B5GKPX2VT5G5M8J2FCX4WD","conducting-post-incident-lessons-learned",null,"Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.","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\u002Fconducting-post-incident-lessons-learned\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-post-incident-lessons-learned\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conducting-post-incident-lessons-learned\ndescription: Facilitate structured post-incident reviews to identify root causes,\n  document what worked and failed, and produce actionable recommendations to improve\n  future incident response.\ndomain: cybersecurity\nsubdomain: incident-response\ntags:\n- incident-response\n- lessons-learned\n- post-incident\n- after-action-review\n- process-improvement\nmitre_attack:\n- T1566\n- T1486\n- T1059\n- T1078\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.MA-01\n- RS.MA-02\n- RS.AN-03\n- RC.RP-01\n---\n\n# Conducting Post-Incident Lessons Learned\n\n## When to Use\n- After any security incident has been fully resolved and recovery completed\n- Following tabletop exercises or IR simulations\n- After significant near-miss events\n- Quarterly review of accumulated incident trends\n- When IR playbooks need updating based on real-world experience\n\n## Prerequisites\n- Incident fully resolved (containment, eradication, recovery complete)\n- Incident timeline and documentation gathered\n- All incident responders available for review session\n- Meeting space for collaborative discussion\n- Incident ticketing system data for metrics analysis\n\n## Workflow\n\n### Step 1: Gather Incident Data\n```bash\n# Export incident timeline from ticketing system\ncurl -s \"https:\u002F\u002Fthehive.local\u002Fapi\u002Fv1\u002Fcase\u002F$CASE_ID\u002Ftimeline\" \\\n  -H \"Authorization: Bearer $THEHIVE_API_KEY\" | jq '.' > incident_timeline.json\n\n# Extract detection and response metrics from SIEM\nindex=notable incident_id=\"IR-2024-042\"\n| stats min(_time) as first_alert, max(_time) as last_alert,\n  count as total_alerts, dc(src) as unique_sources\n\n# Compile all responder actions and timestamps\ngrep -E \"timestamp|action|analyst\" \u002Fvar\u002Flog\u002Fir\u002FIR-2024-042\u002F*.json | \\\n  python3 -m json.tool > compiled_actions.json\n```\n\n### Step 2: Conduct Blameless Post-Mortem Meeting\n```\nStructured Agenda (90 minutes):\n1. Incident summary (5 min) - Factual overview\n2. Timeline walkthrough (20 min) - Chronological events\n3. What worked well (15 min) - Positive outcomes\n4. What needs improvement (15 min) - Gaps and failures\n5. Root cause analysis (15 min) - 5 Whys or fishbone\n6. Action items (10 min) - Specific improvements with owners\n7. Playbook updates (10 min) - Changes to IR procedures\n\nBlameless Principles:\n- Focus on systems and processes, not individuals\n- Assume best intentions with available information\n- Seek to understand, not to blame\n```\n\n### Step 3: Perform Root Cause Analysis\n```bash\n# 5 Whys analysis example:\n# Why 1: Why did ransomware encrypt production servers?\n#   Answer: Attacker had domain admin credentials\n# Why 2: Why did attacker have domain admin credentials?\n#   Answer: Kerberoasted a service account and cracked it\n# Why 3: Why was the service account password crackable?\n#   Answer: Used a 12-character dictionary-based password\n# Why 4: Why was the service account password weak?\n#   Answer: No enforcement of service account password policy\n# Why 5: Why was there no service account password policy?\n#   Answer: PAM was not implemented for service accounts\n# ROOT CAUSE: Lack of privileged access management\n```\n\n### Step 4: Calculate Response Metrics\n```python\nfrom datetime import datetime\nevents = {\n    'compromise': '2024-01-10 14:00:00',\n    'detection': '2024-01-15 08:30:00',\n    'triage': '2024-01-15 08:45:00',\n    'containment': '2024-01-15 09:30:00',\n    'eradication': '2024-01-16 14:00:00',\n    'recovery': '2024-01-18 16:00:00',\n    'closure': '2024-01-25 10:00:00',\n}\nfmt = '%Y-%m-%d %H:%M:%S'\ntimes = {k: datetime.strptime(v, fmt) for k, v in events.items()}\nprint(f\"Dwell Time: {times['detection'] - times['compromise']}\")\nprint(f\"MTTD: {times['triage'] - times['detection']}\")\nprint(f\"MTTC: {times['containment'] - times['detection']}\")\nprint(f\"MTTR: {times['recovery'] - times['eradication']}\")\nprint(f\"Total Duration: {times['closure'] - times['detection']}\")\n```\n\n### Step 5: Document Findings and Create Action Items\n```bash\n# Create tracked action items in project management\ncurl -X POST \"https:\u002F\u002Fjira.local\u002Frest\u002Fapi\u002F2\u002Fissue\" \\\n  -H \"Authorization: Bearer $JIRA_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"fields\": {\n      \"project\": {\"key\": \"SEC\"},\n      \"summary\": \"Implement PAM for service accounts (IR-2024-042)\",\n      \"issuetype\": {\"name\": \"Task\"},\n      \"priority\": {\"name\": \"High\"},\n      \"assignee\": {\"name\": \"security_engineer\"},\n      \"duedate\": \"2024-03-15\"\n    }\n  }'\n```\n\n### Step 6: Update Playbooks and Detection Rules\n```yaml\n# New Sigma detection rule based on incident learnings\ntitle: Kerberoasting Activity Detected\nstatus: stable\ndescription: Detects Kerberoasting based on IR-2024-042 lessons\nlogsource:\n  product: windows\n  service: security\ndetection:\n  selection:\n    EventID: 4769\n    TicketEncryptionType: '0x17'\n  condition: selection\nlevel: high\ntags:\n  - attack.credential_access\n  - attack.t1558.003\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Blameless Post-Mortem | Reviewing incidents focusing on systems, not blaming individuals |\n| Root Cause Analysis | Identifying the fundamental reason the incident occurred |\n| 5 Whys | Iterative questioning technique to find root cause |\n| MTTD | Mean Time to Detect - time from compromise to detection |\n| MTTC | Mean Time to Contain - time from detection to containment |\n| MTTR | Mean Time to Recover - time from eradication to full recovery |\n| Continuous Improvement | Iterating on IR processes based on real incident data |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| TheHive\u002FServiceNow | Incident timeline and documentation |\n| Jira\u002FAzure DevOps | Action item tracking |\n| Confluence\u002FSharePoint | Lessons learned documentation |\n| Splunk\u002FElastic | Incident metrics and detection improvement |\n| Sigma | Detection rule development |\n\n## Common Scenarios\n\n1. **Ransomware Post-Mortem**: Review entire kill chain from initial access to encryption. Identify detection gaps and backup failures.\n2. **Phishing Campaign Review**: Analyze why users clicked, why email filters missed it, and how to improve training.\n3. **Cloud Misconfiguration Incident**: Review IaC pipeline, CSPM coverage, and change management process.\n4. **Insider Threat Review**: Examine DLP effectiveness, access control gaps, and user monitoring capabilities.\n5. **Third-Party Breach Impact**: Review vendor risk assessment process and data sharing agreements.\n\n## Output Format\n- Post-incident review meeting minutes\n- Root cause analysis document\n- Incident metrics report (MTTD, MTTC, MTTR)\n- Action items list with owners and deadlines\n- Updated IR playbooks and detection rules\n- Executive summary for leadership\n","# Conducting Post-Incident Lessons Learned\n\n## When to Use\n- After any security incident has been fully resolved and recovery completed\n- Following tabletop exercises or IR simulations\n- After significant near-miss events\n- Quarterly review of accumulated incident trends\n- When IR playbooks need updating based on real-world experience\n\n## Prerequisites\n- Incident fully resolved (containment, eradication, recovery complete)\n- Incident timeline and documentation gathered\n- All incident responders available for review session\n- Meeting space for collaborative discussion\n- Incident ticketing system data for metrics analysis\n\n## Workflow\n\n### Step 1: Gather Incident Data\n```bash\n# Export incident timeline from ticketing system\ncurl -s \"https:\u002F\u002Fthehive.local\u002Fapi\u002Fv1\u002Fcase\u002F$CASE_ID\u002Ftimeline\" \\\n  -H \"Authorization: Bearer $THEHIVE_API_KEY\" | jq '.' > incident_timeline.json\n\n# Extract detection and response metrics from SIEM\nindex=notable incident_id=\"IR-2024-042\"\n| stats min(_time) as first_alert, max(_time) as last_alert,\n  count as total_alerts, dc(src) as unique_sources\n\n# Compile all responder actions and timestamps\ngrep -E \"timestamp|action|analyst\" \u002Fvar\u002Flog\u002Fir\u002FIR-2024-042\u002F*.json | \\\n  python3 -m json.tool > compiled_actions.json\n```\n\n### Step 2: Conduct Blameless Post-Mortem Meeting\n```\nStructured Agenda (90 minutes):\n1. Incident summary (5 min) - Factual overview\n2. Timeline walkthrough (20 min) - Chronological events\n3. What worked well (15 min) - Positive outcomes\n4. What needs improvement (15 min) - Gaps and failures\n5. Root cause analysis (15 min) - 5 Whys or fishbone\n6. Action items (10 min) - Specific improvements with owners\n7. Playbook updates (10 min) - Changes to IR procedures\n\nBlameless Principles:\n- Focus on systems and processes, not individuals\n- Assume best intentions with available information\n- Seek to understand, not to blame\n```\n\n### Step 3: Perform Root Cause Analysis\n```bash\n# 5 Whys analysis example:\n# Why 1: Why did ransomware encrypt production servers?\n#   Answer: Attacker had domain admin credentials\n# Why 2: Why did attacker have domain admin credentials?\n#   Answer: Kerberoasted a service account and cracked it\n# Why 3: Why was the service account password crackable?\n#   Answer: Used a 12-character dictionary-based password\n# Why 4: Why was the service account password weak?\n#   Answer: No enforcement of service account password policy\n# Why 5: Why was there no service account password policy?\n#   Answer: PAM was not implemented for service accounts\n# ROOT CAUSE: Lack of privileged access management\n```\n\n### Step 4: Calculate Response Metrics\n```python\nfrom datetime import datetime\nevents = {\n    'compromise': '2024-01-10 14:00:00',\n    'detection': '2024-01-15 08:30:00',\n    'triage': '2024-01-15 08:45:00',\n    'containment': '2024-01-15 09:30:00',\n    'eradication': '2024-01-16 14:00:00',\n    'recovery': '2024-01-18 16:00:00',\n    'closure': '2024-01-25 10:00:00',\n}\nfmt = '%Y-%m-%d %H:%M:%S'\ntimes = {k: datetime.strptime(v, fmt) for k, v in events.items()}\nprint(f\"Dwell Time: {times['detection'] - times['compromise']}\")\nprint(f\"MTTD: {times['triage'] - times['detection']}\")\nprint(f\"MTTC: {times['containment'] - times['detection']}\")\nprint(f\"MTTR: {times['recovery'] - times['eradication']}\")\nprint(f\"Total Duration: {times['closure'] - times['detection']}\")\n```\n\n### Step 5: Document Findings and Create Action Items\n```bash\n# Create tracked action items in project management\ncurl -X POST \"https:\u002F\u002Fjira.local\u002Frest\u002Fapi\u002F2\u002Fissue\" \\\n  -H \"Authorization: Bearer $JIRA_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"fields\": {\n      \"project\": {\"key\": \"SEC\"},\n      \"summary\": \"Implement PAM for service accounts (IR-2024-042)\",\n      \"issuetype\": {\"name\": \"Task\"},\n      \"priority\": {\"name\": \"High\"},\n      \"assignee\": {\"name\": \"security_engineer\"},\n      \"duedate\": \"2024-03-15\"\n    }\n  }'\n```\n\n### Step 6: Update Playbooks and Detection Rules\n```yaml\n# New Sigma detection rule based on incident learnings\ntitle: Kerberoasting Activity Detected\nstatus: stable\ndescription: Detects Kerberoasting based on IR-2024-042 lessons\nlogsource:\n  product: windows\n  service: security\ndetection:\n  selection:\n    EventID: 4769\n    TicketEncryptionType: '0x17'\n  condition: selection\nlevel: high\ntags:\n  - attack.credential_access\n  - attack.t1558.003\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Blameless Post-Mortem | Reviewing incidents focusing on systems, not blaming individuals |\n| Root Cause Analysis | Identifying the fundamental reason the incident occurred |\n| 5 Whys | Iterative questioning technique to find root cause |\n| MTTD | Mean Time to Detect - time from compromise to detection |\n| MTTC | Mean Time to Contain - time from detection to containment |\n| MTTR | Mean Time to Recover - time from eradication to full recovery |\n| Continuous Improvement | Iterating on IR processes based on real incident data |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| TheHive\u002FServiceNow | Incident timeline and documentation |\n| Jira\u002FAzure DevOps | Action item tracking |\n| Confluence\u002FSharePoint | Lessons learned documentation |\n| Splunk\u002FElastic | Incident metrics and detection improvement |\n| Sigma | Detection rule development |\n\n## Common Scenarios\n\n1. **Ransomware Post-Mortem**: Review entire kill chain from initial access to encryption. Identify detection gaps and backup failures.\n2. **Phishing Campaign Review**: Analyze why users clicked, why email filters missed it, and how to improve training.\n3. **Cloud Misconfiguration Incident**: Review IaC pipeline, CSPM coverage, and change management process.\n4. **Insider Threat Review**: Examine DLP effectiveness, access control gaps, and user monitoring capabilities.\n5. **Third-Party Breach Impact**: Review vendor risk assessment process and data sharing agreements.\n\n## Output Format\n- Post-incident review meeting minutes\n- Root cause analysis document\n- Incident metrics report (MTTD, MTTC, MTTR)\n- Action items list with owners and deadlines\n- Updated IR playbooks and detection rules\n- Executive summary for leadership\n",{"name":5,"tags":24,"author":30,"domain":31,"license":14,"version":32,"nist_csf":33,"subdomain":25,"description":7,"mitre_attack":38},[25,26,27,28,29],"incident-response","lessons-learned","post-incident","after-action-review","process-improvement","mahipal","cybersecurity","1.0",[34,35,36,37],"RS.MA-01","RS.MA-02","RS.AN-03","RC.RP-01",[39,40,41,42],"T1566","T1486","T1059","T1078","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-post-incident-lessons-learned","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 conducting-post-incident-lessons-learned",{"tool":55,"command":56},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill conducting-post-incident-lessons-learned",{"tool":58,"command":59},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill conducting-post-incident-lessons-learned","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-post-incident-lessons-learned\u002FSKILL.md",true,[63,69,73,79,83,87,93],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"assets\u002Ftemplate.md","ASSET","资产文件",2199,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-post-incident-lessons-learned\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","参考文档",1535,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-post-incident-lessons-learned\u002Freferences\u002Fapi-reference.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fstandards.md",1208,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-post-incident-lessons-learned\u002Freferences\u002Fstandards.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fworkflows.md",1993,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-post-incident-lessons-learned\u002Freferences\u002Fworkflows.md",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fagent.py","SCRIPT","脚本",5815,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-post-incident-lessons-learned\u002Fscripts\u002Fagent.py",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fprocess.py",9431,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fconducting-post-incident-lessons-learned\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",[],[]]