[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BCZVBK0QM4RHF2HKXQGE0X":3,"skill-same:01M7BCZVBK0QM4RHF2HKXQGE0X":58},{"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":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7BCZVBK0QM4RHF2HKXQGE0X","render-disks",null,"Attaches and manages persistent disks on Render services—mount paths, sizing, snapshots, file transfers, and single-instance constraints. Use when the user needs persistent storage, file uploads, a custom database on disk, CMS media storage, or needs to understand why their service can't scale horizontally or use zero-downtime deploys. Trigger terms: persistent disk, disk, storage, mount path, sizeGB, SSD, file uploads, snapshots, disk restore, ephemeral filesystem.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-disks\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: render-disks\ndescription: >-\n  Attaches and manages persistent disks on Render services—mount paths, sizing,\n  snapshots, file transfers, and single-instance constraints. Use when the user\n  needs persistent storage, file uploads, a custom database on disk, CMS media\n  storage, or needs to understand why their service can't scale horizontally\n  or use zero-downtime deploys.\n  Trigger terms: persistent disk, disk, storage, mount path, sizeGB, SSD,\n  file uploads, snapshots, disk restore, ephemeral filesystem.\nlicense: MIT\ncompatibility: Render paid web services, private services, and background workers\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: storage\n---\n\n# Render Persistent Disks\n\nPersistent disks are high-performance SSDs you attach to a Render service to preserve filesystem changes across deploys and restarts. Without a disk, services have an **ephemeral filesystem**—all local file changes are lost on every deploy.\n\n## When to Use\n\n- Storing **file uploads**, CMS media, or user-generated content\n- Running a **self-managed database** (MySQL, MongoDB, ClickHouse) on Render\n- Deploying **stateful infrastructure** (Elasticsearch, Kafka, RabbitMQ, Mattermost)\n- Understanding **why scaling is blocked** or **zero-downtime deploys are disabled**\n- **Restoring data** from an automatic disk snapshot\n\nFor managed databases, prefer **Render Postgres** (render-postgres) or **Key Value** (render-keyvalue) over self-managed alternatives on disk.\n\n## Critical Constraints\n\nThese constraints affect architecture decisions. Understand them **before** attaching a disk:\n\n| Constraint | Impact |\n|------------|--------|\n| **Single instance only** | Cannot scale horizontally (`numInstances` must be 1, autoscaling not available) |\n| **No zero-downtime deploys** | Old instance stops before new instance starts (brief downtime on each deploy) |\n| **Runtime access only** | Disk is not available during `buildCommand` or `preDeployCommand` (those run on separate compute) |\n| **Not accessible from other services** | Only the attached service can read\u002Fwrite the disk |\n| **Not available on cron jobs** | Attach to a web service, private service, or background worker instead |\n| **Not available on one-off jobs** | One-off jobs run on separate compute without disk access |\n| **Can increase size, cannot decrease** | Start small and grow as needed |\n\n## Setup\n\n### Dashboard\n\n1. Go to your service's **Disks** page\n2. Set the **mount path** (absolute path where persistent data is stored)\n3. Choose a **size** in GB\n4. Click **Add disk** — triggers a new deploy\n\n### Blueprint\n\n```yaml\nservices:\n  - type: web\n    name: cms\n    runtime: node\n    plan: starter\n    region: oregon\n    buildCommand: npm ci && npm run build\n    startCommand: npm start\n    disk:\n      name: cms-data\n      mountPath: \u002Fvar\u002Fdata\n      sizeGB: 10\n```\n\n## Mount Path\n\nOnly files written **under the mount path** are preserved. Everything else remains ephemeral.\n\n| Runtime | Source code path | Example mount path |\n|---------|------------------|--------------------|\n| Node.js, Python, Ruby, Elixir, Rust | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc` | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` |\n| Go | `\u002Fopt\u002Frender\u002Fproject\u002Fgo\u002Fsrc\u002Fgithub.com\u002F\u003Cuser>\u002F\u003Crepo>` | `...\u002Fdata` |\n| Docker | Dockerfile's `WORKDIR` (commonly `\u002Fapp`) | `\u002Fapp\u002Fstorage` |\n\n### Disallowed mount paths\n\nCannot mount at: `\u002F`, `\u002Fopt`, `\u002Fopt\u002Frender`, `\u002Fopt\u002Frender\u002Fproject`, `\u002Fopt\u002Frender\u002Fproject\u002Fsrc`, `\u002Fhome`, `\u002Fhome\u002Frender`, `\u002Fetc`, `\u002Fetc\u002Fsecrets`.\n\nSubdirectories of these paths are fine (e.g. `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads`).\n\n## Snapshots\n\n- Render creates an **automatic snapshot every 24 hours**\n- Snapshots are available for **at least 7 days**\n- Restore from the service's **Disks** page in the Dashboard\n- **Full restore only** — you cannot restore individual files\n- **Destructive** — all changes after the snapshot are lost\n\n**Do not restore snapshots for custom database recovery.** Use database-native backup tools (mysqldump, mongodump) instead—disk snapshots may capture a corrupted database state.\n\n## File Transfers\n\n### SCP (via SSH)\n\n```bash\n# Download from service\nscp -s YOUR_SERVICE@ssh.YOUR_REGION.render.com:\u002Fmount\u002Fpath\u002Ffile .\u002Flocal-file\n\n# Upload to service\nscp -s .\u002Flocal-file YOUR_SERVICE@ssh.YOUR_REGION.render.com:\u002Fmount\u002Fpath\u002Ffile\n```\n\nRequires SSH access enabled for the service.\n\n### Magic-Wormhole\n\nAvailable on all native runtimes (install manually on Docker):\n\n```bash\n# On the service shell\nwormhole send \u002Fmount\u002Fpath\u002Ffile\n\n# On your local machine\nwormhole receive\n```\n\n## Common Patterns\n\n| Pattern | Service type | Mount path | Notes |\n|---------|-------------|------------|-------|\n| WordPress \u002F Ghost \u002F CMS | Web Service | `\u002Fvar\u002Fdata` or `\u002Fapp\u002Fcontent` | Media uploads, SQLite |\n| Self-managed MySQL | Private Service | `\u002Fvar\u002Flib\u002Fmysql` | Use mysqldump for backups, not disk snapshots |\n| File upload API | Web Service | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` | Single instance constraint |\n| Elasticsearch | Private Service | `\u002Fusr\u002Fshare\u002Felasticsearch\u002Fdata` | Stateful search infrastructure |\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Expecting horizontal scaling with a disk | Not possible — disk services are single-instance only |\n| Mounting at a disallowed path | Use a subdirectory (e.g. `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` not `\u002Fopt\u002Frender\u002Fproject\u002Fsrc`) |\n| Reading disk during build or pre-deploy | These run on separate compute — move logic to the start command |\n| Restoring disk snapshot for a database | Use database-native backups instead |\n| Starting with a large disk size | Start small — you can increase but never decrease |\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fsizing-and-snapshots.md` | Sizing guidance, snapshot lifecycle, restore procedures, cost patterns |\n\n## Related Skills\n\n- **render-web-services** — Deploy lifecycle, health checks (disk disables zero-downtime)\n- **render-private-services** — Internal services with disks (Elasticsearch, MySQL)\n- **render-blueprints** — `disk` field reference in `render.yaml`\n- **render-postgres** — Managed database alternative (no disk management needed)\n","# Render Persistent Disks\n\nPersistent disks are high-performance SSDs you attach to a Render service to preserve filesystem changes across deploys and restarts. Without a disk, services have an **ephemeral filesystem**—all local file changes are lost on every deploy.\n\n## When to Use\n\n- Storing **file uploads**, CMS media, or user-generated content\n- Running a **self-managed database** (MySQL, MongoDB, ClickHouse) on Render\n- Deploying **stateful infrastructure** (Elasticsearch, Kafka, RabbitMQ, Mattermost)\n- Understanding **why scaling is blocked** or **zero-downtime deploys are disabled**\n- **Restoring data** from an automatic disk snapshot\n\nFor managed databases, prefer **Render Postgres** (render-postgres) or **Key Value** (render-keyvalue) over self-managed alternatives on disk.\n\n## Critical Constraints\n\nThese constraints affect architecture decisions. Understand them **before** attaching a disk:\n\n| Constraint | Impact |\n|------------|--------|\n| **Single instance only** | Cannot scale horizontally (`numInstances` must be 1, autoscaling not available) |\n| **No zero-downtime deploys** | Old instance stops before new instance starts (brief downtime on each deploy) |\n| **Runtime access only** | Disk is not available during `buildCommand` or `preDeployCommand` (those run on separate compute) |\n| **Not accessible from other services** | Only the attached service can read\u002Fwrite the disk |\n| **Not available on cron jobs** | Attach to a web service, private service, or background worker instead |\n| **Not available on one-off jobs** | One-off jobs run on separate compute without disk access |\n| **Can increase size, cannot decrease** | Start small and grow as needed |\n\n## Setup\n\n### Dashboard\n\n1. Go to your service's **Disks** page\n2. Set the **mount path** (absolute path where persistent data is stored)\n3. Choose a **size** in GB\n4. Click **Add disk** — triggers a new deploy\n\n### Blueprint\n\n```yaml\nservices:\n  - type: web\n    name: cms\n    runtime: node\n    plan: starter\n    region: oregon\n    buildCommand: npm ci && npm run build\n    startCommand: npm start\n    disk:\n      name: cms-data\n      mountPath: \u002Fvar\u002Fdata\n      sizeGB: 10\n```\n\n## Mount Path\n\nOnly files written **under the mount path** are preserved. Everything else remains ephemeral.\n\n| Runtime | Source code path | Example mount path |\n|---------|------------------|--------------------|\n| Node.js, Python, Ruby, Elixir, Rust | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc` | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` |\n| Go | `\u002Fopt\u002Frender\u002Fproject\u002Fgo\u002Fsrc\u002Fgithub.com\u002F\u003Cuser>\u002F\u003Crepo>` | `...\u002Fdata` |\n| Docker | Dockerfile's `WORKDIR` (commonly `\u002Fapp`) | `\u002Fapp\u002Fstorage` |\n\n### Disallowed mount paths\n\nCannot mount at: `\u002F`, `\u002Fopt`, `\u002Fopt\u002Frender`, `\u002Fopt\u002Frender\u002Fproject`, `\u002Fopt\u002Frender\u002Fproject\u002Fsrc`, `\u002Fhome`, `\u002Fhome\u002Frender`, `\u002Fetc`, `\u002Fetc\u002Fsecrets`.\n\nSubdirectories of these paths are fine (e.g. `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads`).\n\n## Snapshots\n\n- Render creates an **automatic snapshot every 24 hours**\n- Snapshots are available for **at least 7 days**\n- Restore from the service's **Disks** page in the Dashboard\n- **Full restore only** — you cannot restore individual files\n- **Destructive** — all changes after the snapshot are lost\n\n**Do not restore snapshots for custom database recovery.** Use database-native backup tools (mysqldump, mongodump) instead—disk snapshots may capture a corrupted database state.\n\n## File Transfers\n\n### SCP (via SSH)\n\n```bash\n# Download from service\nscp -s YOUR_SERVICE@ssh.YOUR_REGION.render.com:\u002Fmount\u002Fpath\u002Ffile .\u002Flocal-file\n\n# Upload to service\nscp -s .\u002Flocal-file YOUR_SERVICE@ssh.YOUR_REGION.render.com:\u002Fmount\u002Fpath\u002Ffile\n```\n\nRequires SSH access enabled for the service.\n\n### Magic-Wormhole\n\nAvailable on all native runtimes (install manually on Docker):\n\n```bash\n# On the service shell\nwormhole send \u002Fmount\u002Fpath\u002Ffile\n\n# On your local machine\nwormhole receive\n```\n\n## Common Patterns\n\n| Pattern | Service type | Mount path | Notes |\n|---------|-------------|------------|-------|\n| WordPress \u002F Ghost \u002F CMS | Web Service | `\u002Fvar\u002Fdata` or `\u002Fapp\u002Fcontent` | Media uploads, SQLite |\n| Self-managed MySQL | Private Service | `\u002Fvar\u002Flib\u002Fmysql` | Use mysqldump for backups, not disk snapshots |\n| File upload API | Web Service | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` | Single instance constraint |\n| Elasticsearch | Private Service | `\u002Fusr\u002Fshare\u002Felasticsearch\u002Fdata` | Stateful search infrastructure |\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Expecting horizontal scaling with a disk | Not possible — disk services are single-instance only |\n| Mounting at a disallowed path | Use a subdirectory (e.g. `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` not `\u002Fopt\u002Frender\u002Fproject\u002Fsrc`) |\n| Reading disk during build or pre-deploy | These run on separate compute — move logic to the start command |\n| Restoring disk snapshot for a database | Use database-native backups instead |\n| Starting with a large disk size | Start small — you can increase but never decrease |\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fsizing-and-snapshots.md` | Sizing guidance, snapshot lifecycle, restore procedures, cost patterns |\n\n## Related Skills\n\n- **render-web-services** — Deploy lifecycle, health checks (disk disables zero-downtime)\n- **render-private-services** — Internal services with disks (Elasticsearch, MySQL)\n- **render-blueprints** — `disk` field reference in `render.yaml`\n- **render-postgres** — Managed database alternative (no disk management needed)\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"author":24,"version":25,"category":26},"Render","1.0.0","storage","Render paid web services, private services, and background workers","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-disks","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill render-disks",{"tool":40,"command":41},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill render-disks",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill render-disks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-disks\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",220,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-disks\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fsizing-and-snapshots.md",2167,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-disks\u002Freferences\u002Fsizing-and-snapshots.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"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.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"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",[],[]]