[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B6DERPWQVR3FX265W2VB2N":3,"skill-same:01M7B6DERPWQVR3FX265W2VB2N":99},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":13,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M7B6DERPWQVR3FX265W2VB2N","executing-red-team-engagement-planning",null,"Build the foundational red team engagement plan - scope definition, Rules of Engagement (restrictions, communication plan, emergency stop procedures, legal authorization), MITRE ATT&CK-aligned threat profile selection, and operational timelines - producing an engagement brief for stakeholder approval. Use before any offensive testing begins, when scoping a full-scope, assumed-breach, objective-based, or purple-team engagement.","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\u002Fexecuting-red-team-engagement-planning\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: executing-red-team-engagement-planning\ndescription: Build the foundational red team engagement plan - scope definition, Rules\n  of Engagement (restrictions, communication plan, emergency stop procedures, legal authorization),\n  MITRE ATT&CK-aligned threat profile selection, and operational timelines - producing an\n  engagement brief for stakeholder approval. Use before any offensive testing begins, when\n  scoping a full-scope, assumed-breach, objective-based, or purple-team engagement.\ndomain: cybersecurity\nsubdomain: red-teaming\ntags:\n- red-team\n- adversary-simulation\n- mitre-attack\n- exploitation\n- post-exploitation\n- engagement-planning\n- rules-of-engagement\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- GV.OV-02\n- DE.AE-07\nmitre_attack:\n- T1595\n- T1190\n- T1059\n- T1078\n---\n# Executing Red Team Engagement Planning\n\n## Overview\n\nRed team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins. A well-structured engagement plan ensures the red team simulates realistic adversary behavior while maintaining safety guardrails that prevent unintended business disruption.\n\n\n## When to Use\n\n- When conducting security assessments that involve executing red team engagement planning\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with red teaming concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Define clear engagement scope including in-scope and out-of-scope assets, networks, and personnel\n- Establish Rules of Engagement (ROE) with emergency stop procedures, communication channels, and legal boundaries\n- Select appropriate threat profiles from the MITRE ATT&CK framework aligned to the organization's threat landscape\n- Create a detailed attack plan mapping adversary TTPs to engagement objectives\n- Develop deconfliction procedures with the organization's SOC\u002Fblue team\n- Produce a comprehensive engagement brief for stakeholder approval\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Core Concepts\n\n### Engagement Types\n\n| Type | Description | Scope |\n|------|-------------|-------|\n| Full Scope | Complete adversary simulation with physical, social, and cyber vectors | Entire organization |\n| Assumed Breach | Starts from initial foothold, focuses on post-exploitation | Internal network |\n| Objective-Based | Target specific crown jewels (e.g., domain admin, PII exfiltration) | Defined targets |\n| Purple Team | Collaborative with blue team for detection improvement | Specific controls |\n\n### Rules of Engagement Components\n\n1. **Scope Definition**: IP ranges, domains, physical locations, personnel\n2. **Restrictions**: Systems\u002Fnetworks that must not be touched (e.g., production databases, medical devices)\n3. **Communication Plan**: Primary and secondary contact channels, escalation procedures\n4. **Emergency Procedures**: Code word for immediate cessation, incident response coordination\n5. **Legal Authorization**: Signed authorization letters, get-out-of-jail letters for physical tests\n6. **Data Handling**: How sensitive data discovered during testing will be handled and destroyed\n7. **Timeline**: Start\u002Fend dates, blackout windows, reporting deadlines\n\n### Threat Profile Selection\n\nMap organizational threats using MITRE ATT&CK Navigator to select relevant adversary profiles:\n\n- **APT29 (Cozy Bear)**: Government\u002Fdefense sector targeting via spearphishing, supply chain\n- **APT28 (Fancy Bear)**: Government organizations, credential harvesting, zero-days\n- **FIN7**: Financial sector, POS malware, social engineering\n- **Lazarus Group**: Financial institutions, cryptocurrency exchanges, destructive malware\n- **Conti\u002FRoyal**: Ransomware operators, double extortion, RaaS model\n\n## Workflow\n\n### Phase 1: Pre-Engagement\n\n1. Conduct initial scoping meeting with stakeholders\n2. Identify crown jewels and critical business assets\n3. Review previous security assessments and audit findings\n4. Define success criteria and engagement objectives\n5. Draft Rules of Engagement document\n\n### Phase 2: Threat Modeling\n\n1. Identify relevant threat actors using MITRE ATT&CK\n2. Map threat actor TTPs to organizational attack surface\n3. Select primary and secondary attack scenarios\n4. Define adversary emulation plan with specific technique IDs\n5. Establish detection checkpoints for purple team opportunities\n\n### Phase 3: Operational Planning\n\n1. Set up secure communication channels (encrypted email, Signal, etc.)\n2. Create operational security (OPSEC) guidelines for the red team\n3. Establish infrastructure requirements (C2 servers, redirectors, phishing domains)\n4. Develop phased attack timeline with go\u002Fno-go decision points\n5. Create deconfliction matrix with SOC\u002FIR team\n\n### Phase 4: Documentation and Approval\n\n1. Compile engagement plan document\n2. Review with legal counsel\n3. Obtain executive sponsor signature\n4. Brief red team operators on ROE and restrictions\n5. Distribute emergency contact cards\n\n## Tools and Resources\n\n- **MITRE ATT&CK Navigator**: Threat actor TTP mapping and visualization\n- **VECTR**: Red team engagement tracking and metrics platform\n- **Cobalt Strike \u002F Nighthawk**: C2 framework planning and infrastructure design\n- **PlexTrac**: Red team reporting and engagement management platform\n- **SCYTHE**: Adversary emulation platform for attack plan creation\n\n## Validation Criteria\n\n- [ ] Signed Rules of Engagement document\n- [ ] Defined scope with explicit in\u002Fout boundaries\n- [ ] Selected threat profile with mapped MITRE ATT&CK techniques\n- [ ] Emergency stop procedures tested and verified\n- [ ] Communication plan distributed to all stakeholders\n- [ ] Legal authorization obtained and filed\n- [ ] Red team operators briefed and acknowledged ROE\n\n## Common Pitfalls\n\n1. **Scope Creep**: Expanding testing beyond approved boundaries during execution\n2. **Inadequate Deconfliction**: SOC investigating red team activity as real incidents\n3. **Missing Legal Authorization**: Testing without proper signed authorization\n4. **Unrealistic Threat Models**: Simulating threats irrelevant to the organization\n5. **Poor Communication**: Failing to maintain contact with stakeholders during engagement\n\n## Related Skills\n\n- performing-open-source-intelligence-gathering\n- conducting-adversary-simulation-with-atomic-red-team\n- performing-assumed-breach-red-team-exercise\n- building-red-team-infrastructure-with-redirectors\n","# Executing Red Team Engagement Planning\n\n## Overview\n\nRed team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins. A well-structured engagement plan ensures the red team simulates realistic adversary behavior while maintaining safety guardrails that prevent unintended business disruption.\n\n\n## When to Use\n\n- When conducting security assessments that involve executing red team engagement planning\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with red teaming concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Define clear engagement scope including in-scope and out-of-scope assets, networks, and personnel\n- Establish Rules of Engagement (ROE) with emergency stop procedures, communication channels, and legal boundaries\n- Select appropriate threat profiles from the MITRE ATT&CK framework aligned to the organization's threat landscape\n- Create a detailed attack plan mapping adversary TTPs to engagement objectives\n- Develop deconfliction procedures with the organization's SOC\u002Fblue team\n- Produce a comprehensive engagement brief for stakeholder approval\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Core Concepts\n\n### Engagement Types\n\n| Type | Description | Scope |\n|------|-------------|-------|\n| Full Scope | Complete adversary simulation with physical, social, and cyber vectors | Entire organization |\n| Assumed Breach | Starts from initial foothold, focuses on post-exploitation | Internal network |\n| Objective-Based | Target specific crown jewels (e.g., domain admin, PII exfiltration) | Defined targets |\n| Purple Team | Collaborative with blue team for detection improvement | Specific controls |\n\n### Rules of Engagement Components\n\n1. **Scope Definition**: IP ranges, domains, physical locations, personnel\n2. **Restrictions**: Systems\u002Fnetworks that must not be touched (e.g., production databases, medical devices)\n3. **Communication Plan**: Primary and secondary contact channels, escalation procedures\n4. **Emergency Procedures**: Code word for immediate cessation, incident response coordination\n5. **Legal Authorization**: Signed authorization letters, get-out-of-jail letters for physical tests\n6. **Data Handling**: How sensitive data discovered during testing will be handled and destroyed\n7. **Timeline**: Start\u002Fend dates, blackout windows, reporting deadlines\n\n### Threat Profile Selection\n\nMap organizational threats using MITRE ATT&CK Navigator to select relevant adversary profiles:\n\n- **APT29 (Cozy Bear)**: Government\u002Fdefense sector targeting via spearphishing, supply chain\n- **APT28 (Fancy Bear)**: Government organizations, credential harvesting, zero-days\n- **FIN7**: Financial sector, POS malware, social engineering\n- **Lazarus Group**: Financial institutions, cryptocurrency exchanges, destructive malware\n- **Conti\u002FRoyal**: Ransomware operators, double extortion, RaaS model\n\n## Workflow\n\n### Phase 1: Pre-Engagement\n\n1. Conduct initial scoping meeting with stakeholders\n2. Identify crown jewels and critical business assets\n3. Review previous security assessments and audit findings\n4. Define success criteria and engagement objectives\n5. Draft Rules of Engagement document\n\n### Phase 2: Threat Modeling\n\n1. Identify relevant threat actors using MITRE ATT&CK\n2. Map threat actor TTPs to organizational attack surface\n3. Select primary and secondary attack scenarios\n4. Define adversary emulation plan with specific technique IDs\n5. Establish detection checkpoints for purple team opportunities\n\n### Phase 3: Operational Planning\n\n1. Set up secure communication channels (encrypted email, Signal, etc.)\n2. Create operational security (OPSEC) guidelines for the red team\n3. Establish infrastructure requirements (C2 servers, redirectors, phishing domains)\n4. Develop phased attack timeline with go\u002Fno-go decision points\n5. Create deconfliction matrix with SOC\u002FIR team\n\n### Phase 4: Documentation and Approval\n\n1. Compile engagement plan document\n2. Review with legal counsel\n3. Obtain executive sponsor signature\n4. Brief red team operators on ROE and restrictions\n5. Distribute emergency contact cards\n\n## Tools and Resources\n\n- **MITRE ATT&CK Navigator**: Threat actor TTP mapping and visualization\n- **VECTR**: Red team engagement tracking and metrics platform\n- **Cobalt Strike \u002F Nighthawk**: C2 framework planning and infrastructure design\n- **PlexTrac**: Red team reporting and engagement management platform\n- **SCYTHE**: Adversary emulation platform for attack plan creation\n\n## Validation Criteria\n\n- [ ] Signed Rules of Engagement document\n- [ ] Defined scope with explicit in\u002Fout boundaries\n- [ ] Selected threat profile with mapped MITRE ATT&CK techniques\n- [ ] Emergency stop procedures tested and verified\n- [ ] Communication plan distributed to all stakeholders\n- [ ] Legal authorization obtained and filed\n- [ ] Red team operators briefed and acknowledged ROE\n\n## Common Pitfalls\n\n1. **Scope Creep**: Expanding testing beyond approved boundaries during execution\n2. **Inadequate Deconfliction**: SOC investigating red team activity as real incidents\n3. **Missing Legal Authorization**: Testing without proper signed authorization\n4. **Unrealistic Threat Models**: Simulating threats irrelevant to the organization\n5. **Poor Communication**: Failing to maintain contact with stakeholders during engagement\n\n## Related Skills\n\n- performing-open-source-intelligence-gathering\n- conducting-adversary-simulation-with-atomic-red-team\n- performing-assumed-breach-red-team-exercise\n- building-red-team-infrastructure-with-redirectors\n",{"name":5,"tags":24,"author":32,"domain":33,"license":14,"version":34,"nist_csf":35,"subdomain":39,"description":7,"mitre_attack":40},[25,26,27,28,29,30,31],"red-team","adversary-simulation","mitre-attack","exploitation","post-exploitation","engagement-planning","rules-of-engagement","mahipal","cybersecurity","1.0",[36,37,38],"ID.RA-01","GV.OV-02","DE.AE-07","red-teaming",[41,42,43,44],"T1595","T1190","T1059","T1078","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexecuting-red-team-engagement-planning","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill executing-red-team-engagement-planning",{"tool":57,"command":58},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill executing-red-team-engagement-planning",{"tool":60,"command":61},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill executing-red-team-engagement-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002FSKILL.md",true,[65,71,75,81,85,89,95],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"assets\u002Ftemplate.md","ASSET","资产文件",6830,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Fassets\u002Ftemplate.md",{"path":72,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fapi-reference.md","REFERENCE","参考文档",2273,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Freferences\u002Fapi-reference.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fstandards.md",2798,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Freferences\u002Fstandards.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fworkflows.md",6292,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Freferences\u002Fworkflows.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fagent.py","SCRIPT","脚本",6072,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Fscripts\u002Fagent.py",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fprocess.py",33525,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Fscripts\u002Fprocess.py",[100,108,115,122,129,136],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"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":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"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":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"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",[],[]]