[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BD00TZNGHKP8C06BJ5NKHJ":3,"skill-same:01M7BD00TZNGHKP8C06BJ5NKHJ":66},{"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},"01M7BD00TZNGHKP8C06BJ5NKHJ","render-docker",null,"Builds and deploys Docker containers on Render—Dockerfiles, multi-stage builds, Blueprint Docker fields, private registries, layer caching, and platform constraints. Use when the user mentions Docker, Dockerfile, container images, multi-stage builds, container registry, GHCR, ECR, BuildKit, dockerContext, runtime docker or image, or optimizing Docker builds on Render.","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-docker\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: render-docker\ndescription: >-\n  Builds and deploys Docker containers on Render—Dockerfiles, multi-stage\n  builds, Blueprint Docker fields, private registries, layer caching, and\n  platform constraints. Use when the user mentions Docker,\n  Dockerfile, container images, multi-stage builds, container registry,\n  GHCR, ECR, BuildKit, dockerContext, runtime docker or image, or\n  optimizing Docker builds on Render.\nlicense: MIT\ncompatibility: >-\n  Any Render compute service (web, private, worker, cron) with runtime: docker\n  or runtime: image.\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: deployment\n---\n\n# Render Docker Deployments\n\nRender uses **BuildKit** for Docker builds. All compute service types that support custom runtimes can use **`runtime: docker`** (build from a Dockerfile in the repo) or **`runtime: image`** (pull a prebuilt image; no Dockerfile build on Render). Deeper patterns and copy-paste templates live under `references\u002F`.\n\n## When to Use\n\n- Authoring or debugging a **Dockerfile** for a Render service\n- Choosing **`runtime: docker`** vs **`runtime: image`** in a Blueprint\n- Wiring **private base images** or **prebuilt images** with registry credentials\n- **Multi-stage builds**, **build args**, **secrets**, and **layer caching**\n- **Performance** and **security** hardening of container images on Render\n\nFor full Blueprint authoring, see **render-blueprints**. For end-to-end deploy flows, see **render-deploy**.\n\n## Render Docker Builds\n\n- **BuildKit** is used for Docker builds on Render.\n- **`runtime: docker`**: Render builds an image from your repo using `dockerfilePath`, `dockerContext`, and optional `dockerCommand` (overrides image `CMD`).\n- **`runtime: image`**: Render pulls **`image.url`**; no repo-based image build. Pair with **`registryCredential`** when the registry is private.\n\n## Blueprint Configuration\n\n| Field | Role |\n|-------|------|\n| `dockerfilePath` | Path to the Dockerfile (default `.\u002FDockerfile`) |\n| `dockerContext` | Build context directory (what is sent to the daemon) |\n| `dockerCommand` | Overrides the container `CMD` after the image is built |\n| `image.url` | Image reference for `runtime: image` (registry\u002Frepo:tag or digest) |\n| `registryCredential` | Auth for private pulls; often `fromRegistryCreds` → Dashboard-stored credential |\n\nExample sketch (values illustrative):\n\n```yaml\nservices:\n  - type: web\n    name: api\n    runtime: docker\n    region: oregon\n    plan: starter\n    dockerfilePath: .\u002FDockerfile\n    dockerContext: .\n    dockerCommand: node server.js\n    envVars:\n      - key: PORT\n        value: 10000\n```\n\nFor `runtime: image`, set `image.url` and, if needed, `registryCredential` per **Registry Configuration** below.\n\n## Multi-Stage Builds\n\n**Recommended for production.** Use a **builder** stage for compilation and dependency installation, and a minimal **runner** stage that only copies artifacts and runtime files. Benefits:\n\n- Smaller images and faster pulls\n- Fewer tools and secrets in the final image (smaller attack surface)\n- Clear separation between build-time and run-time dependencies\n\nSee `references\u002Fdockerfile-patterns.md` for language-specific templates.\n\n## Build Args vs Secrets\n\n**Critical:** **Never pass secrets via `ARG`.** Build arguments are stored in image **layers** and can be recovered from the image history or intermediate layers.\n\n- Prefer **runtime environment variables** (Render **env vars** \u002F secret files) for application secrets.\n- For **build-time** secrets (e.g. private package feeds), use **Docker BuildKit secret mounts** (`RUN --mount=type=secret,...`) rather than `ARG`.\n\nTreat anything sensitive as **runtime** or **BuildKit secret mount**, not as a build arg.\n\n## Registry Configuration\n\nPrivate **base images** (for `runtime: docker`) or **prebuilt images** (`runtime: image`) need authentication:\n\n- Store credentials in the Render Dashboard under **Registry Credentials**.\n- In Blueprint, reference them with **`registryCredential.fromRegistryCreds.name`** (match the Dashboard name).\n\nSupports common registries (Docker Hub, GHCR, ECR, Google Artifact Registry, and others). Step-by-step per provider: `references\u002Fregistry-setup.md`.\n\n**Prebuilt image services** do **not** auto-deploy when the tag moves in the registry; trigger a **manual redeploy** or use a **deploy hook** when you publish a new image.\n\n## Layer Caching\n\n- Render **caches Docker layers** between builds; **order Dockerfile instructions** so that frequently unchanged layers stay early (see `references\u002Foptimization-guide.md`).\n- **Tags and caching:** mutable tags like **`latest`** can resolve to **stale cached** images. Prefer **immutable** references: **digest** (`repo\u002Fimage@sha256:...`) or **version pins** (`v1.2.3`).\n\n## Platform Specifics\n\n- Render builds **linux\u002Famd64**. Avoid assumptions about other architectures in production images.\n- **Port binding** matches native services: bind HTTP to **`0.0.0.0:$PORT`** (Render sets `PORT`).\n- **Health checks** behave like non-Docker web services (`healthCheckPath`, etc.).\n- **Secret files** from Render appear under **`\u002Fetc\u002Fsecrets\u002F`** — do not rely on repo-root secret paths inside the container unless you copy or mount them explicitly in the image.\n\n## `.dockerignore` and Start Commands\n\n- Always maintain a **`.dockerignore`** that excludes **`node_modules`**, **`.git`**, **`.env`**, build artifacts, logs, and OS junk. This shrinks context upload time and avoids leaking local files into layers. Lists and rationale: `references\u002Foptimization-guide.md`.\n- **Custom start command:** if you need multiple shell steps, use a single shell form, e.g. **`\u002Fbin\u002Fsh -c 'set -e; .\u002Fmigrate && exec node server.js'`** (prefer **`exec`** so your app receives signals for graceful shutdown).\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fdockerfile-patterns.md` | Multi-stage templates (Node, Python, Go, Ruby, Rust, static sites) |\n| `references\u002Fregistry-setup.md` | Docker Hub, GHCR, ECR, Artifact Registry + Blueprint wiring |\n| `references\u002Foptimization-guide.md` | Layer order, `.dockerignore`, BuildKit cache mounts, debugging |\n\n## Related Skills\n\n- **render-deploy** — Deploy flows, Blueprint vs Dashboard, operational steps\n- **render-blueprints** — Full `render.yaml` schema, wiring, and validation\n- **render-web-services** — Web service behavior, health checks, and HTTP edge cases\n","# Render Docker Deployments\n\nRender uses **BuildKit** for Docker builds. All compute service types that support custom runtimes can use **`runtime: docker`** (build from a Dockerfile in the repo) or **`runtime: image`** (pull a prebuilt image; no Dockerfile build on Render). Deeper patterns and copy-paste templates live under `references\u002F`.\n\n## When to Use\n\n- Authoring or debugging a **Dockerfile** for a Render service\n- Choosing **`runtime: docker`** vs **`runtime: image`** in a Blueprint\n- Wiring **private base images** or **prebuilt images** with registry credentials\n- **Multi-stage builds**, **build args**, **secrets**, and **layer caching**\n- **Performance** and **security** hardening of container images on Render\n\nFor full Blueprint authoring, see **render-blueprints**. For end-to-end deploy flows, see **render-deploy**.\n\n## Render Docker Builds\n\n- **BuildKit** is used for Docker builds on Render.\n- **`runtime: docker`**: Render builds an image from your repo using `dockerfilePath`, `dockerContext`, and optional `dockerCommand` (overrides image `CMD`).\n- **`runtime: image`**: Render pulls **`image.url`**; no repo-based image build. Pair with **`registryCredential`** when the registry is private.\n\n## Blueprint Configuration\n\n| Field | Role |\n|-------|------|\n| `dockerfilePath` | Path to the Dockerfile (default `.\u002FDockerfile`) |\n| `dockerContext` | Build context directory (what is sent to the daemon) |\n| `dockerCommand` | Overrides the container `CMD` after the image is built |\n| `image.url` | Image reference for `runtime: image` (registry\u002Frepo:tag or digest) |\n| `registryCredential` | Auth for private pulls; often `fromRegistryCreds` → Dashboard-stored credential |\n\nExample sketch (values illustrative):\n\n```yaml\nservices:\n  - type: web\n    name: api\n    runtime: docker\n    region: oregon\n    plan: starter\n    dockerfilePath: .\u002FDockerfile\n    dockerContext: .\n    dockerCommand: node server.js\n    envVars:\n      - key: PORT\n        value: 10000\n```\n\nFor `runtime: image`, set `image.url` and, if needed, `registryCredential` per **Registry Configuration** below.\n\n## Multi-Stage Builds\n\n**Recommended for production.** Use a **builder** stage for compilation and dependency installation, and a minimal **runner** stage that only copies artifacts and runtime files. Benefits:\n\n- Smaller images and faster pulls\n- Fewer tools and secrets in the final image (smaller attack surface)\n- Clear separation between build-time and run-time dependencies\n\nSee `references\u002Fdockerfile-patterns.md` for language-specific templates.\n\n## Build Args vs Secrets\n\n**Critical:** **Never pass secrets via `ARG`.** Build arguments are stored in image **layers** and can be recovered from the image history or intermediate layers.\n\n- Prefer **runtime environment variables** (Render **env vars** \u002F secret files) for application secrets.\n- For **build-time** secrets (e.g. private package feeds), use **Docker BuildKit secret mounts** (`RUN --mount=type=secret,...`) rather than `ARG`.\n\nTreat anything sensitive as **runtime** or **BuildKit secret mount**, not as a build arg.\n\n## Registry Configuration\n\nPrivate **base images** (for `runtime: docker`) or **prebuilt images** (`runtime: image`) need authentication:\n\n- Store credentials in the Render Dashboard under **Registry Credentials**.\n- In Blueprint, reference them with **`registryCredential.fromRegistryCreds.name`** (match the Dashboard name).\n\nSupports common registries (Docker Hub, GHCR, ECR, Google Artifact Registry, and others). Step-by-step per provider: `references\u002Fregistry-setup.md`.\n\n**Prebuilt image services** do **not** auto-deploy when the tag moves in the registry; trigger a **manual redeploy** or use a **deploy hook** when you publish a new image.\n\n## Layer Caching\n\n- Render **caches Docker layers** between builds; **order Dockerfile instructions** so that frequently unchanged layers stay early (see `references\u002Foptimization-guide.md`).\n- **Tags and caching:** mutable tags like **`latest`** can resolve to **stale cached** images. Prefer **immutable** references: **digest** (`repo\u002Fimage@sha256:...`) or **version pins** (`v1.2.3`).\n\n## Platform Specifics\n\n- Render builds **linux\u002Famd64**. Avoid assumptions about other architectures in production images.\n- **Port binding** matches native services: bind HTTP to **`0.0.0.0:$PORT`** (Render sets `PORT`).\n- **Health checks** behave like non-Docker web services (`healthCheckPath`, etc.).\n- **Secret files** from Render appear under **`\u002Fetc\u002Fsecrets\u002F`** — do not rely on repo-root secret paths inside the container unless you copy or mount them explicitly in the image.\n\n## `.dockerignore` and Start Commands\n\n- Always maintain a **`.dockerignore`** that excludes **`node_modules`**, **`.git`**, **`.env`**, build artifacts, logs, and OS junk. This shrinks context upload time and avoids leaking local files into layers. Lists and rationale: `references\u002Foptimization-guide.md`.\n- **Custom start command:** if you need multiple shell steps, use a single shell form, e.g. **`\u002Fbin\u002Fsh -c 'set -e; .\u002Fmigrate && exec node server.js'`** (prefer **`exec`** so your app receives signals for graceful shutdown).\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fdockerfile-patterns.md` | Multi-stage templates (Node, Python, Go, Ruby, Rust, static sites) |\n| `references\u002Fregistry-setup.md` | Docker Hub, GHCR, ECR, Artifact Registry + Blueprint wiring |\n| `references\u002Foptimization-guide.md` | Layer order, `.dockerignore`, BuildKit cache mounts, debugging |\n\n## Related Skills\n\n- **render-deploy** — Deploy flows, Blueprint vs Dashboard, operational steps\n- **render-blueprints** — Full `render.yaml` schema, wiring, and validation\n- **render-web-services** — Web service behavior, health checks, and HTTP edge cases\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"author":24,"version":25,"category":26},"Render","1.0.0","deployment","Any Render compute service (web, private, worker, cron) with runtime: docker or runtime: image.","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker","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-docker",{"tool":40,"command":41},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill render-docker",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill render-docker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002FSKILL.md",true,[48,54,58,62],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",204,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fdockerfile-patterns.md",5495,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002Freferences\u002Fdockerfile-patterns.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Foptimization-guide.md",3297,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002Freferences\u002Foptimization-guide.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fregistry-setup.md",3118,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002Freferences\u002Fregistry-setup.md",[67,74,81,88,95,102],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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",[],[]]