[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BD05SAQEGRT5S0FE236F4Q":3,"skill-same:01M7BD05SAQEGRT5S0FE236F4Q":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},"01M7BD05SAQEGRT5S0FE236F4Q","render-domains",null,"Configures custom domains and TLS certificates on Render—DNS setup, CNAME records, apex domains, wildcard domains, and certificate troubleshooting. Use when the user needs to add a custom domain, configure DNS, set up HTTPS\u002FTLS, troubleshoot certificate issuance, disable the onrender.com subdomain, or add a wildcard domain. Trigger terms: custom domain, DNS, CNAME, TLS, SSL, HTTPS, certificate, apex domain, wildcard domain, onrender.com, domain verification.","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-domains\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: render-domains\ndescription: >-\n  Configures custom domains and TLS certificates on Render—DNS setup, CNAME\n  records, apex domains, wildcard domains, and certificate troubleshooting.\n  Use when the user needs to add a custom domain, configure DNS, set up\n  HTTPS\u002FTLS, troubleshoot certificate issuance, disable the onrender.com\n  subdomain, or add a wildcard domain.\n  Trigger terms: custom domain, DNS, CNAME, TLS, SSL, HTTPS, certificate,\n  apex domain, wildcard domain, onrender.com, domain verification.\nlicense: MIT\ncompatibility: Render web services and static sites\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: networking\n---\n\n# Render Custom Domains\n\nRender automatically provisions and renews TLS certificates (via Let's Encrypt and Google Trust Services) for all custom domains. All HTTP traffic is redirected to HTTPS. Custom domains work on **web services** and **static sites** only.\n\n## When to Use\n\n- Adding a **custom domain** to a web service or static site\n- Configuring **DNS records** (CNAME, A, or ALIAS) with a provider\n- Setting up a **wildcard domain** (`*.example.com`)\n- Troubleshooting **certificate issuance** or **domain verification** failures\n- Choosing between **apex** (`example.com`) and **www** (`www.example.com`)\n- **Disabling the `onrender.com` subdomain** after adding a custom domain\n\n## Domain Limits\n\n| Workspace tier | Custom domain limit |\n|---------------|---------------------|\n| Hobby | 2 custom domains (across all services) |\n| Professional+ | Unlimited |\n\n## Setup Steps\n\n### 1. Add domain in Dashboard\n\n1. Go to your service's **Settings > Custom Domains**\n2. Click **+ Add Custom Domain**\n3. Enter your domain (e.g. `app.example.com`)\n4. Click **Save**\n\nAdding a `www` subdomain automatically adds the root domain (and vice versa) with a redirect between them.\n\n### 2. Configure DNS\n\nAdd a DNS record with your provider pointing to your Render service:\n\n| Domain type | Record type | Name | Value |\n|-------------|-------------|------|-------|\n| **Subdomain** (`app.example.com`) | CNAME | `app` | `\u003Cservice>.onrender.com` |\n| **Apex** (`example.com`) on Cloudflare | CNAME (flattened) | `@` | `\u003Cservice>.onrender.com` |\n| **Apex** on other providers | A | `@` | Use Render-provided IP (see Dashboard) |\n\n**Important:** Remove any `AAAA` (IPv6) records for your domain. Render uses IPv4, and stale `AAAA` records cause unexpected behavior.\n\nProvider-specific guides:\n- [Cloudflare](https:\u002F\u002Frender.com\u002Fdocs\u002Fconfigure-cloudflare-dns)\n- [Namecheap](https:\u002F\u002Frender.com\u002Fdocs\u002Fconfigure-namecheap-dns)\n- [Other providers](https:\u002F\u002Frender.com\u002Fdocs\u002Fconfigure-other-dns)\n\n### 3. Verify domain\n\nClick **Verify** in the Dashboard. If verification fails, DNS may not have propagated yet—wait a few minutes and retry.\n\nSpeed up verification by flushing DNS caches:\n- [Google Public DNS](https:\u002F\u002Fdevelopers.google.com\u002Fspeed\u002Fpublic-dns\u002Fcache)\n- [Cloudflare DNS](https:\u002F\u002F1.1.1.1\u002Fpurge-cache\u002F)\n- [OpenDNS](https:\u002F\u002Fcachecheck.opendns.com\u002F)\n\nAfter verification, Render issues a TLS certificate automatically.\n\n## Wildcard Domains\n\nWildcard domains (`*.example.com`) route all matching subdomains to one service.\n\nRequires **three CNAME records**:\n\n| Name | Value | Purpose |\n|------|-------|---------|\n| `*` | `\u003Cservice>.onrender.com` | Routes traffic |\n| `_acme-challenge` | `\u003Cservice-id>.verify.renderdns.com` | Let's Encrypt validation |\n| `_cf-custom-hostname` | `\u003Cservice-id>.hostname.renderdns.com` | Cloudflare DDoS validation |\n\n**Cloudflare users:** If you add `*.example.com` without adding the root domain to Render, disable proxying (gray cloud) for the root domain to avoid routing conflicts.\n\n## CAA Records\n\nIf your domain has `CAA` records, add entries for Render's certificate authorities:\n\n```\nexample.com IN CAA 0 issue \"letsencrypt.org\"\nexample.com IN CAA 0 issuewild \"letsencrypt.org\"\nexample.com IN CAA 0 issue \"pki.goog; cansignhttpexchanges=yes\"\nexample.com IN CAA 0 issuewild \"pki.goog; cansignhttpexchanges=yes\"\n```\n\nWithout these, TLS certificate issuance fails silently.\n\n## Disabling the `onrender.com` Subdomain\n\nAfter adding at least one custom domain, you can disable the default `onrender.com` subdomain:\n\n1. Settings > Custom Domains > **Render Subdomain** > toggle to **Disabled**\n2. All requests to the `onrender.com` URL receive a 404\n3. Can be re-enabled at any time\n\n## Blueprint Configuration\n\nCustom domains are specified in the `domains` field:\n\n```yaml\nservices:\n  - type: web\n    name: api\n    runtime: node\n    plan: starter\n    domains:\n      - app.example.com\n      - www.example.com\n```\n\nBlueprint `domains` only **declare** the domain association. You still need to configure DNS with your provider manually.\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| AAAA records present | Remove all IPv6 AAAA records for the domain |\n| CAA records blocking issuance | Add `letsencrypt.org` and `pki.goog` entries |\n| Verifying too quickly | Wait 2-5 minutes for DNS propagation, then flush caches |\n| Cloudflare proxy + wildcard without root domain | Disable proxying (gray cloud) for the root domain |\n| Trying to add domain to a private service | Custom domains only work on web services and static sites |\n| 502 after verification | Routing rules are updating — wait a few minutes |\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fdns-configuration.md` | Provider-specific DNS setup, apex domain options, TTL recommendations |\n\n## Related Skills\n\n- **render-web-services** — Web service configuration, TLS, port binding\n- **render-static-sites** — Static site domains, CDN, headers\n- **render-blueprints** — `domains` field in `render.yaml`\n","# Render Custom Domains\n\nRender automatically provisions and renews TLS certificates (via Let's Encrypt and Google Trust Services) for all custom domains. All HTTP traffic is redirected to HTTPS. Custom domains work on **web services** and **static sites** only.\n\n## When to Use\n\n- Adding a **custom domain** to a web service or static site\n- Configuring **DNS records** (CNAME, A, or ALIAS) with a provider\n- Setting up a **wildcard domain** (`*.example.com`)\n- Troubleshooting **certificate issuance** or **domain verification** failures\n- Choosing between **apex** (`example.com`) and **www** (`www.example.com`)\n- **Disabling the `onrender.com` subdomain** after adding a custom domain\n\n## Domain Limits\n\n| Workspace tier | Custom domain limit |\n|---------------|---------------------|\n| Hobby | 2 custom domains (across all services) |\n| Professional+ | Unlimited |\n\n## Setup Steps\n\n### 1. Add domain in Dashboard\n\n1. Go to your service's **Settings > Custom Domains**\n2. Click **+ Add Custom Domain**\n3. Enter your domain (e.g. `app.example.com`)\n4. Click **Save**\n\nAdding a `www` subdomain automatically adds the root domain (and vice versa) with a redirect between them.\n\n### 2. Configure DNS\n\nAdd a DNS record with your provider pointing to your Render service:\n\n| Domain type | Record type | Name | Value |\n|-------------|-------------|------|-------|\n| **Subdomain** (`app.example.com`) | CNAME | `app` | `\u003Cservice>.onrender.com` |\n| **Apex** (`example.com`) on Cloudflare | CNAME (flattened) | `@` | `\u003Cservice>.onrender.com` |\n| **Apex** on other providers | A | `@` | Use Render-provided IP (see Dashboard) |\n\n**Important:** Remove any `AAAA` (IPv6) records for your domain. Render uses IPv4, and stale `AAAA` records cause unexpected behavior.\n\nProvider-specific guides:\n- [Cloudflare](https:\u002F\u002Frender.com\u002Fdocs\u002Fconfigure-cloudflare-dns)\n- [Namecheap](https:\u002F\u002Frender.com\u002Fdocs\u002Fconfigure-namecheap-dns)\n- [Other providers](https:\u002F\u002Frender.com\u002Fdocs\u002Fconfigure-other-dns)\n\n### 3. Verify domain\n\nClick **Verify** in the Dashboard. If verification fails, DNS may not have propagated yet—wait a few minutes and retry.\n\nSpeed up verification by flushing DNS caches:\n- [Google Public DNS](https:\u002F\u002Fdevelopers.google.com\u002Fspeed\u002Fpublic-dns\u002Fcache)\n- [Cloudflare DNS](https:\u002F\u002F1.1.1.1\u002Fpurge-cache\u002F)\n- [OpenDNS](https:\u002F\u002Fcachecheck.opendns.com\u002F)\n\nAfter verification, Render issues a TLS certificate automatically.\n\n## Wildcard Domains\n\nWildcard domains (`*.example.com`) route all matching subdomains to one service.\n\nRequires **three CNAME records**:\n\n| Name | Value | Purpose |\n|------|-------|---------|\n| `*` | `\u003Cservice>.onrender.com` | Routes traffic |\n| `_acme-challenge` | `\u003Cservice-id>.verify.renderdns.com` | Let's Encrypt validation |\n| `_cf-custom-hostname` | `\u003Cservice-id>.hostname.renderdns.com` | Cloudflare DDoS validation |\n\n**Cloudflare users:** If you add `*.example.com` without adding the root domain to Render, disable proxying (gray cloud) for the root domain to avoid routing conflicts.\n\n## CAA Records\n\nIf your domain has `CAA` records, add entries for Render's certificate authorities:\n\n```\nexample.com IN CAA 0 issue \"letsencrypt.org\"\nexample.com IN CAA 0 issuewild \"letsencrypt.org\"\nexample.com IN CAA 0 issue \"pki.goog; cansignhttpexchanges=yes\"\nexample.com IN CAA 0 issuewild \"pki.goog; cansignhttpexchanges=yes\"\n```\n\nWithout these, TLS certificate issuance fails silently.\n\n## Disabling the `onrender.com` Subdomain\n\nAfter adding at least one custom domain, you can disable the default `onrender.com` subdomain:\n\n1. Settings > Custom Domains > **Render Subdomain** > toggle to **Disabled**\n2. All requests to the `onrender.com` URL receive a 404\n3. Can be re-enabled at any time\n\n## Blueprint Configuration\n\nCustom domains are specified in the `domains` field:\n\n```yaml\nservices:\n  - type: web\n    name: api\n    runtime: node\n    plan: starter\n    domains:\n      - app.example.com\n      - www.example.com\n```\n\nBlueprint `domains` only **declare** the domain association. You still need to configure DNS with your provider manually.\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| AAAA records present | Remove all IPv6 AAAA records for the domain |\n| CAA records blocking issuance | Add `letsencrypt.org` and `pki.goog` entries |\n| Verifying too quickly | Wait 2-5 minutes for DNS propagation, then flush caches |\n| Cloudflare proxy + wildcard without root domain | Disable proxying (gray cloud) for the root domain |\n| Trying to add domain to a private service | Custom domains only work on web services and static sites |\n| 502 after verification | Routing rules are updating — wait a few minutes |\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fdns-configuration.md` | Provider-specific DNS setup, apex domain options, TTL recommendations |\n\n## Related Skills\n\n- **render-web-services** — Web service configuration, TLS, port binding\n- **render-static-sites** — Static site domains, CDN, headers\n- **render-blueprints** — `domains` field in `render.yaml`\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"author":24,"version":25,"category":26},"Render","1.0.0","networking","Render web services and static sites","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-domains","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-domains",{"tool":40,"command":41},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill render-domains",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill render-domains","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-domains\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",205,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-domains\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fdns-configuration.md",3360,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-domains\u002Freferences\u002Fdns-configuration.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",[],[]]