[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BD1FS63PP7JKZBM93V1DMV":3,"skill-same:01M7BD1FS63PP7JKZBM93V1DMV":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},"01M7BD1FS63PP7JKZBM93V1DMV","render-private-services",null,"Configures Render private services—internal-only apps that accept traffic exclusively from other Render services over the private network. Use when the user needs an internal API, microservice, gRPC server, sidecar, or any service that should not be publicly accessible. Also use when choosing between a private service and a background worker. Trigger terms: private service, pserv, internal service, internal API, microservice, gRPC, not public, private network service.","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-private-services\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: render-private-services\ndescription: >-\n  Configures Render private services—internal-only apps that accept traffic\n  exclusively from other Render services over the private network. Use when\n  the user needs an internal API, microservice, gRPC server, sidecar, or any\n  service that should not be publicly accessible. Also use when choosing\n  between a private service and a background worker.\n  Trigger terms: private service, pserv, internal service, internal API,\n  microservice, gRPC, not public, private network service.\nlicense: MIT\ncompatibility: Render private services (paid plans)\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: compute\n---\n\n# Render Private Services\n\nPrivate services are identical to web services except they have **no public URL**. They are reachable only by other Render services on the same **private network** (same region + workspace). Use them for internal APIs, microservices, gRPC servers, sidecar processes, and anything that should never face the internet.\n\n## When to Use\n\n- Building an **internal API** or **microservice** behind a public gateway\n- Running a **gRPC**, **TCP**, or other non-HTTP server that only your services call\n- Deploying infrastructure components (**Elasticsearch**, **ClickHouse**, **RabbitMQ**)\n- Choosing between a **private service** and a **background worker**\n\nFor public-facing HTTP services, use **render-web-services**. For services that don't receive any traffic, use **render-background-workers**.\n\n## Private Service vs Background Worker\n\n| Criterion | Private Service | Background Worker |\n|-----------|----------------|-------------------|\n| Binds to a port | **Yes** (required) | No |\n| Receives private network traffic | **Yes** | No |\n| Sends outbound traffic | Yes | Yes |\n| Has internal hostname | **Yes** | No |\n| Use case | Internal APIs, gRPC, TCP servers | Queue consumers, async processors |\n\n**Rule of thumb:** If the process **listens on a port** and other services call it, it's a private service. If it **pulls work from a queue** and never receives requests, it's a background worker.\n\n## How Private Services Work\n\n- No `onrender.com` subdomain—not reachable from the internet\n- Reachable at `\u003Cservice-name>:\u003Cport>` on the private network by services in the same region and workspace\n- Can listen on **any port** (except restricted system ports)—not limited to HTTP or port 10000\n- Supports **any protocol**: HTTP, gRPC, TCP, WebSocket, custom binary protocols\n- Same build\u002Fdeploy lifecycle as web services (build command, start command, pre-deploy, health checks via the private network)\n- Supports persistent disks, scaling, Docker runtime—same capabilities as web services\n\n## Connecting to a Private Service\n\nOther services reference a private service via its **internal hostname and port**:\n\n```\nhttp:\u002F\u002F\u003Cservice-name>:\u003Cport>\n```\n\nIn Blueprints, wire the address using `fromService`:\n\n```yaml\n- key: INTERNAL_API_URL\n  fromService:\n    name: my-api\n    type: pserv\n    property: hostport\n```\n\nAvailable `fromService` properties for `pserv`:\n\n| Property | Value |\n|----------|-------|\n| `host` | Internal hostname (e.g. `my-api`) |\n| `port` | Port the service listens on |\n| `hostport` | `host:port` combined (e.g. `my-api:10000`) |\n\nYou can also reference a specific env var from the private service using `envVarKey` instead of `property`.\n\n## Port Binding\n\nPrivate services **must bind to at least one port**. If your process does not need to receive traffic, create a background worker instead.\n\n- Bind to `0.0.0.0` (not `127.0.0.1` or `localhost`)\n- The `PORT` env var defaults to `10000`, but you can listen on any non-restricted port\n- For non-HTTP protocols (gRPC, TCP), configure your server on the desired port and tell consumers the `hostport`\n\n## Blueprint Configuration\n\n```yaml\nservices:\n  - type: pserv\n    name: internal-api\n    runtime: node\n    region: oregon\n    plan: starter\n    buildCommand: npm ci && npm run build\n    startCommand: npm start\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: db\n          property: connectionString\n```\n\n### Microservices pattern (gateway + internal services)\n\n```yaml\nservices:\n  - type: web\n    name: gateway\n    runtime: node\n    plan: starter\n    region: oregon\n    buildCommand: npm ci && npm run build\n    startCommand: npm start\n    envVars:\n      - key: USER_SERVICE_URL\n        fromService:\n          name: user-service\n          type: pserv\n          property: hostport\n      - key: BILLING_SERVICE_URL\n        fromService:\n          name: billing-service\n          type: pserv\n          property: hostport\n\n  - type: pserv\n    name: user-service\n    runtime: node\n    plan: starter\n    region: oregon\n    buildCommand: npm ci\n    startCommand: node server.js\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: db\n          property: connectionString\n\n  - type: pserv\n    name: billing-service\n    runtime: python\n    plan: starter\n    region: oregon\n    buildCommand: pip install -r requirements.txt\n    startCommand: gunicorn billing:app\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: db\n          property: connectionString\n```\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fpatterns.md` | Microservice topology, gRPC setup, sidecar patterns, health checks for private services |\n\n## Related Skills\n\n- **render-web-services** — Public HTTP services\n- **render-networking** — Private network, DNS, service discovery\n- **render-background-workers** — Services that don't receive traffic\n- **render-blueprints** — Full `render.yaml` schema, `fromService` wiring\n- **render-scaling** — Instance types and autoscaling for private services\n","# Render Private Services\n\nPrivate services are identical to web services except they have **no public URL**. They are reachable only by other Render services on the same **private network** (same region + workspace). Use them for internal APIs, microservices, gRPC servers, sidecar processes, and anything that should never face the internet.\n\n## When to Use\n\n- Building an **internal API** or **microservice** behind a public gateway\n- Running a **gRPC**, **TCP**, or other non-HTTP server that only your services call\n- Deploying infrastructure components (**Elasticsearch**, **ClickHouse**, **RabbitMQ**)\n- Choosing between a **private service** and a **background worker**\n\nFor public-facing HTTP services, use **render-web-services**. For services that don't receive any traffic, use **render-background-workers**.\n\n## Private Service vs Background Worker\n\n| Criterion | Private Service | Background Worker |\n|-----------|----------------|-------------------|\n| Binds to a port | **Yes** (required) | No |\n| Receives private network traffic | **Yes** | No |\n| Sends outbound traffic | Yes | Yes |\n| Has internal hostname | **Yes** | No |\n| Use case | Internal APIs, gRPC, TCP servers | Queue consumers, async processors |\n\n**Rule of thumb:** If the process **listens on a port** and other services call it, it's a private service. If it **pulls work from a queue** and never receives requests, it's a background worker.\n\n## How Private Services Work\n\n- No `onrender.com` subdomain—not reachable from the internet\n- Reachable at `\u003Cservice-name>:\u003Cport>` on the private network by services in the same region and workspace\n- Can listen on **any port** (except restricted system ports)—not limited to HTTP or port 10000\n- Supports **any protocol**: HTTP, gRPC, TCP, WebSocket, custom binary protocols\n- Same build\u002Fdeploy lifecycle as web services (build command, start command, pre-deploy, health checks via the private network)\n- Supports persistent disks, scaling, Docker runtime—same capabilities as web services\n\n## Connecting to a Private Service\n\nOther services reference a private service via its **internal hostname and port**:\n\n```\nhttp:\u002F\u002F\u003Cservice-name>:\u003Cport>\n```\n\nIn Blueprints, wire the address using `fromService`:\n\n```yaml\n- key: INTERNAL_API_URL\n  fromService:\n    name: my-api\n    type: pserv\n    property: hostport\n```\n\nAvailable `fromService` properties for `pserv`:\n\n| Property | Value |\n|----------|-------|\n| `host` | Internal hostname (e.g. `my-api`) |\n| `port` | Port the service listens on |\n| `hostport` | `host:port` combined (e.g. `my-api:10000`) |\n\nYou can also reference a specific env var from the private service using `envVarKey` instead of `property`.\n\n## Port Binding\n\nPrivate services **must bind to at least one port**. If your process does not need to receive traffic, create a background worker instead.\n\n- Bind to `0.0.0.0` (not `127.0.0.1` or `localhost`)\n- The `PORT` env var defaults to `10000`, but you can listen on any non-restricted port\n- For non-HTTP protocols (gRPC, TCP), configure your server on the desired port and tell consumers the `hostport`\n\n## Blueprint Configuration\n\n```yaml\nservices:\n  - type: pserv\n    name: internal-api\n    runtime: node\n    region: oregon\n    plan: starter\n    buildCommand: npm ci && npm run build\n    startCommand: npm start\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: db\n          property: connectionString\n```\n\n### Microservices pattern (gateway + internal services)\n\n```yaml\nservices:\n  - type: web\n    name: gateway\n    runtime: node\n    plan: starter\n    region: oregon\n    buildCommand: npm ci && npm run build\n    startCommand: npm start\n    envVars:\n      - key: USER_SERVICE_URL\n        fromService:\n          name: user-service\n          type: pserv\n          property: hostport\n      - key: BILLING_SERVICE_URL\n        fromService:\n          name: billing-service\n          type: pserv\n          property: hostport\n\n  - type: pserv\n    name: user-service\n    runtime: node\n    plan: starter\n    region: oregon\n    buildCommand: npm ci\n    startCommand: node server.js\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: db\n          property: connectionString\n\n  - type: pserv\n    name: billing-service\n    runtime: python\n    plan: starter\n    region: oregon\n    buildCommand: pip install -r requirements.txt\n    startCommand: gunicorn billing:app\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: db\n          property: connectionString\n```\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fpatterns.md` | Microservice topology, gRPC setup, sidecar patterns, health checks for private services |\n\n## Related Skills\n\n- **render-web-services** — Public HTTP services\n- **render-networking** — Private network, DNS, service discovery\n- **render-background-workers** — Services that don't receive traffic\n- **render-blueprints** — Full `render.yaml` schema, `fromService` wiring\n- **render-scaling** — Instance types and autoscaling for private services\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"author":24,"version":25,"category":26},"Render","1.0.0","compute","Render private services (paid plans)","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-private-services","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-private-services",{"tool":40,"command":41},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill render-private-services",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill render-private-services","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-private-services\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",229,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-private-services\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fpatterns.md",3353,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-private-services\u002Freferences\u002Fpatterns.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",[],[]]