[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BVAP0NPFP8JSV5WZVRSVBA":3,"skill-same:01M7BVAP0NPFP8JSV5WZVRSVBA":83},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7BVAP0NPFP8JSV5WZVRSVBA","linkedin-engagement",null,"Use when someone wants to grow reach through comments, replies, groups, or outreach on LinkedIn — a commenting roster, a connection request note, a DM or InMail, a networking plan, or a check on whether their outreach volume is safe. Triggers on \"who should I engage with\", \"write a connection request\", \"cold DM\", \"LinkedIn outreach\", \"networking strategy\", \"how many invites can I send\". Builds a weekly comment roster inside a real time budget, assembles one message at a time and refuses templates, and caps volume against LinkedIn's limits. Nothing is ever sent.","azhri1990\u002Fproject-genesis","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7BMC0XAE6SV0VTKWP3EMFGZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing\u002Flinkedin-engagement\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: linkedin-engagement\ndescription: Use when someone wants to grow reach through comments, replies, groups, or outreach on LinkedIn — a commenting roster, a connection request note, a DM or InMail, a networking plan, or a check on whether their outreach volume is safe. Triggers on \"who should I engage with\", \"write a connection request\", \"cold DM\", \"LinkedIn outreach\", \"networking strategy\", \"how many invites can I send\". Builds a weekly comment roster inside a real time budget, assembles one message at a time and refuses templates, and caps volume against LinkedIn's limits. Nothing is ever sent.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-08-25\n---\n\n# LinkedIn Engagement — comments first, outreach second\n\nFrom a standing start your posts reach almost nobody, and publishing harder does not fix it.\nA substantive comment on a post that already has an audience puts your name, headline, and a\nparagraph of thinking in front of people already reading about your subject, for six minutes\nof work — the cheapest distribution on the platform, and the most badly used.\n\n**Nothing here sends anything** — no credentials, no API calls. Automated connecting,\nmessaging, commenting, liking, and sharing are prohibited by User Agreement §8.2.\n\n## Workflow\n\n**1. Build the comment roster.** Name 8-12 accounts they would read anyway, with audience\noverlap and rough size tier, then:\n\n```bash\npython3 scripts\u002Fcomment_target_planner.py --account \"Priya Raman:5:4:larger\" \\\n  --account \"Tomas Lind:5:3:peer\" --minutes-per-day 18 --output human\n```\n\nTiers are `huge` (10x+, crowded), `larger` (2-10x, the best ratio), `peer` (~1x, where\nreciprocity compounds), `smaller` (goodwill). The roster caps any account at twice a week —\ncommenting daily on one person reads as following them around — and keeps the huge tier under\nhalf of any day. It builds the roster, never the comments: a generated comment is exactly\nwhat §8.2 names, and it is recognisable anyway.\n\n**2. Outreach — check the volume before writing anything.**\n\n```bash\npython3 scripts\u002Foutreach_volume_guard.py --invites 20 --pending 5 --minutes 120 \\\n  --acceptance 0.42 --output human\n```\n\nExit 0 safe \u002F 2 tight \u002F 3 over a cap or the time budget \u002F **4 refused** above 40 invitations\na day, because nobody reads that many profiles and writes that many specific lines. Pending\ninvitations count against the weekly limit (observed around 100), and acceptance below 20% is\na stop signal — it is the pattern LinkedIn reviews, and the targeting is wrong.\n\n**3. Write one message, for one person.**\n\n```bash\npython3 scripts\u002Foutreach_message_builder.py --type connection \\\n  --recipient \"Priya\" --specific-line \"...\" --reason \"...\" --output human\n```\n\nIt refuses without a person-specific line, refuses an ask in a first-touch connection note,\nand enforces the 200-character cap (300 with `--premium`). In large third-party samples a\nnote barely moves acceptance (~26.4% either way) but roughly doubles the post-accept reply\nrate: **the note earns the conversation, not the meeting.**\n\n**4. The order that works.** Comment on their work for two weeks. Then invite, referencing\nsomething specific from that reading. Then, after acceptance and a pause, ask once, small.\n\n## Rules\n\n- **Nothing is auto-sent.** Ever. The user pastes and sends, one person at a time.\n- **No engagement pods.** Coordinated reciprocal commenting is inauthentic engagement under\n  §8.2 regardless of who pressed the key. Build a real reciprocity list instead.\n- **Every message carries a line that could only have been written for that person.**\n- **Never paste the same comment twice.** Identical comments at volume are the definition of\n  the thing §8.2 prohibits.\n- **One follow-up, a week later, only with something new to say.**\n- **Agreement is not a comment.** Add the counter-example, the number, or the case where it\n  breaks — or skip the slot.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fcomment_target_planner.py`](scripts\u002Fcomment_target_planner.py) | Weekly roster from scored accounts, inside a time budget, with per-account and per-tier caps. |\n| [`scripts\u002Foutreach_message_builder.py`](scripts\u002Foutreach_message_builder.py) | Assembles one message; refuses templates, premature asks, and 14 dead phrases. |\n| [`scripts\u002Foutreach_volume_guard.py`](scripts\u002Foutreach_volume_guard.py) | Caps invitations against the observed weekly limit, pending backlog, acceptance floor, and the hours available. |\n\n## References and assets\n\n- [`references\u002Fcomment_strategy.md`](references\u002Fcomment_strategy.md) — tiers, what a comment competes on, pods, replying to your own posts (7 sources)\n- [`references\u002Foutreach_ethics_and_benchmarks.md`](references\u002Foutreach_ethics_and_benchmarks.md) — the benchmark numbers with their provenance, and the personalisation claim corrected (7 sources)\n\n- [`assets\u002Foutreach_worksheet.md`](assets\u002Foutreach_worksheet.md) — fillable per-person prep sheet\n- [`assets\u002Fexample_outreach.json`](assets\u002Fexample_outreach.json) — input shape for the builder\n\n## Distinct from\n\n- **`linkedin-content`** — writes posts. A comment is a different craft on a different budget.\n- **`marketing-skill\u002Fcold-email`** — email. Different channel, law, and caps.\n- **`business-growth\u002F`, `commercial\u002F`** — sales process and deal economics, not networking.\n\n---\n**Version:** 1.0.0\n","# LinkedIn Engagement — comments first, outreach second\n\nFrom a standing start your posts reach almost nobody, and publishing harder does not fix it.\nA substantive comment on a post that already has an audience puts your name, headline, and a\nparagraph of thinking in front of people already reading about your subject, for six minutes\nof work — the cheapest distribution on the platform, and the most badly used.\n\n**Nothing here sends anything** — no credentials, no API calls. Automated connecting,\nmessaging, commenting, liking, and sharing are prohibited by User Agreement §8.2.\n\n## Workflow\n\n**1. Build the comment roster.** Name 8-12 accounts they would read anyway, with audience\noverlap and rough size tier, then:\n\n```bash\npython3 scripts\u002Fcomment_target_planner.py --account \"Priya Raman:5:4:larger\" \\\n  --account \"Tomas Lind:5:3:peer\" --minutes-per-day 18 --output human\n```\n\nTiers are `huge` (10x+, crowded), `larger` (2-10x, the best ratio), `peer` (~1x, where\nreciprocity compounds), `smaller` (goodwill). The roster caps any account at twice a week —\ncommenting daily on one person reads as following them around — and keeps the huge tier under\nhalf of any day. It builds the roster, never the comments: a generated comment is exactly\nwhat §8.2 names, and it is recognisable anyway.\n\n**2. Outreach — check the volume before writing anything.**\n\n```bash\npython3 scripts\u002Foutreach_volume_guard.py --invites 20 --pending 5 --minutes 120 \\\n  --acceptance 0.42 --output human\n```\n\nExit 0 safe \u002F 2 tight \u002F 3 over a cap or the time budget \u002F **4 refused** above 40 invitations\na day, because nobody reads that many profiles and writes that many specific lines. Pending\ninvitations count against the weekly limit (observed around 100), and acceptance below 20% is\na stop signal — it is the pattern LinkedIn reviews, and the targeting is wrong.\n\n**3. Write one message, for one person.**\n\n```bash\npython3 scripts\u002Foutreach_message_builder.py --type connection \\\n  --recipient \"Priya\" --specific-line \"...\" --reason \"...\" --output human\n```\n\nIt refuses without a person-specific line, refuses an ask in a first-touch connection note,\nand enforces the 200-character cap (300 with `--premium`). In large third-party samples a\nnote barely moves acceptance (~26.4% either way) but roughly doubles the post-accept reply\nrate: **the note earns the conversation, not the meeting.**\n\n**4. The order that works.** Comment on their work for two weeks. Then invite, referencing\nsomething specific from that reading. Then, after acceptance and a pause, ask once, small.\n\n## Rules\n\n- **Nothing is auto-sent.** Ever. The user pastes and sends, one person at a time.\n- **No engagement pods.** Coordinated reciprocal commenting is inauthentic engagement under\n  §8.2 regardless of who pressed the key. Build a real reciprocity list instead.\n- **Every message carries a line that could only have been written for that person.**\n- **Never paste the same comment twice.** Identical comments at volume are the definition of\n  the thing §8.2 prohibits.\n- **One follow-up, a week later, only with something new to say.**\n- **Agreement is not a comment.** Add the counter-example, the number, or the case where it\n  breaks — or skip the slot.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fcomment_target_planner.py`](scripts\u002Fcomment_target_planner.py) | Weekly roster from scored accounts, inside a time budget, with per-account and per-tier caps. |\n| [`scripts\u002Foutreach_message_builder.py`](scripts\u002Foutreach_message_builder.py) | Assembles one message; refuses templates, premature asks, and 14 dead phrases. |\n| [`scripts\u002Foutreach_volume_guard.py`](scripts\u002Foutreach_volume_guard.py) | Caps invitations against the observed weekly limit, pending backlog, acceptance floor, and the hours available. |\n\n## References and assets\n\n- [`references\u002Fcomment_strategy.md`](references\u002Fcomment_strategy.md) — tiers, what a comment competes on, pods, replying to your own posts (7 sources)\n- [`references\u002Foutreach_ethics_and_benchmarks.md`](references\u002Foutreach_ethics_and_benchmarks.md) — the benchmark numbers with their provenance, and the personalisation claim corrected (7 sources)\n\n- [`assets\u002Foutreach_worksheet.md`](assets\u002Foutreach_worksheet.md) — fillable per-person prep sheet\n- [`assets\u002Fexample_outreach.json`](assets\u002Fexample_outreach.json) — input shape for the builder\n\n## Distinct from\n\n- **`linkedin-content`** — writes posts. A comment is a different craft on a different budget.\n- **`marketing-skill\u002Fcold-email`** — email. Different channel, law, and caps.\n- **`business-growth\u002F`, `commercial\u002F`** — sales process and deal economics, not networking.\n\n---\n**Version:** 1.0.0\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1787616000000,"1.0.0","marketing","main","456c0680145b74fe0168cc63541f08eda89e53c0","claude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing\u002Flinkedin-engagement","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-09-27 20:56:28",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add azhri1990\u002Fproject-genesis --skill linkedin-engagement",{"tool":41,"command":42},"bunx","bunx skills add azhri1990\u002Fproject-genesis --skill linkedin-engagement",{"tool":44,"command":45},"pnpm","pnpm dlx skills add azhri1990\u002Fproject-genesis --skill linkedin-engagement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing\u002Flinkedin-engagement\u002FSKILL.md",true,[49,55,59,65,69,75,79],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"assets\u002Fexample_outreach.json","ASSET","资产文件",607,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing\u002Flinkedin-engagement\u002Fassets\u002Fexample_outreach.json",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"assets\u002Foutreach_worksheet.md",2480,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing\u002Flinkedin-engagement\u002Fassets\u002Foutreach_worksheet.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fcomment_strategy.md","REFERENCE","参考文档",6756,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing\u002Flinkedin-engagement\u002Freferences\u002Fcomment_strategy.md",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Foutreach_ethics_and_benchmarks.md",6617,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing\u002Flinkedin-engagement\u002Freferences\u002Foutreach_ethics_and_benchmarks.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fcomment_target_planner.py","SCRIPT","脚本",11172,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing\u002Flinkedin-engagement\u002Fscripts\u002Fcomment_target_planner.py",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Foutreach_message_builder.py",11937,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing\u002Flinkedin-engagement\u002Fscripts\u002Foutreach_message_builder.py",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Foutreach_volume_guard.py",9466,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fmarketing\u002Flinkedin-engagement\u002Fscripts\u002Foutreach_volume_guard.py",[84,91,98,105,112,119],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7C0EZY9FK6JW3YAC7CN17KY","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7C0EA12FWRZTMG0N23HV68M","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7C0DXEHJKMKTB4N6B7MS4BT","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7C0DJM5ECEKZXTQA9G6YHQZ","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7C0D304Z7YX7J25R42N6W2T","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M7C0CP1419VDF6SGCDY6ZRZV","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\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]