[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FHE0QJ6ZRH3NEX2FQ3SE4":3,"skill-same:01M79FHE0QJ6ZRH3NEX2FQ3SE4":68},{"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":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M79FHE0QJ6ZRH3NEX2FQ3SE4","render-web-services",null,"Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: render-web-services\ndescription: >-\n  Configures Render web services—port binding, TLS, health checks, custom\n  domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle.\n  Use when the user needs to set up a web service, fix health check failures,\n  add a custom domain, configure zero-downtime deploys, or troubleshoot port\n  binding issues.\nlicense: MIT\ncompatibility: Render web services (native runtimes or Docker)\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: compute\n---\n\n# Render Web Services\n\nThis skill covers **Web Service** behavior on Render: how traffic reaches your process, how deploys go live, and how optional features (domains, disks, auto-deploy) interact. Use it alongside Blueprint and networking skills when wiring `render.yaml` or Dashboard settings.\n\n## When to Use\n\n- Configuring or debugging **port binding**, **PORT**, or **multi-port** web services\n- **TLS\u002FHTTPS** expectations at the edge vs inside the container\n- **Health checks** blocking or rolling back deploys\n- **Custom domains**, DNS, and certificate provisioning\n- **Auto-deploy**, **CI-gated deploys**, and **PR preview** generation\n- **Persistent disks** and their impact on scaling and zero-downtime\n- **Deploy lifecycle**: build, pre-deploy, swap, drain, **rollback**, shutdown delay\n\nDeeper patterns live under `references\u002F` (health checks, domains, deploy phases).\n\n## Port Binding\n\n- Listen on **`0.0.0.0`** (all interfaces). Binding only to **`localhost`** or **`127.0.0.1`** prevents Render’s proxy from reaching your app.\n- Use the **`PORT`** environment variable for the HTTP listen port. Render sets it for you; the **default is often `10000`** and you can change the configured value in the service **Settings** in the Dashboard.\n- **Reserved ports** (do **not** bind your application to these for normal traffic): **`18012`**, **`18013`**, **`19099`**.\n\n### Multi-port Web Services\n\n- Only **one** port receives **public** HTTP traffic: the port aligned with **`PORT`**.\n- **Additional** open ports are reachable on Render’s **private network** only (not from the public internet through the same public URL pattern).\n\n## TLS and HTTPS\n\n- **TLS terminates at Render’s edge.** The edge speaks HTTPS to clients; your process typically receives **plain HTTP** on `PORT`.\n- **HTTPS redirect** for clients is handled by the platform; users hitting HTTP are redirected appropriately at the edge.\n- **Do not terminate TLS inside the app** for the primary public listener unless you have a rare, explicit need—standard Web Services assume HTTP behind the proxy.\n\n## Health Checks\n\n- Configure a path via **`healthCheckPath`** in a Blueprint or the **Health Check Path** field in the Dashboard.\n- Render issues **HTTP GET** requests to that path. Responses must be **`2xx` or `3xx`** for success.\n- **Failed health checks** prevent a new deploy from **going live** (the deploy does not succeed in taking production traffic as expected).\n- Render probes on a **repeat interval** with a per-request **timeout**; both are **configurable** in service settings (see Dashboard). Failed checks during rollout prevent the new revision from receiving traffic.\n- Check frequency, timeouts, and tuning guidance in `references\u002Fhealth-check-patterns.md`.\n\n## Custom Domains\n\n- Point DNS with a **CNAME** to **`[service-name].onrender.com`** (use your service’s hostname from the Dashboard).\n- Render **automatically provisions and renews** TLS certificates for verified domains.\n- **Apex** (root) domains need provider-specific **CNAME-like** or flattened records where plain CNAME at `@` is unsupported.\n- **Wildcard** domains (e.g. `*.example.com`) are supported when configured and verified.\n- Multiple custom domains per service are supported; Blueprints can list them under the **`domains`** field.\n\nSee `references\u002Fcustom-domains.md` for Dashboard steps, verification, and troubleshooting.\n\n## Auto-Deploy and PR Previews\n\n- **`autoDeployTrigger`** (Blueprint) \u002F auto-deploy settings control when production deploys run:\n  - **`commit`** — deploy on every push to the tracked branch\n  - **`checksPass`** — deploy only when required **Git checks** pass\n  - **`off`** — **manual** deploys only (Dashboard, CLI, hooks)\n- **PR previews** are configured under Blueprint **`previews.generation`** (and related preview settings); generation behavior depends on repo integration and plan.\n\n## Persistent Disks\n\n- Attach disks via the **`disk`** field in a Blueprint (or equivalent Dashboard storage settings).\n- A service with an attached persistent disk is **single-instance** only: **horizontal scaling** is not available in that configuration.\n- **Zero-downtime deploys are disabled** when a persistent disk is attached—deploys follow a different rollout pattern.\n- **Disk size increases** are allowed; **decreases** are not.\n- The disk is **not mounted during the build phase**—only at **runtime** in the running service.\n\n## Deploy Lifecycle\n\nTypical flow:\n\n1. **Build** — clone repo, run **`buildCommand`**, produce the runnable artifact\u002Fimage.\n2. **Pre-deploy command** (optional) — runs in the **new** image **before** traffic switches; use for **migrations**. If it **fails**, the deploy is **canceled**.\n3. **Deploy** — new instances start; health checks must pass before traffic moves.\n4. **Zero-downtime swap** (when applicable) — traffic shifts to new instances; **old instances drain** in-flight work.\n\n- **`maxShutdownDelaySeconds`** (range **1–300**, **default 30**) bounds how long old instances may continue handling requests during drain before shutdown.\n- **Rollbacks** — revert to a **previous successful deploy** from the Dashboard.\n\nFull sequence, hooks, filters, and CLI notes: `references\u002Fdeploy-lifecycle.md`.\n\n## Free Tier Notes\n\nFree Web Services have **separate limits**: e.g. **no custom domains** on the free instance type, and services **spin down after inactivity** (cold starts on next request). Treat free-tier behavior as distinct from paid Web Service defaults when advising on domains, uptime, and scaling.\n\n## References\n\n| Topic | File |\n|--------|------|\n| Health check design, timeouts, pitfalls | `references\u002Fhealth-check-patterns.md` |\n| Domains, DNS, TLS verification | `references\u002Fcustom-domains.md` |\n| Build, pre-deploy, drain, rollbacks, triggers | `references\u002Fdeploy-lifecycle.md` |\n\n## Related Skills\n\n- **render-deploy** — Blueprints, first-time deploy, `render.yaml` structure\n- **render-docker** — Docker-based Web Services and image\u002Fruntime details\n- **render-networking** — Private network, internal URLs, multi-port private listeners\n- **render-scaling** — Instance counts, plans, and scaling constraints (including disk interactions)\n","# Render Web Services\n\nThis skill covers **Web Service** behavior on Render: how traffic reaches your process, how deploys go live, and how optional features (domains, disks, auto-deploy) interact. Use it alongside Blueprint and networking skills when wiring `render.yaml` or Dashboard settings.\n\n## When to Use\n\n- Configuring or debugging **port binding**, **PORT**, or **multi-port** web services\n- **TLS\u002FHTTPS** expectations at the edge vs inside the container\n- **Health checks** blocking or rolling back deploys\n- **Custom domains**, DNS, and certificate provisioning\n- **Auto-deploy**, **CI-gated deploys**, and **PR preview** generation\n- **Persistent disks** and their impact on scaling and zero-downtime\n- **Deploy lifecycle**: build, pre-deploy, swap, drain, **rollback**, shutdown delay\n\nDeeper patterns live under `references\u002F` (health checks, domains, deploy phases).\n\n## Port Binding\n\n- Listen on **`0.0.0.0`** (all interfaces). Binding only to **`localhost`** or **`127.0.0.1`** prevents Render’s proxy from reaching your app.\n- Use the **`PORT`** environment variable for the HTTP listen port. Render sets it for you; the **default is often `10000`** and you can change the configured value in the service **Settings** in the Dashboard.\n- **Reserved ports** (do **not** bind your application to these for normal traffic): **`18012`**, **`18013`**, **`19099`**.\n\n### Multi-port Web Services\n\n- Only **one** port receives **public** HTTP traffic: the port aligned with **`PORT`**.\n- **Additional** open ports are reachable on Render’s **private network** only (not from the public internet through the same public URL pattern).\n\n## TLS and HTTPS\n\n- **TLS terminates at Render’s edge.** The edge speaks HTTPS to clients; your process typically receives **plain HTTP** on `PORT`.\n- **HTTPS redirect** for clients is handled by the platform; users hitting HTTP are redirected appropriately at the edge.\n- **Do not terminate TLS inside the app** for the primary public listener unless you have a rare, explicit need—standard Web Services assume HTTP behind the proxy.\n\n## Health Checks\n\n- Configure a path via **`healthCheckPath`** in a Blueprint or the **Health Check Path** field in the Dashboard.\n- Render issues **HTTP GET** requests to that path. Responses must be **`2xx` or `3xx`** for success.\n- **Failed health checks** prevent a new deploy from **going live** (the deploy does not succeed in taking production traffic as expected).\n- Render probes on a **repeat interval** with a per-request **timeout**; both are **configurable** in service settings (see Dashboard). Failed checks during rollout prevent the new revision from receiving traffic.\n- Check frequency, timeouts, and tuning guidance in `references\u002Fhealth-check-patterns.md`.\n\n## Custom Domains\n\n- Point DNS with a **CNAME** to **`[service-name].onrender.com`** (use your service’s hostname from the Dashboard).\n- Render **automatically provisions and renews** TLS certificates for verified domains.\n- **Apex** (root) domains need provider-specific **CNAME-like** or flattened records where plain CNAME at `@` is unsupported.\n- **Wildcard** domains (e.g. `*.example.com`) are supported when configured and verified.\n- Multiple custom domains per service are supported; Blueprints can list them under the **`domains`** field.\n\nSee `references\u002Fcustom-domains.md` for Dashboard steps, verification, and troubleshooting.\n\n## Auto-Deploy and PR Previews\n\n- **`autoDeployTrigger`** (Blueprint) \u002F auto-deploy settings control when production deploys run:\n  - **`commit`** — deploy on every push to the tracked branch\n  - **`checksPass`** — deploy only when required **Git checks** pass\n  - **`off`** — **manual** deploys only (Dashboard, CLI, hooks)\n- **PR previews** are configured under Blueprint **`previews.generation`** (and related preview settings); generation behavior depends on repo integration and plan.\n\n## Persistent Disks\n\n- Attach disks via the **`disk`** field in a Blueprint (or equivalent Dashboard storage settings).\n- A service with an attached persistent disk is **single-instance** only: **horizontal scaling** is not available in that configuration.\n- **Zero-downtime deploys are disabled** when a persistent disk is attached—deploys follow a different rollout pattern.\n- **Disk size increases** are allowed; **decreases** are not.\n- The disk is **not mounted during the build phase**—only at **runtime** in the running service.\n\n## Deploy Lifecycle\n\nTypical flow:\n\n1. **Build** — clone repo, run **`buildCommand`**, produce the runnable artifact\u002Fimage.\n2. **Pre-deploy command** (optional) — runs in the **new** image **before** traffic switches; use for **migrations**. If it **fails**, the deploy is **canceled**.\n3. **Deploy** — new instances start; health checks must pass before traffic moves.\n4. **Zero-downtime swap** (when applicable) — traffic shifts to new instances; **old instances drain** in-flight work.\n\n- **`maxShutdownDelaySeconds`** (range **1–300**, **default 30**) bounds how long old instances may continue handling requests during drain before shutdown.\n- **Rollbacks** — revert to a **previous successful deploy** from the Dashboard.\n\nFull sequence, hooks, filters, and CLI notes: `references\u002Fdeploy-lifecycle.md`.\n\n## Free Tier Notes\n\nFree Web Services have **separate limits**: e.g. **no custom domains** on the free instance type, and services **spin down after inactivity** (cold starts on next request). Treat free-tier behavior as distinct from paid Web Service defaults when advising on domains, uptime, and scaling.\n\n## References\n\n| Topic | File |\n|--------|------|\n| Health check design, timeouts, pitfalls | `references\u002Fhealth-check-patterns.md` |\n| Domains, DNS, TLS verification | `references\u002Fcustom-domains.md` |\n| Build, pre-deploy, drain, rollbacks, triggers | `references\u002Fdeploy-lifecycle.md` |\n\n## Related Skills\n\n- **render-deploy** — Blueprints, first-time deploy, `render.yaml` structure\n- **render-docker** — Docker-based Web Services and image\u002Fruntime details\n- **render-networking** — Private network, internal URLs, multi-port private listeners\n- **render-scaling** — Instance counts, plans, and scaling constraints (including disk interactions)\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"author":25,"version":26,"category":27},"Render","1.0.0","compute","Render web services (native runtimes or Docker)","main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Frender-web-services","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add zfifteen\u002Fskills-catalog --skill render-web-services",{"tool":42,"command":43},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill render-web-services",{"tool":45,"command":46},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill render-web-services","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Frender-web-services\u002FSKILL.md",true,[50,56,60,64],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"agents\u002Fopenai.yaml","REFERENCE","参考文档",213,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Frender-web-services\u002Fagents\u002Fopenai.yaml",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcustom-domains.md",2716,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Frender-web-services\u002Freferences\u002Fcustom-domains.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fdeploy-lifecycle.md",3814,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Frender-web-services\u002Freferences\u002Fdeploy-lifecycle.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fhealth-check-patterns.md",3088,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Frender-web-services\u002Freferences\u002Fhealth-check-patterns.md",[69,76,83,90,99,106],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","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\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]