[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76X6KVYA25NPN8SSABDRTPB":3,"skill-same:01M76X6KVYA25NPN8SSABDRTPB":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M76X6KVYA25NPN8SSABDRTPB","render-networking",null,"Connects Render services over the private network—internal DNS, service discovery, and cross-service communication. Use when the user needs to wire services together, resolve internal hostnames, troubleshoot connectivity between services, configure environment isolation, or understand which services can reach each other.","stanfish06\u002Fskillquarium","stanfish06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93099613?v=4","01M75F1CK4ZW109ZK3T26VN52F","Zhiyuan","01M75F1CM53VH6F79DZ8GXKKES",12,"MIT","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-networking\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: render-networking\ndescription: >-\n  Connects Render services over the private network—internal DNS, service\n  discovery, and cross-service communication. Use when the user needs to wire\n  services together, resolve internal hostnames, troubleshoot connectivity\n  between services, configure environment isolation, or understand which\n  services can reach each other.\nlicense: MIT\ncompatibility: Render services in the same region and workspace\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: networking\n---\n\n# Render private networking\n\nRender’s **private network** lets services talk to each other without exposing traffic on the public internet. Use this skill when users need internal connectivity, discovery across scaled instances, or correct URL\u002Fport behavior for Blueprints and the Dashboard.\n\n## When to Use This Skill\n\n- Designing or debugging **service-to-service** traffic on Render\n- Questions about **internal hostnames**, **internal URLs**, or **Connect > Internal** in the Dashboard\n- **Service discovery** across multiple instances (custom load balancing, mesh-style setups)\n- **Port limits**, reserved ports, or **multi-port** web services (public vs private)\n- **Free-tier** web services and **who can send vs receive** private traffic\n- **Environment isolation** (Professional+) or **AWS PrivateLink** for private egress\u002Fingress patterns\n\nFor step-by-step architecture examples and Blueprint patterns, see `references\u002Fcommunication-patterns.md`. For failure modes and fixes, see `references\u002Ftroubleshooting.md`.\n\n## Private Network Basics\n\nPrivate connectivity is available only when **all** of the following hold:\n\n- Services are in the **same region**\n- Services are in the **same workspace**\n\nIf either differs, private DNS and internal routing will not connect those services.\n\n### Who can communicate\n\n| Resource | Private inbound | Private outbound | Internal hostname |\n|----------|-----------------|------------------|-------------------|\n| **Web Service** | Yes (paid tiers; see Free tier below) | Yes | Yes |\n| **Private Service** | Yes | Yes | Yes |\n| **Background Worker** | No | Yes | No |\n| **Cron Job** | No | Yes | No |\n| **Workflow Run** | No | Yes | No |\n| **Static Site** | — | — | **Not on private network** |\n| **Managed Postgres** | Via internal URL (from allowed clients) | N\u002FA (datastore) | Via internal URL |\n| **Key Value** | Via internal URL (from allowed clients) | N\u002FA (datastore) | Via internal URL |\n\n**Free-tier Web Services:** They may **send** private traffic to other services, but they **cannot receive** inbound private traffic. Plan upgrades or topology changes apply if a free web service must accept private connections.\n\nWorkers, crons, and workflow runs initiate outbound connections (e.g., to internal URLs or private service hostnames) but are **not** reachable by internal hostname for inbound calls.\n\n## Internal Addresses\n\n- Open the service in the Render Dashboard → **Connect** → **Internal** tab for the canonical internal hostname, URL, and connection details.\n- Clients often need an **explicit scheme** in code or config, e.g. `http:\u002F\u002Fservice-name:port` or `https:\u002F\u002F...` when TLS applies—do not assume a bare hostname alone is enough for every HTTP client.\n- **URL shape:** `http:\u002F\u002F[internal-hostname]:[port]\u002Fpath` (adjust scheme\u002Fport per service).\n\n## Service Discovery\n\nFor services with **multiple instances**, Render exposes a **discovery DNS** name that resolves to **all instance IPs** for that service. The pattern is **`[hostname]-discovery`** (see Dashboard docs for the exact hostname shown for your service).\n\n- **`RENDER_DISCOVERY_SERVICE`** is set in environments where discovery applies; use it with the discovery hostname pattern for scripts and app code that need instance lists.\n- **Use case:** Custom load balancing, health aggregation, or any logic that must fan out or pick among instances explicitly instead of a single internal hostname.\n\nSee `references\u002Fcommunication-patterns.md` for discovery-oriented patterns.\n\n## Port Rules\n\n- **Maximum 75 open ports** per service.\n- **Reserved ports** (do not bind your app to these for normal use): **10000** (public HTTP proxy path), **18012**, **18013**, **19099**.\n- **Multi-port Web Services:** Only **one** port receives **public** HTTP traffic; that port must align with the **`PORT`** environment variable. **Additional** ports are for **private network** access only.\n\nWhen something fails to connect, verify the target is listening on the expected port and that the port is not reserved or blocked by misconfiguration.\n\n## Environment Isolation\n\nOn **Professional and higher** workspaces, you can configure **per-environment** rules so private traffic does **not** cross certain environment boundaries. If private calls work in one environment but not another, check workspace **environment isolation** settings before assuming DNS or app bugs.\n\n## AWS PrivateLink\n\n**Professional+** workspaces can use **AWS PrivateLink** to extend private connectivity to or from external AWS VPCs and approved endpoints. This is separate from default service-to-service private DNS; use it when the architecture requires **private** access to Render or from Render to specific AWS resources without the public internet.\n\n## Common Patterns\n\nShort summaries; full diagrams and Blueprint notes live in `references\u002Fcommunication-patterns.md`.\n\n1. **Web gateway + private backends** — Public Web Service terminates HTTP; internal calls use private hostnames and ports to Private Services or internal URLs.\n2. **Worker to database** — Background Worker (no internal hostname) connects **outbound** to Postgres or Key Value **internal URLs**.\n3. **Microservices** — Private Services (and eligible Web Services) call each other by **internal hostname:port** on the private network.\n\n## References\n\n| Document | Purpose |\n|----------|---------|\n| `references\u002Fcommunication-patterns.md` | Gateway, worker→DB, mesh, URL construction, Blueprint `fromService`, discovery load balancing, private health checks |\n| `references\u002Ftroubleshooting.md` | DNS, ports, region\u002Fworkspace, free tier, protocol, resolver, environment isolation |\n\n## Related Skills\n\n- **render-web-services** — Public web services, `PORT`, and HTTP behavior\n- **render-private-services** (planned) — Private Service–specific setup and scaling\n- **render-blueprints** — `render.yaml`, `fromService`, and multi-service wiring\n","# Render private networking\n\nRender’s **private network** lets services talk to each other without exposing traffic on the public internet. Use this skill when users need internal connectivity, discovery across scaled instances, or correct URL\u002Fport behavior for Blueprints and the Dashboard.\n\n## When to Use This Skill\n\n- Designing or debugging **service-to-service** traffic on Render\n- Questions about **internal hostnames**, **internal URLs**, or **Connect > Internal** in the Dashboard\n- **Service discovery** across multiple instances (custom load balancing, mesh-style setups)\n- **Port limits**, reserved ports, or **multi-port** web services (public vs private)\n- **Free-tier** web services and **who can send vs receive** private traffic\n- **Environment isolation** (Professional+) or **AWS PrivateLink** for private egress\u002Fingress patterns\n\nFor step-by-step architecture examples and Blueprint patterns, see `references\u002Fcommunication-patterns.md`. For failure modes and fixes, see `references\u002Ftroubleshooting.md`.\n\n## Private Network Basics\n\nPrivate connectivity is available only when **all** of the following hold:\n\n- Services are in the **same region**\n- Services are in the **same workspace**\n\nIf either differs, private DNS and internal routing will not connect those services.\n\n### Who can communicate\n\n| Resource | Private inbound | Private outbound | Internal hostname |\n|----------|-----------------|------------------|-------------------|\n| **Web Service** | Yes (paid tiers; see Free tier below) | Yes | Yes |\n| **Private Service** | Yes | Yes | Yes |\n| **Background Worker** | No | Yes | No |\n| **Cron Job** | No | Yes | No |\n| **Workflow Run** | No | Yes | No |\n| **Static Site** | — | — | **Not on private network** |\n| **Managed Postgres** | Via internal URL (from allowed clients) | N\u002FA (datastore) | Via internal URL |\n| **Key Value** | Via internal URL (from allowed clients) | N\u002FA (datastore) | Via internal URL |\n\n**Free-tier Web Services:** They may **send** private traffic to other services, but they **cannot receive** inbound private traffic. Plan upgrades or topology changes apply if a free web service must accept private connections.\n\nWorkers, crons, and workflow runs initiate outbound connections (e.g., to internal URLs or private service hostnames) but are **not** reachable by internal hostname for inbound calls.\n\n## Internal Addresses\n\n- Open the service in the Render Dashboard → **Connect** → **Internal** tab for the canonical internal hostname, URL, and connection details.\n- Clients often need an **explicit scheme** in code or config, e.g. `http:\u002F\u002Fservice-name:port` or `https:\u002F\u002F...` when TLS applies—do not assume a bare hostname alone is enough for every HTTP client.\n- **URL shape:** `http:\u002F\u002F[internal-hostname]:[port]\u002Fpath` (adjust scheme\u002Fport per service).\n\n## Service Discovery\n\nFor services with **multiple instances**, Render exposes a **discovery DNS** name that resolves to **all instance IPs** for that service. The pattern is **`[hostname]-discovery`** (see Dashboard docs for the exact hostname shown for your service).\n\n- **`RENDER_DISCOVERY_SERVICE`** is set in environments where discovery applies; use it with the discovery hostname pattern for scripts and app code that need instance lists.\n- **Use case:** Custom load balancing, health aggregation, or any logic that must fan out or pick among instances explicitly instead of a single internal hostname.\n\nSee `references\u002Fcommunication-patterns.md` for discovery-oriented patterns.\n\n## Port Rules\n\n- **Maximum 75 open ports** per service.\n- **Reserved ports** (do not bind your app to these for normal use): **10000** (public HTTP proxy path), **18012**, **18013**, **19099**.\n- **Multi-port Web Services:** Only **one** port receives **public** HTTP traffic; that port must align with the **`PORT`** environment variable. **Additional** ports are for **private network** access only.\n\nWhen something fails to connect, verify the target is listening on the expected port and that the port is not reserved or blocked by misconfiguration.\n\n## Environment Isolation\n\nOn **Professional and higher** workspaces, you can configure **per-environment** rules so private traffic does **not** cross certain environment boundaries. If private calls work in one environment but not another, check workspace **environment isolation** settings before assuming DNS or app bugs.\n\n## AWS PrivateLink\n\n**Professional+** workspaces can use **AWS PrivateLink** to extend private connectivity to or from external AWS VPCs and approved endpoints. This is separate from default service-to-service private DNS; use it when the architecture requires **private** access to Render or from Render to specific AWS resources without the public internet.\n\n## Common Patterns\n\nShort summaries; full diagrams and Blueprint notes live in `references\u002Fcommunication-patterns.md`.\n\n1. **Web gateway + private backends** — Public Web Service terminates HTTP; internal calls use private hostnames and ports to Private Services or internal URLs.\n2. **Worker to database** — Background Worker (no internal hostname) connects **outbound** to Postgres or Key Value **internal URLs**.\n3. **Microservices** — Private Services (and eligible Web Services) call each other by **internal hostname:port** on the private network.\n\n## References\n\n| Document | Purpose |\n|----------|---------|\n| `references\u002Fcommunication-patterns.md` | Gateway, worker→DB, mesh, URL construction, Blueprint `fromService`, discovery load balancing, private health checks |\n| `references\u002Ftroubleshooting.md` | DNS, ports, region\u002Fworkspace, free tier, protocol, resolver, environment isolation |\n\n## Related Skills\n\n- **render-web-services** — Public web services, `PORT`, and HTTP behavior\n- **render-private-services** (planned) — Private Service–specific setup and scaling\n- **render-blueprints** — `render.yaml`, `fromService`, and multi-service wiring\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"author":25,"version":26,"category":27},"Render","1.0.0","networking","Render services in the same region and workspace","master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Frender-networking",5,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium","https:\u002F\u002Fgithub.com\u002Fstanfish06","https:\u002F\u002Fwww.stanfish.dev\u002F","2026-11-14 21:31:37",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add stanfish06\u002Fskillquarium --skill render-networking",{"tool":43,"command":44},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill render-networking",{"tool":46,"command":47},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill render-networking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-networking\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"agents\u002Fopenai.yaml","REFERENCE","参考文档",212,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-networking\u002Fagents\u002Fopenai.yaml",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcommunication-patterns.md",3143,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-networking\u002Freferences\u002Fcommunication-patterns.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Ftroubleshooting.md",3063,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-networking\u002Freferences\u002Ftroubleshooting.md",[66,73,82,89,96,103],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M76ZJTRVA456GD7K8Y3EP82H","zarr-python","Stores and queries chunked N-D scientific arrays with Zarr-Python 3, including codecs, sharding, S3\u002FGCS storage, and NumPy\u002FDask\u002FXarray integration. Use for array layout, bounded I\u002FO, format migration, or scientific metadata preservation.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M76ZJQZ15Q1HKC5V85NHE325","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M76ZJ8ASZ4QYQ70Y6SBA4Z4S","xarray","N-dimensional labeled arrays and datasets in Python. Built on top of NumPy and Dask. It introduces labels in the form of dimensions, coordinates, and attributes on top of raw NumPy-like arrays, making data analysis in physical sciences more intuitive and less error-prone. Use for working with multi-dimensional scientific data, NetCDF\u002FGRIB\u002FZarr files, climate\u002Fweather\u002Foceanographic datasets, remote sensing, geospatial imaging, large out-of-memory datasets with Dask, and labeled array operations.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fxarray\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M76ZHFBXD6VXPQ02VCEG202B","writing-mstest-tests","Use when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-mstest-tests\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M76ZDFDF4N88RH6HSYGS7GP2","wgs-prs","End-to-end WGS to polygenic risk score pipeline. Takes paired-end FASTQ files (or a pre-existing VCF) through nf-core\u002Fsarek for variant calling, applies VCF QC (normalisation, hard filtering, Ti\u002FTv and Het\u002FHom checks), then computes polygenic risk scores via the PGS Catalog. Fills the FASTQ to VCF gap upstream of the gwas-prs skill.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwgs-prs\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M76ZCC1SC68J42QK4MDC8RCG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[]]