[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CD513FDPE023YWN88NPG10":3,"skill-same:01M7CD513FDPE023YWN88NPG10":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7CD513FDPE023YWN88NPG10","strategic-alignment",null,"Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, or strategy communication.","azhri1990\u002Fjarvis-mega-repo","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7C4WMQVQ450E0NA99BG7BHA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fc-level-advisor\u002Fstrategic-alignment\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"strategic-alignment\"\ndescription: \"Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, or strategy communication.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: strategic-alignment\n  updated: 2026-03-05\n  python-tools: alignment_checker.py\n  frameworks: alignment-playbook\n---\n\n# Strategic Alignment Engine\n\nStrategy fails at the cascade, not the boardroom. This skill detects misalignment before it becomes dysfunction and builds systems that keep strategy connected from CEO to individual contributor.\n\n## Keywords\nstrategic alignment, strategy cascade, OKR alignment, orphan OKRs, conflicting goals, silos, communication gap, department alignment, alignment checker, strategy articulation, cross-functional, goal cascade, misalignment, alignment score\n\n## Quick Start\n\n```bash\npython scripts\u002Falignment_checker.py    # Check OKR alignment: orphans, conflicts, coverage gaps\n```\n\n## Core Framework\n\nThe alignment problem: **The further a goal gets from the strategy that created it, the less likely it reflects the original intent.** This is the organizational telephone game. It happens at every stage. The question is how bad it is and how to fix it.\n\n### Step 1: Strategy Articulation Test\n\nBefore checking cascade, check the source. Ask five people from five different teams:\n**\"What is the company's most important strategic priority right now?\"**\n\n**Scoring:**\n- All five give the same answer: ✅ Articulation is clear\n- 3–4 give similar answers: 🟡 Loose alignment — clarify and communicate\n- \u003C 3 agree: 🔴 Strategy isn't clear enough to cascade. Fix this before fixing cascade.\n\n**Format test:** The strategy should be statable in one sentence. If leadership needs a paragraph, teams won't internalize it.\n- ❌ \"We focus on product-led growth while maintaining enterprise relationships and expanding our international presence and investing in platform capabilities\"\n- ✅ \"Win the mid-market healthcare segment in DACH before Series B\"\n\n### Step 2: Cascade Mapping\n\nMap the flow from company strategy → each level of the organization.\n\n```\nCompany level:  OKR-1, OKR-2, OKR-3\n    ↓\nDept level:     Sales OKRs, Eng OKRs, Product OKRs, CS OKRs\n    ↓\nTeam level:     Team A OKRs, Team B OKRs...\n    ↓\nIndividual:     Personal goals \u002F rocks\n```\n\n**For each goal at every level, ask:**\n- Which company-level goal does this support?\n- If this goal is 100% achieved, how much does it move the company goal?\n- Is the connection direct or theoretical?\n\n### Step 3: Alignment Detection\n\nThree failure patterns:\n\n**Orphan goals:** Team or individual goals that don't connect to any company goal.\n- Symptom: \"We've been working on this for a quarter and nobody above us seems to care\"\n- Root cause: Goals set bottom-up or from last quarter's priorities without reconciling to current company OKRs\n- Fix: Connect or cut. Every goal needs a parent.\n\n**Conflicting goals:** Two teams' goals, when both succeed, create a worse outcome.\n- Classic example: Sales commits to volume contracts (revenue), CS is measured on satisfaction scores. Sales closes bad-fit customers; CS scores tank.\n- Fix: Cross-functional OKR review before quarter begins. Shared metrics where teams interact.\n\n**Coverage gaps:** Company has 3 OKRs. 5 teams support OKR-1, 2 support OKR-2, 0 support OKR-3.\n- Symptom: Company OKR-3 consistently misses; nobody owns it\n- Fix: Explicit ownership assignment. If no team owns a company OKR, it won't happen.\n\nSee `scripts\u002Falignment_checker.py` for automated detection against your JSON-formatted OKRs.\n\n### Step 4: Silo Identification\n\nSilos exist when teams optimize for local metrics at the expense of company metrics.\n\n**Silo signals:**\n- A department consistently hits their goals while the company misses\n- Teams don't know what other teams are working on\n- \"That's not our problem\" is a common phrase\n- Escalations only flow up; coordination never flows sideways\n- Data isn't shared between teams that depend on each other\n\n**Silo root causes:**\n1. **Incentive misalignment:** Teams rewarded for local metrics don't optimize for company metrics\n2. **No shared goals:** When teams share a goal, they coordinate. When they don't, they drift.\n3. **No shared language:** Engineering doesn't understand sales metrics; sales doesn't understand technical debt\n4. **Geography or time zones:** Silos accelerate when teams don't interact organically\n\n**Silo measurement:**\n- How often do teams request something from each other vs. proceed independently?\n- How much time does it take to resolve a cross-functional issue?\n- Can a team member describe the current priorities of an adjacent team?\n\n### Step 5: Communication Gap Analysis\n\nWhat the CEO says ≠ what teams hear. The gap grows with company size.\n\n**The message decay model:**\n- CEO communicates strategy at all-hands → managers filter through their lens → teams receive modified version → individuals interpret further\n\n**Gap sources:**\n- **Ambiguity:** Strategy stated at too high a level (\"grow the business\") lets each team fill in their own interpretation\n- **Frequency:** One all-hands per quarter isn't enough repetition to change behavior\n- **Medium mismatch:** Long written strategy doc for teams that respond to visual communication\n- **Trust deficit:** Teams don't believe the strategy is real (\"we've heard this before\")\n\n**Gap detection:**\n- Run the Step 1 articulation test across all levels\n- Compare what leadership thinks they communicated vs. what teams say they heard\n- Survey: \"What changed about how you work since the last strategy update?\"\n\n### Step 6: Realignment Protocol\n\nHow to fix misalignment without calling it a \"realignment\" (which creates fear).\n\n**Step 6a: Don't start with what's wrong**\nStarting with \"here's our misalignment\" creates defensiveness. Start with \"here's where we're heading and I want to make sure we're connected.\"\n\n**Step 6b: Re-cascade in a workshop, not a memo**\nAlignment workshops are more effective than documents. Get company-level OKR owners and department leads in a room. Map connections. Find gaps together.\n\n**Step 6c: Fix incentives before fixing goals**\nIf department heads are rewarded for local metrics that conflict with company goals, no amount of goal-setting fixes the problem. The incentive structure must change first.\n\n**Step 6d: Install a quarterly alignment check**\nAfter fixing, prevent recurrence. See `references\u002Falignment-playbook.md` for quarterly cadence.\n\n---\n\n## Alignment Score\n\nA quick health check. Score each area 0–10:\n\n| Area | Question | Score |\n|------|----------|-------|\n| Strategy clarity | Can 5 people from different teams state the strategy consistently? | \u002F10 |\n| Cascade completeness | Do all team goals connect to company goals? | \u002F10 |\n| Conflict detection | Have cross-team OKR conflicts been reviewed and resolved? | \u002F10 |\n| Coverage | Does each company OKR have explicit team ownership? | \u002F10 |\n| Communication | Do teams' behaviors reflect the strategy (not just their stated understanding)? | \u002F10 |\n\n**Total: __ \u002F 50**\n\n| Score | Status |\n|-------|--------|\n| 45–50 | Excellent. Maintain the system. |\n| 35–44 | Good. Address specific weak areas. |\n| 20–34 | Misalignment is costing you. Immediate attention required. |\n| \u003C 20 | Strategic drift. Treat as crisis. |\n\n---\n\n## Key Questions for Alignment\n\n- \"Ask your newest team member: what is the most important thing the company is trying to achieve right now?\"\n- \"Which company OKR does your team's top priority support? Can you trace the connection?\"\n- \"When Team A and Team B both hit their goals, does the company always win? Are there scenarios where they don't?\"\n- \"What changed in how your team works since the last strategy update?\"\n- \"Name a decision made last week that was influenced by the company strategy.\"\n\n## Red Flags\n\n- Teams consistently hit goals while company misses targets\n- Cross-functional projects take 3x longer than expected (coordination failure)\n- Strategy updated quarterly but team priorities don't change\n- \"That's a leadership problem, not our problem\" attitude at the team level\n- New initiatives announced without connecting them to existing OKRs\n- Department heads optimize for headcount or budget rather than company outcomes\n\n## Integration with Other C-Suite Roles\n\n| When... | Work with... | To... |\n|---------|-------------|-------|\n| New strategy is set | CEO + COO | Cascade into quarterly rocks before announcing |\n| OKR cycle starts | COO | Run cross-team conflict check before finalizing |\n| Team consistently misses goals | CHRO | Diagnose: capability gap or alignment gap? |\n| Silo identified | COO | Design shared metrics or cross-functional OKRs |\n| Post-M&A | CEO + Culture Architect | Detect strategy conflicts between merged entities |\n\n## Detailed References\n- `scripts\u002Falignment_checker.py` — Automated OKR alignment analysis (orphans, conflicts, coverage)\n- `references\u002Falignment-playbook.md` — Cascade techniques, quarterly alignment check, common patterns\n","# Strategic Alignment Engine\n\nStrategy fails at the cascade, not the boardroom. This skill detects misalignment before it becomes dysfunction and builds systems that keep strategy connected from CEO to individual contributor.\n\n## Keywords\nstrategic alignment, strategy cascade, OKR alignment, orphan OKRs, conflicting goals, silos, communication gap, department alignment, alignment checker, strategy articulation, cross-functional, goal cascade, misalignment, alignment score\n\n## Quick Start\n\n```bash\npython scripts\u002Falignment_checker.py    # Check OKR alignment: orphans, conflicts, coverage gaps\n```\n\n## Core Framework\n\nThe alignment problem: **The further a goal gets from the strategy that created it, the less likely it reflects the original intent.** This is the organizational telephone game. It happens at every stage. The question is how bad it is and how to fix it.\n\n### Step 1: Strategy Articulation Test\n\nBefore checking cascade, check the source. Ask five people from five different teams:\n**\"What is the company's most important strategic priority right now?\"**\n\n**Scoring:**\n- All five give the same answer: ✅ Articulation is clear\n- 3–4 give similar answers: 🟡 Loose alignment — clarify and communicate\n- \u003C 3 agree: 🔴 Strategy isn't clear enough to cascade. Fix this before fixing cascade.\n\n**Format test:** The strategy should be statable in one sentence. If leadership needs a paragraph, teams won't internalize it.\n- ❌ \"We focus on product-led growth while maintaining enterprise relationships and expanding our international presence and investing in platform capabilities\"\n- ✅ \"Win the mid-market healthcare segment in DACH before Series B\"\n\n### Step 2: Cascade Mapping\n\nMap the flow from company strategy → each level of the organization.\n\n```\nCompany level:  OKR-1, OKR-2, OKR-3\n    ↓\nDept level:     Sales OKRs, Eng OKRs, Product OKRs, CS OKRs\n    ↓\nTeam level:     Team A OKRs, Team B OKRs...\n    ↓\nIndividual:     Personal goals \u002F rocks\n```\n\n**For each goal at every level, ask:**\n- Which company-level goal does this support?\n- If this goal is 100% achieved, how much does it move the company goal?\n- Is the connection direct or theoretical?\n\n### Step 3: Alignment Detection\n\nThree failure patterns:\n\n**Orphan goals:** Team or individual goals that don't connect to any company goal.\n- Symptom: \"We've been working on this for a quarter and nobody above us seems to care\"\n- Root cause: Goals set bottom-up or from last quarter's priorities without reconciling to current company OKRs\n- Fix: Connect or cut. Every goal needs a parent.\n\n**Conflicting goals:** Two teams' goals, when both succeed, create a worse outcome.\n- Classic example: Sales commits to volume contracts (revenue), CS is measured on satisfaction scores. Sales closes bad-fit customers; CS scores tank.\n- Fix: Cross-functional OKR review before quarter begins. Shared metrics where teams interact.\n\n**Coverage gaps:** Company has 3 OKRs. 5 teams support OKR-1, 2 support OKR-2, 0 support OKR-3.\n- Symptom: Company OKR-3 consistently misses; nobody owns it\n- Fix: Explicit ownership assignment. If no team owns a company OKR, it won't happen.\n\nSee `scripts\u002Falignment_checker.py` for automated detection against your JSON-formatted OKRs.\n\n### Step 4: Silo Identification\n\nSilos exist when teams optimize for local metrics at the expense of company metrics.\n\n**Silo signals:**\n- A department consistently hits their goals while the company misses\n- Teams don't know what other teams are working on\n- \"That's not our problem\" is a common phrase\n- Escalations only flow up; coordination never flows sideways\n- Data isn't shared between teams that depend on each other\n\n**Silo root causes:**\n1. **Incentive misalignment:** Teams rewarded for local metrics don't optimize for company metrics\n2. **No shared goals:** When teams share a goal, they coordinate. When they don't, they drift.\n3. **No shared language:** Engineering doesn't understand sales metrics; sales doesn't understand technical debt\n4. **Geography or time zones:** Silos accelerate when teams don't interact organically\n\n**Silo measurement:**\n- How often do teams request something from each other vs. proceed independently?\n- How much time does it take to resolve a cross-functional issue?\n- Can a team member describe the current priorities of an adjacent team?\n\n### Step 5: Communication Gap Analysis\n\nWhat the CEO says ≠ what teams hear. The gap grows with company size.\n\n**The message decay model:**\n- CEO communicates strategy at all-hands → managers filter through their lens → teams receive modified version → individuals interpret further\n\n**Gap sources:**\n- **Ambiguity:** Strategy stated at too high a level (\"grow the business\") lets each team fill in their own interpretation\n- **Frequency:** One all-hands per quarter isn't enough repetition to change behavior\n- **Medium mismatch:** Long written strategy doc for teams that respond to visual communication\n- **Trust deficit:** Teams don't believe the strategy is real (\"we've heard this before\")\n\n**Gap detection:**\n- Run the Step 1 articulation test across all levels\n- Compare what leadership thinks they communicated vs. what teams say they heard\n- Survey: \"What changed about how you work since the last strategy update?\"\n\n### Step 6: Realignment Protocol\n\nHow to fix misalignment without calling it a \"realignment\" (which creates fear).\n\n**Step 6a: Don't start with what's wrong**\nStarting with \"here's our misalignment\" creates defensiveness. Start with \"here's where we're heading and I want to make sure we're connected.\"\n\n**Step 6b: Re-cascade in a workshop, not a memo**\nAlignment workshops are more effective than documents. Get company-level OKR owners and department leads in a room. Map connections. Find gaps together.\n\n**Step 6c: Fix incentives before fixing goals**\nIf department heads are rewarded for local metrics that conflict with company goals, no amount of goal-setting fixes the problem. The incentive structure must change first.\n\n**Step 6d: Install a quarterly alignment check**\nAfter fixing, prevent recurrence. See `references\u002Falignment-playbook.md` for quarterly cadence.\n\n---\n\n## Alignment Score\n\nA quick health check. Score each area 0–10:\n\n| Area | Question | Score |\n|------|----------|-------|\n| Strategy clarity | Can 5 people from different teams state the strategy consistently? | \u002F10 |\n| Cascade completeness | Do all team goals connect to company goals? | \u002F10 |\n| Conflict detection | Have cross-team OKR conflicts been reviewed and resolved? | \u002F10 |\n| Coverage | Does each company OKR have explicit team ownership? | \u002F10 |\n| Communication | Do teams' behaviors reflect the strategy (not just their stated understanding)? | \u002F10 |\n\n**Total: __ \u002F 50**\n\n| Score | Status |\n|-------|--------|\n| 45–50 | Excellent. Maintain the system. |\n| 35–44 | Good. Address specific weak areas. |\n| 20–34 | Misalignment is costing you. Immediate attention required. |\n| \u003C 20 | Strategic drift. Treat as crisis. |\n\n---\n\n## Key Questions for Alignment\n\n- \"Ask your newest team member: what is the most important thing the company is trying to achieve right now?\"\n- \"Which company OKR does your team's top priority support? Can you trace the connection?\"\n- \"When Team A and Team B both hit their goals, does the company always win? Are there scenarios where they don't?\"\n- \"What changed in how your team works since the last strategy update?\"\n- \"Name a decision made last week that was influenced by the company strategy.\"\n\n## Red Flags\n\n- Teams consistently hit goals while company misses targets\n- Cross-functional projects take 3x longer than expected (coordination failure)\n- Strategy updated quarterly but team priorities don't change\n- \"That's a leadership problem, not our problem\" attitude at the team level\n- New initiatives announced without connecting them to existing OKRs\n- Department heads optimize for headcount or budget rather than company outcomes\n\n## Integration with Other C-Suite Roles\n\n| When... | Work with... | To... |\n|---------|-------------|-------|\n| New strategy is set | CEO + COO | Cascade into quarterly rocks before announcing |\n| OKR cycle starts | COO | Run cross-team conflict check before finalizing |\n| Team consistently misses goals | CHRO | Diagnose: capability gap or alignment gap? |\n| Silo identified | COO | Design shared metrics or cross-functional OKRs |\n| Post-M&A | CEO + Culture Architect | Detect strategy conflicts between merged entities |\n\n## Detailed References\n- `scripts\u002Falignment_checker.py` — Automated OKR alignment analysis (orphans, conflicts, coverage)\n- `references\u002Falignment-playbook.md` — Cascade techniques, quarterly alignment check, common patterns\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"domain":5,"updated":26,"version":27,"category":28,"frameworks":29,"python-tools":30},"Alireza Rezvani",1772668800000,"1.0.0","c-level","alignment-playbook","alignment_checker.py","main","46d43f3edecde97283ac410e9051444d90120cfb","repos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fc-level-advisor\u002Fstrategic-alignment","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-10-10 07:58:58",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add azhri1990\u002Fjarvis-mega-repo --skill strategic-alignment",{"tool":43,"command":44},"bunx","bunx skills add azhri1990\u002Fjarvis-mega-repo --skill strategic-alignment",{"tool":46,"command":47},"pnpm","pnpm dlx skills add azhri1990\u002Fjarvis-mega-repo --skill strategic-alignment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fc-level-advisor\u002Fstrategic-alignment\u002FSKILL.md",true,[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Falignment-playbook.md","REFERENCE","参考文档",8606,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fc-level-advisor\u002Fstrategic-alignment\u002Freferences\u002Falignment-playbook.md",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Falignment_checker.py","SCRIPT","脚本",17679,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002FJ.A.R.V.I.S\u002Fcomponents\u002Fcore\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fc-level-advisor\u002Fstrategic-alignment\u002Fscripts\u002Falignment_checker.py",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CYPF9V9EMA4ZXS1TTCMBFH","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.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CYNRJDTQCRF5KGPMBMSB1S","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CYNAVSE84QD7HAWZWTY2FS","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CYN0CE8P5ZN7WV2X06HKPC","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CYMHZ3QRJ9BKRB859KW8TQ","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7CYM3D8YKV7R6DT4RNJSF0A","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]