[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77BA2M2TE41TYX879MB3TBZ":3,"skill-same:01M77BA2M2TE41TYX879MB3TBZ":52},{"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":34,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M77BA2M2TE41TYX879MB3TBZ","render",null,"Deploy and operate apps on Render (Blueprint + one-click Dashboard deeplink, same flow as Codex render-deploy). Use when the user wants to deploy, host, or publish an app; create or edit render.yaml; add web, static, workers, cron, Postgres, or Key Value; get the Blueprint deeplink to deploy; trigger or verify deploys via API when RENDER_API_KEY is set; connect Render MCP via mcporter for direct service creation; or configure env vars, health checks, scaling, previews, and projects.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fd\u002Fdeploy-on-render\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: render\ndescription: Deploy and operate apps on Render (Blueprint + one-click Dashboard deeplink, same flow as Codex render-deploy). Use when the user wants to deploy, host, or publish an app; create or edit render.yaml; add web, static, workers, cron, Postgres, or Key Value; get the Blueprint deeplink to deploy; trigger or verify deploys via API when RENDER_API_KEY is set; connect Render MCP via mcporter for direct service creation; or configure env vars, health checks, scaling, previews, and projects.\nmetadata:\n  { \"openclaw\": { \"emoji\": \"☁️\", \"homepage\": \"https:\u002F\u002Frender.com\u002Fdocs\", \"version\": \"1.0.0\" } }\n---\n\n# Render Skill\n\nDeploy and manage applications on Render using Blueprints (`render.yaml`), the Dashboard, or the API. This skill mirrors the **Codex render-deploy** flow: analyze codebase → generate\u002Fvalidate Blueprint → commit & push → one-click Dashboard deeplink → optional API\u002Fmcporter verify or re-deploy.\n\n## When to Use This Skill\n\nActivate when the user wants to:\n- Deploy, host, or publish an application on Render\n- Create or edit a `render.yaml` Blueprint (new or existing repo)\n- Add web, static site, private, worker, or cron services; Postgres; or Key Value\n- Configure env vars, health checks, scaling, disks, or regions\n- Set up preview environments or projects\n- Validate a Blueprint or get Dashboard\u002FAPI links\n\n## Deployment Method Selection\n\n1. **If `RENDER_API_KEY` is set** → Prefer REST API or MCP (fastest; no user click). Use `references\u002Frest-api-deployment.md` for request bodies, or mcporter if configured (see `references\u002Fmcp-integration.md`).\n2. **If no API key** → Use Blueprint + deeplink (user commits, pushes, then clicks the deeplink to deploy).\n\nCheck for API key:\n\n```bash\n[ -n \"$RENDER_API_KEY\" ] && echo \"RENDER_API_KEY is set\" || echo \"RENDER_API_KEY is not set\"\n```\n\n## Happy Path (New Users)\n\nBefore deep analysis, use this short sequence to reduce friction:\n1. Ask whether they want to deploy from a **Git repo** (required for Blueprint and deeplink) or only get guidance. If no Git remote, they must create\u002Fpush one first.\n2. Ask whether the app needs a database, workers, cron, or other services so you can choose the right Blueprint shape.\n\nThen follow **Deploy to Render** below (Blueprint → push → deeplink → verify).\n\n## Prerequisites Check\n\n1. **Git remote** – Required for Blueprint deploy. Run `git remote -v`; if none, ask the user to create a repo on GitHub\u002FGitLab\u002FBitbucket, add `origin`, and push.\n2. **Render CLI (optional)** – For local validation: `render blueprints validate render.yaml`. Install: `brew install render` or [Render CLI](https:\u002F\u002Fgithub.com\u002Frender-oss\u002Fcli).\n3. **API key (optional)** – For verifying deploys or triggering re-deploys: [Dashboard → API Keys](https:\u002F\u002Fdashboard.render.com\u002Fu\u002F*\u002Fsettings#api-keys). Set `RENDER_API_KEY` in the environment.\n\n## Security Notes\n\n- **Never commit secrets to render.yaml** — always use `sync: false` for API keys, passwords, and tokens; the user fills them in the Dashboard.\n- **Validate before suggesting deployment** — run `render blueprints validate render.yaml` or use the Validate Blueprint API so invalid YAML is never pushed.\n- **Validate user-provided values** — when writing env vars or service names from user input into YAML, sanitize or quote as needed to avoid injection.\n\n## References\n\n- `references\u002Fcodebase-analysis.md` (detect runtime, build\u002Fstart commands, env vars)\n- `references\u002Fblueprint-spec.md` (root keys, service types, env vars, validation)\n- `references\u002Frest-api-deployment.md` (direct API create service: ownerId, request bodies, type mapping)\n- `references\u002Fmcp-integration.md` (Render MCP tools, mcporter usage, supported runtimes\u002Fplans\u002Fregions)\n- `references\u002Fpost-deploy-checks.md` (verify deploy status and health via API)\n- `references\u002Ftroubleshooting-basics.md` (build\u002Fstartup\u002Fruntime failures)\n- `assets\u002F` (example Blueprints: node-express.yaml, python-web.yaml, static-site.yaml, web-with-postgres.yaml)\n\n## Blueprint Basics\n\n- **File:** `render.yaml` at the **root** of the Git repository (required).\n- **Root-level keys (official spec):** `services`, `databases`, `envVarGroups`, `projects`, `ungrouped`, `previews.generation`, `previews.expireAfterDays`.\n- **Spec:** [Blueprint YAML Reference](https:\u002F\u002Frender.com\u002Fdocs\u002Fblueprint-spec). JSON Schema for IDE validation: https:\u002F\u002Frender.com\u002Fschema\u002Frender.yaml.json (e.g. YAML extension by Red Hat in VS Code\u002FCursor).\n\n**Validation:** `render blueprints validate render.yaml` (Render CLI v2.7.0+), or the [Validate Blueprint API](https:\u002F\u002Fapi-docs.render.com\u002Freference\u002Fvalidate-blueprint) endpoint.\n\n## Service Types\n\n| type       | Purpose |\n|------------|--------|\n| `web`      | Public HTTP app or static site (use `runtime: static` for static) |\n| `pserv`    | Private service (internal hostname only, no public URL) |\n| `worker`   | Background worker (runs continuously, e.g. job queues) |\n| `cron`     | Scheduled job (cron expression; runs and exits) |\n| `keyvalue` | Render Key Value instance (Redis\u002FValkey-compatible; **defined in `services`**) |\n\n**Note:** Private services use `pserv`, not `private`. Key Value is a service with `type: keyvalue`; do not use a separate root key for it in new Blueprints (some older blueprints use `keyValueStores` and `fromKeyValueStore`—prefer the official format).\n\n## Runtimes\n\nUse **`runtime`** (preferred; `env` is deprecated): `node`, `python`, `elixir`, `go`, `ruby`, `rust`, `docker`, `image`, `static`. For static sites: `type: web`, `runtime: static`, and **`staticPublishPath`** (e.g. `.\u002Fbuild` or `.\u002Fdist`) required.\n\n## Minimal Web Service\n\n```yaml\nservices:\n  - type: web\n    name: my-app\n    runtime: node\n    buildCommand: npm install\n    startCommand: npm start\n    envVars:\n      - key: NODE_ENV\n        value: production\n```\n\nPython example: `runtime: python`, `buildCommand: pip install -r requirements.txt`, `startCommand: uvicorn app.main:app --host 0.0.0.0 --port $PORT` (or gunicorn). Set `PYTHON_VERSION` \u002F `NODE_VERSION` in envVars when needed.\n\n## Static Site\n\n```yaml\n- type: web\n  name: my-blog\n  runtime: static\n  buildCommand: yarn build\n  staticPublishPath: .\u002Fbuild\n```\n\nOptional: `headers`, `routes` (redirects\u002Frewrites). See [Static Sites](https:\u002F\u002Frender.com\u002Fdocs\u002Fstatic-sites).\n\n## Environment Variables\n\n- **Literal:** `key` + `value` (never hardcode secrets).\n- **From Postgres:** `fromDatabase.name` + `fromDatabase.property` (e.g. `connectionString`).\n- **From Key Value or other service:** `fromService.type` + `fromService.name` + `fromService.property` (e.g. `connectionString`, `host`, `port`, `hostport`) or `fromService.envVarKey` for another service’s env var.\n- **Secret \u002F user-set:** `sync: false` (user is prompted in Dashboard on first create; add new secrets manually later). **Cannot be used inside env var groups.**\n- **Generated:** `generateValue: true` (base64 256-bit value).\n- **Shared:** `fromGroup: \u003CenvVarGroups[].name>` to attach an env var group.\n\nEnv groups **cannot** reference other services (no `fromDatabase`\u002F`fromService` in groups) and **cannot** use `sync: false`. Put secrets and DB\u002FKV references in **service-level** `envVars`, or reference a group and add service-specific vars alongside.\n\n## Databases (Render Postgres)\n\n```yaml\ndatabases:\n  - name: my-db\n    plan: basic-256mb\n    databaseName: my_app\n    user: my_user\n    region: oregon\n    postgresMajorVersion: \"18\"\n```\n\n**Plans (current):** `free`, `basic-256mb`, `basic-1gb`, `basic-4gb`, `pro-*`, `accelerated-*`. Legacy: `starter`, `standard`, `pro`, `pro plus` (no new DBs on legacy). Optional: `diskSizeGB`, `ipAllowList`, `readReplicas`, `highAvailability.enabled`. Reference in services: `fromDatabase.name`, `property: connectionString`.\n\n## Key Value (Redis\u002FValkey)\n\nKey Value instances are **services** with `type: keyvalue` (or deprecated `redis`). **`ipAllowList` is required:** use `[]` for internal-only, or `- source: 0.0.0.0\u002F0` to allow external.\n\n```yaml\nservices:\n  - type: keyvalue\n    name: my-cache\n    ipAllowList:\n      - source: 0.0.0.0\u002F0\n        description: everywhere\n    plan: free\n    maxmemoryPolicy: allkeys-lru\n```\n\nReference in another service: `fromService.type: keyvalue`, `fromService.name: my-cache`, `property: connectionString`. Policies: `allkeys-lru` (caching), `noeviction` (job queues), etc. See [Key Value](https:\u002F\u002Frender.com\u002Fdocs\u002Fkey-value).\n\n**Note:** Some repos use root-level `keyValueStores` and `fromKeyValueStore`; the official spec uses `services` + `fromService`. Prefer the official form for new Blueprints.\n\n## Cron Jobs\n\n```yaml\n- type: cron\n  name: my-cron\n  runtime: python\n  schedule: \"0 * * * *\"\n  buildCommand: \"true\"\n  startCommand: python scripts\u002Fdaily.py\n  envVars: []\n```\n\n`schedule` is a cron expression (minute hour day month weekday). `buildCommand` is required (use `\"true\"` if no build). Free plan not available for cron\u002Fworker\u002Fpserv.\n\n## Env Var Groups\n\nShare vars across services. No `fromDatabase`\u002F`fromService`\u002F`sync: false` inside groups—only literal values or `generateValue: true`.\n\n```yaml\nenvVarGroups:\n  - name: app-env\n    envVars:\n      - key: CONCURRENCY\n        value: \"2\"\n      - key: APP_SECRET\n        generateValue: true\n\nservices:\n  - type: web\n    name: api\n    envVars:\n      - fromGroup: app-env\n      - key: DATABASE_URL\n        fromDatabase:\n          name: my-db\n          property: connectionString\n```\n\n## Health Check, Region, Pre-deploy\n\n- **Web only:** `healthCheckPath: \u002Fhealth` for zero-downtime deploys.\n- **Region:** `region: oregon` (default), `ohio`, `virginia`, `frankfurt`, `singapore` (set at create; cannot change later).\n- **Pre-deploy:** `preDeployCommand` runs after build, before start (e.g. migrations).\n\n## Scaling\n\n- **Manual:** `numInstances: 2`.\n- **Autoscaling** (Professional workspace): `scaling.minInstances`, `scaling.maxInstances`, `scaling.targetCPUPercent` or `scaling.targetMemoryPercent`. Not available with persistent disks.\n\n## Disks, Monorepos, Docker\n\n- **Persistent disk:** `disk.name`, `disk.mountPath`, `disk.sizeGB` (web, pserv, worker).\n- **Monorepo:** `rootDir`, `buildFilter.paths` \u002F `buildFilter.ignoredPaths`, `dockerfilePath` \u002F `dockerContext`.\n- **Docker:** `runtime: docker` (build from Dockerfile) or `runtime: image` (pull from registry). Use `dockerCommand` instead of `startCommand` when needed.\n\n## Preview Environments & Projects\n\n- **Preview environments:** Root-level `previews.generation: off | manual | automatic`, optional `previews.expireAfterDays`. Per-service `previews.generation`, `previews.numInstances`, `previews.plan`.\n- **Projects\u002Fenvironments:** Root-level `projects` with `environments` (each lists `services`, `databases`, `envVarGroups`). Use for staging\u002Fproduction. Optional `ungrouped` for resources not in any environment.\n\n## Common Deployment Patterns\n\n### Full stack (web + Postgres + Key Value)\n\nWeb service with `fromDatabase` for Postgres and `fromService` for Key Value. Add one `databases` entry and one `type: keyvalue` service; reference both from the web service `envVars`. See `assets\u002Fweb-with-postgres.yaml` for Postgres; add a keyvalue service and `fromService` for Redis URL.\n\n### Microservices (API + worker + cron)\n\nMultiple services in one Blueprint: `type: web` for the API, `type: worker` for a background processor, `type: cron` for scheduled jobs. Share `envVarGroups` or repeat env vars; use `fromDatabase`\u002F`fromService` for shared DB\u002FRedis. All use the same `branch` and `buildCommand`\u002F`startCommand` as appropriate per runtime.\n\n### Preview environments for PRs\n\nSet root-level `previews.generation: automatic` (or `manual`). Optionally `previews.expireAfterDays: 7`. Each PR gets a preview URL; per-service overrides with `previews.generation`, `previews.numInstances`, or `previews.plan` when needed.\n\n## Plans (Services)\n\n`plan: free | starter | standard | pro | pro plus` (and for web\u002Fpserv\u002Fworker: `pro max`, `pro ultra`). Omit to keep existing or default to `starter` for new. Free not available for pserv, worker, cron.\n\n## Dashboard & API\n\n- **Dashboard:** https:\u002F\u002Fdashboard.render.com — New → Blueprint, connect repo, select `render.yaml`.\n- **Key Value:** https:\u002F\u002Fdashboard.render.com\u002Fnew\u002Fredis\n\n## API Access\n\nTo use the Render API from the agent (verify deploys, trigger deploys, list services\u002Flogs):\n\n1. **Get an API key:** Dashboard → Account Settings → [API Keys](https:\u002F\u002Fdashboard.render.com\u002Fu\u002F*\u002Fsettings#api-keys).\n2. **Store as env var:** Set `RENDER_API_KEY` in the environment (e.g. `skills.entries.render.env` or process env).\n3. **Authentication:** Use Bearer token: `Authorization: Bearer $RENDER_API_KEY` on all requests.\n4. **API docs:** https:\u002F\u002Fapi-docs.render.com — services, deploys, logs, validate Blueprint, etc.\n\n---\n\n# Deploy to Render (same flow as Codex render-deploy skill)\n\nGoal: get the app deployed by generating a Blueprint, then **one-click via Dashboard deeplink**; optionally **trigger or verify via API** when the user has `RENDER_API_KEY`.\n\n## Step 1: Analyze codebase and create render.yaml\n\n- Use `references\u002Fcodebase-analysis.md` to determine runtime, build\u002Fstart commands, env vars, and datastores.\n- Add or update `render.yaml` at repo root (see Blueprint sections above and `references\u002Fblueprint-spec.md`). Use `sync: false` for secrets. See `assets\u002F` for examples.\n- **Validate** before asking the user to push:\n  - CLI: `render blueprints validate render.yaml` (install: `brew install render` or [Render CLI install](https:\u002F\u002Fgithub.com\u002Frender-oss\u002Fcli)).\n  - Or API: POST to [Validate Blueprint](https:\u002F\u002Fapi-docs.render.com\u002Freference\u002Fvalidate-blueprint) with the YAML body.\n- Fix any validation errors before proceeding.\n\n## Step 2: Commit and push (required)\n\nRender reads the Blueprint from the **Git remote**. The file must be committed and pushed.\n\n```bash\ngit add render.yaml\ngit commit -m \"Add Render deployment configuration\"\ngit push origin main\n```\n\nIf there is no Git remote, stop and ask the user to create a repo on GitHub\u002FGitLab\u002FBitbucket, add it as `origin`, and push. Without a pushed repo, the Dashboard deeplink will not work.\n\n## Step 3: Dashboard deeplink (one-click deploy)\n\nGet the repo URL and build the Blueprint deeplink:\n\n```bash\ngit remote get-url origin\n```\n\nIf the URL is **SSH**, convert to **HTTPS** (Render needs HTTPS for the deeplink):\n\n| SSH | HTTPS |\n|-----|--------|\n| `git@github.com:user\u002Frepo.git` | `https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo` |\n| `git@gitlab.com:user\u002Frepo.git` | `https:\u002F\u002Fgitlab.com\u002Fuser\u002Frepo` |\n| `git@bitbucket.org:user\u002Frepo.git` | `https:\u002F\u002Fbitbucket.org\u002Fuser\u002Frepo` |\n\nPattern: replace `git@\u003Chost>:` with `https:\u002F\u002F\u003Chost>\u002F`, remove `.git` suffix.\n\n**Deeplink format:**\n```\nhttps:\u002F\u002Fdashboard.render.com\u002Fblueprint\u002Fnew?repo=\u003CREPO_HTTPS_URL>\n```\n\nExample: `https:\u002F\u002Fdashboard.render.com\u002Fblueprint\u002Fnew?repo=https:\u002F\u002Fgithub.com\u002Fusername\u002Fmy-app`\n\nGive the user this checklist:\n\n1. Confirm `render.yaml` is in the repo at the root (they just pushed it).\n2. **Click the deeplink** to open Render Dashboard.\n3. Complete Git provider OAuth if prompted.\n4. Name the Blueprint (or accept default).\n5. **Fill in secret env vars** (those with `sync: false`).\n6. Review services\u002Fdatabases, then click **Apply** to deploy.\n\nDeployment starts automatically. User can monitor in the Dashboard.\n\n## Step 4: Verify deployment (optional, needs API key)\n\nIf the user has set `RENDER_API_KEY` (e.g. in `skills.entries.render.env` or process env), the agent can verify after the user has applied the Blueprint:\n\n- **List services:** `GET https:\u002F\u002Fapi.render.com\u002Fv1\u002Fservices` — Header: `Authorization: Bearer $RENDER_API_KEY`. Find the service by name.\n- **List deploys:** `GET https:\u002F\u002Fapi.render.com\u002Fv1\u002Fservices\u002F{serviceId}\u002Fdeploys?limit=1` — Check for `status: \"live\"` to confirm success.\n- **Logs (if needed):** Render API or Dashboard → service → Logs.\n\nExample (exec tool or curl):\n```bash\ncurl -s -H \"Authorization: Bearer $RENDER_API_KEY\" \"https:\u002F\u002Fapi.render.com\u002Fv1\u002Fservices\" | head -100\ncurl -s -H \"Authorization: Bearer $RENDER_API_KEY\" \"https:\u002F\u002Fapi.render.com\u002Fv1\u002Fservices\u002F{serviceId}\u002Fdeploys?limit=1\"\n```\n\nFor a short checklist and common fixes, use `references\u002Fpost-deploy-checks.md` and `references\u002Ftroubleshooting-basics.md`.\n\n## Triggering deploys (re-deploy without push)\n\n- **After repo is connected:** Pushes to the linked branch trigger automatic deploys when auto-deploy is on.\n- **Trigger via API:** With `RENDER_API_KEY`, trigger a new deploy:\n  - **POST** `https:\u002F\u002Fapi.render.com\u002Fv1\u002Fservices\u002F{serviceId}\u002Fdeploys`\n  - Header: `Authorization: Bearer $RENDER_API_KEY`\n  - Optional body: `{ \"clearCache\": \"do_not_clear\" }` or `\"clear\"`\n- **Deploy hook (no API key):** Dashboard → service → Settings → Deploy Hook. User can set that URL as an env var (e.g. `RENDER_DEPLOY_HOOK_URL`); then the agent can run `curl -X POST \"$RENDER_DEPLOY_HOOK_URL\"` to trigger a deploy.\n\nSo: **OpenClaw can deploy** by (1) creating `render.yaml`, (2) having the user push and click the Blueprint deeplink (one-click), and optionally (3) triggering or verifying deploys via API or deploy hook when credentials are available.\n\n## Render from OpenClaw (no native MCP)\n\nOpenClaw does not load MCP servers from config. Use one of:\n\n### Option A: REST API (recommended when API key is set)\n\nUse `RENDER_API_KEY` and the Render REST API (curl\u002Fexec): create services, list services, trigger deploys, list deploys, list logs. **Request bodies and endpoints:** `references\u002Frest-api-deployment.md`.\n\n### Option B: MCP via mcporter (if installed)\n\nIf the user has **mcporter** and Render configured (URL `https:\u002F\u002Fmcp.render.com\u002Fmcp`, Bearer `$RENDER_API_KEY`), the agent can call Render MCP tools directly. **Tool list and example commands:** `references\u002Fmcp-integration.md`.\n\nExample:\n\n```bash\nmcporter call render.list_services\nmcporter call render.create_web_service name=my-api runtime=node buildCommand=\"npm ci\" startCommand=\"npm start\" repo=https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo branch=main plan=free\n```\n\nWorkspace must be set first (e.g. user: “Set my Render workspace to MyTeam”). Use `mcporter list render --schema` to see current tools and parameters.\n\n---\n\n## Checklist for New Deploys\n\n1. Add or update `render.yaml` with `services` (and optionally `databases`, `envVarGroups`, `projects`). Use `runtime` and official Key Value form (`type: keyvalue` in services, `fromService` for references).\n2. Use `sync: false` for secrets in **service** envVars only; tell user to set them in Dashboard. Never put secrets in env groups.\n3. For Key Value, set `ipAllowList` (required).\n4. Validate: `render blueprints validate render.yaml` or API.\n5. User must commit and push, then use the **Blueprint deeplink** (`https:\u002F\u002Fdashboard.render.com\u002Fblueprint\u002Fnew?repo=\u003CHTTPS_REPO_URL>`) to deploy. Optionally verify or re-deploy via API if `RENDER_API_KEY` is set.\n\n## Rules\n\n- Prefer Blueprint for full app definition; suggest Dashboard\u002FAPI only when Blueprint cannot express something.\n- Never commit real API keys or secrets; use `sync: false` and document which env vars the user must set.\n- Use `runtime` (not deprecated `env`). For Python\u002FNode set `PYTHON_VERSION`\u002F`NODE_VERSION` in envVars when required.\n- When referencing Key Value or other services, use `fromService` with correct `type` (e.g. `keyvalue`, `pserv`).\n","# Render Skill\n\nDeploy and manage applications on Render using Blueprints (`render.yaml`), the Dashboard, or the API. This skill mirrors the **Codex render-deploy** flow: analyze codebase → generate\u002Fvalidate Blueprint → commit & push → one-click Dashboard deeplink → optional API\u002Fmcporter verify or re-deploy.\n\n## When to Use This Skill\n\nActivate when the user wants to:\n- Deploy, host, or publish an application on Render\n- Create or edit a `render.yaml` Blueprint (new or existing repo)\n- Add web, static site, private, worker, or cron services; Postgres; or Key Value\n- Configure env vars, health checks, scaling, disks, or regions\n- Set up preview environments or projects\n- Validate a Blueprint or get Dashboard\u002FAPI links\n\n## Deployment Method Selection\n\n1. **If `RENDER_API_KEY` is set** → Prefer REST API or MCP (fastest; no user click). Use `references\u002Frest-api-deployment.md` for request bodies, or mcporter if configured (see `references\u002Fmcp-integration.md`).\n2. **If no API key** → Use Blueprint + deeplink (user commits, pushes, then clicks the deeplink to deploy).\n\nCheck for API key:\n\n```bash\n[ -n \"$RENDER_API_KEY\" ] && echo \"RENDER_API_KEY is set\" || echo \"RENDER_API_KEY is not set\"\n```\n\n## Happy Path (New Users)\n\nBefore deep analysis, use this short sequence to reduce friction:\n1. Ask whether they want to deploy from a **Git repo** (required for Blueprint and deeplink) or only get guidance. If no Git remote, they must create\u002Fpush one first.\n2. Ask whether the app needs a database, workers, cron, or other services so you can choose the right Blueprint shape.\n\nThen follow **Deploy to Render** below (Blueprint → push → deeplink → verify).\n\n## Prerequisites Check\n\n1. **Git remote** – Required for Blueprint deploy. Run `git remote -v`; if none, ask the user to create a repo on GitHub\u002FGitLab\u002FBitbucket, add `origin`, and push.\n2. **Render CLI (optional)** – For local validation: `render blueprints validate render.yaml`. Install: `brew install render` or [Render CLI](https:\u002F\u002Fgithub.com\u002Frender-oss\u002Fcli).\n3. **API key (optional)** – For verifying deploys or triggering re-deploys: [Dashboard → API Keys](https:\u002F\u002Fdashboard.render.com\u002Fu\u002F*\u002Fsettings#api-keys). Set `RENDER_API_KEY` in the environment.\n\n## Security Notes\n\n- **Never commit secrets to render.yaml** — always use `sync: false` for API keys, passwords, and tokens; the user fills them in the Dashboard.\n- **Validate before suggesting deployment** — run `render blueprints validate render.yaml` or use the Validate Blueprint API so invalid YAML is never pushed.\n- **Validate user-provided values** — when writing env vars or service names from user input into YAML, sanitize or quote as needed to avoid injection.\n\n## References\n\n- `references\u002Fcodebase-analysis.md` (detect runtime, build\u002Fstart commands, env vars)\n- `references\u002Fblueprint-spec.md` (root keys, service types, env vars, validation)\n- `references\u002Frest-api-deployment.md` (direct API create service: ownerId, request bodies, type mapping)\n- `references\u002Fmcp-integration.md` (Render MCP tools, mcporter usage, supported runtimes\u002Fplans\u002Fregions)\n- `references\u002Fpost-deploy-checks.md` (verify deploy status and health via API)\n- `references\u002Ftroubleshooting-basics.md` (build\u002Fstartup\u002Fruntime failures)\n- `assets\u002F` (example Blueprints: node-express.yaml, python-web.yaml, static-site.yaml, web-with-postgres.yaml)\n\n## Blueprint Basics\n\n- **File:** `render.yaml` at the **root** of the Git repository (required).\n- **Root-level keys (official spec):** `services`, `databases`, `envVarGroups`, `projects`, `ungrouped`, `previews.generation`, `previews.expireAfterDays`.\n- **Spec:** [Blueprint YAML Reference](https:\u002F\u002Frender.com\u002Fdocs\u002Fblueprint-spec). JSON Schema for IDE validation: https:\u002F\u002Frender.com\u002Fschema\u002Frender.yaml.json (e.g. YAML extension by Red Hat in VS Code\u002FCursor).\n\n**Validation:** `render blueprints validate render.yaml` (Render CLI v2.7.0+), or the [Validate Blueprint API](https:\u002F\u002Fapi-docs.render.com\u002Freference\u002Fvalidate-blueprint) endpoint.\n\n## Service Types\n\n| type       | Purpose |\n|------------|--------|\n| `web`      | Public HTTP app or static site (use `runtime: static` for static) |\n| `pserv`    | Private service (internal hostname only, no public URL) |\n| `worker`   | Background worker (runs continuously, e.g. job queues) |\n| `cron`     | Scheduled job (cron expression; runs and exits) |\n| `keyvalue` | Render Key Value instance (Redis\u002FValkey-compatible; **defined in `services`**) |\n\n**Note:** Private services use `pserv`, not `private`. Key Value is a service with `type: keyvalue`; do not use a separate root key for it in new Blueprints (some older blueprints use `keyValueStores` and `fromKeyValueStore`—prefer the official format).\n\n## Runtimes\n\nUse **`runtime`** (preferred; `env` is deprecated): `node`, `python`, `elixir`, `go`, `ruby`, `rust`, `docker`, `image`, `static`. For static sites: `type: web`, `runtime: static`, and **`staticPublishPath`** (e.g. `.\u002Fbuild` or `.\u002Fdist`) required.\n\n## Minimal Web Service\n\n```yaml\nservices:\n  - type: web\n    name: my-app\n    runtime: node\n    buildCommand: npm install\n    startCommand: npm start\n    envVars:\n      - key: NODE_ENV\n        value: production\n```\n\nPython example: `runtime: python`, `buildCommand: pip install -r requirements.txt`, `startCommand: uvicorn app.main:app --host 0.0.0.0 --port $PORT` (or gunicorn). Set `PYTHON_VERSION` \u002F `NODE_VERSION` in envVars when needed.\n\n## Static Site\n\n```yaml\n- type: web\n  name: my-blog\n  runtime: static\n  buildCommand: yarn build\n  staticPublishPath: .\u002Fbuild\n```\n\nOptional: `headers`, `routes` (redirects\u002Frewrites). See [Static Sites](https:\u002F\u002Frender.com\u002Fdocs\u002Fstatic-sites).\n\n## Environment Variables\n\n- **Literal:** `key` + `value` (never hardcode secrets).\n- **From Postgres:** `fromDatabase.name` + `fromDatabase.property` (e.g. `connectionString`).\n- **From Key Value or other service:** `fromService.type` + `fromService.name` + `fromService.property` (e.g. `connectionString`, `host`, `port`, `hostport`) or `fromService.envVarKey` for another service’s env var.\n- **Secret \u002F user-set:** `sync: false` (user is prompted in Dashboard on first create; add new secrets manually later). **Cannot be used inside env var groups.**\n- **Generated:** `generateValue: true` (base64 256-bit value).\n- **Shared:** `fromGroup: \u003CenvVarGroups[].name>` to attach an env var group.\n\nEnv groups **cannot** reference other services (no `fromDatabase`\u002F`fromService` in groups) and **cannot** use `sync: false`. Put secrets and DB\u002FKV references in **service-level** `envVars`, or reference a group and add service-specific vars alongside.\n\n## Databases (Render Postgres)\n\n```yaml\ndatabases:\n  - name: my-db\n    plan: basic-256mb\n    databaseName: my_app\n    user: my_user\n    region: oregon\n    postgresMajorVersion: \"18\"\n```\n\n**Plans (current):** `free`, `basic-256mb`, `basic-1gb`, `basic-4gb`, `pro-*`, `accelerated-*`. Legacy: `starter`, `standard`, `pro`, `pro plus` (no new DBs on legacy). Optional: `diskSizeGB`, `ipAllowList`, `readReplicas`, `highAvailability.enabled`. Reference in services: `fromDatabase.name`, `property: connectionString`.\n\n## Key Value (Redis\u002FValkey)\n\nKey Value instances are **services** with `type: keyvalue` (or deprecated `redis`). **`ipAllowList` is required:** use `[]` for internal-only, or `- source: 0.0.0.0\u002F0` to allow external.\n\n```yaml\nservices:\n  - type: keyvalue\n    name: my-cache\n    ipAllowList:\n      - source: 0.0.0.0\u002F0\n        description: everywhere\n    plan: free\n    maxmemoryPolicy: allkeys-lru\n```\n\nReference in another service: `fromService.type: keyvalue`, `fromService.name: my-cache`, `property: connectionString`. Policies: `allkeys-lru` (caching), `noeviction` (job queues), etc. See [Key Value](https:\u002F\u002Frender.com\u002Fdocs\u002Fkey-value).\n\n**Note:** Some repos use root-level `keyValueStores` and `fromKeyValueStore`; the official spec uses `services` + `fromService`. Prefer the official form for new Blueprints.\n\n## Cron Jobs\n\n```yaml\n- type: cron\n  name: my-cron\n  runtime: python\n  schedule: \"0 * * * *\"\n  buildCommand: \"true\"\n  startCommand: python scripts\u002Fdaily.py\n  envVars: []\n```\n\n`schedule` is a cron expression (minute hour day month weekday). `buildCommand` is required (use `\"true\"` if no build). Free plan not available for cron\u002Fworker\u002Fpserv.\n\n## Env Var Groups\n\nShare vars across services. No `fromDatabase`\u002F`fromService`\u002F`sync: false` inside groups—only literal values or `generateValue: true`.\n\n```yaml\nenvVarGroups:\n  - name: app-env\n    envVars:\n      - key: CONCURRENCY\n        value: \"2\"\n      - key: APP_SECRET\n        generateValue: true\n\nservices:\n  - type: web\n    name: api\n    envVars:\n      - fromGroup: app-env\n      - key: DATABASE_URL\n        fromDatabase:\n          name: my-db\n          property: connectionString\n```\n\n## Health Check, Region, Pre-deploy\n\n- **Web only:** `healthCheckPath: \u002Fhealth` for zero-downtime deploys.\n- **Region:** `region: oregon` (default), `ohio`, `virginia`, `frankfurt`, `singapore` (set at create; cannot change later).\n- **Pre-deploy:** `preDeployCommand` runs after build, before start (e.g. migrations).\n\n## Scaling\n\n- **Manual:** `numInstances: 2`.\n- **Autoscaling** (Professional workspace): `scaling.minInstances`, `scaling.maxInstances`, `scaling.targetCPUPercent` or `scaling.targetMemoryPercent`. Not available with persistent disks.\n\n## Disks, Monorepos, Docker\n\n- **Persistent disk:** `disk.name`, `disk.mountPath`, `disk.sizeGB` (web, pserv, worker).\n- **Monorepo:** `rootDir`, `buildFilter.paths` \u002F `buildFilter.ignoredPaths`, `dockerfilePath` \u002F `dockerContext`.\n- **Docker:** `runtime: docker` (build from Dockerfile) or `runtime: image` (pull from registry). Use `dockerCommand` instead of `startCommand` when needed.\n\n## Preview Environments & Projects\n\n- **Preview environments:** Root-level `previews.generation: off | manual | automatic`, optional `previews.expireAfterDays`. Per-service `previews.generation`, `previews.numInstances`, `previews.plan`.\n- **Projects\u002Fenvironments:** Root-level `projects` with `environments` (each lists `services`, `databases`, `envVarGroups`). Use for staging\u002Fproduction. Optional `ungrouped` for resources not in any environment.\n\n## Common Deployment Patterns\n\n### Full stack (web + Postgres + Key Value)\n\nWeb service with `fromDatabase` for Postgres and `fromService` for Key Value. Add one `databases` entry and one `type: keyvalue` service; reference both from the web service `envVars`. See `assets\u002Fweb-with-postgres.yaml` for Postgres; add a keyvalue service and `fromService` for Redis URL.\n\n### Microservices (API + worker + cron)\n\nMultiple services in one Blueprint: `type: web` for the API, `type: worker` for a background processor, `type: cron` for scheduled jobs. Share `envVarGroups` or repeat env vars; use `fromDatabase`\u002F`fromService` for shared DB\u002FRedis. All use the same `branch` and `buildCommand`\u002F`startCommand` as appropriate per runtime.\n\n### Preview environments for PRs\n\nSet root-level `previews.generation: automatic` (or `manual`). Optionally `previews.expireAfterDays: 7`. Each PR gets a preview URL; per-service overrides with `previews.generation`, `previews.numInstances`, or `previews.plan` when needed.\n\n## Plans (Services)\n\n`plan: free | starter | standard | pro | pro plus` (and for web\u002Fpserv\u002Fworker: `pro max`, `pro ultra`). Omit to keep existing or default to `starter` for new. Free not available for pserv, worker, cron.\n\n## Dashboard & API\n\n- **Dashboard:** https:\u002F\u002Fdashboard.render.com — New → Blueprint, connect repo, select `render.yaml`.\n- **Key Value:** https:\u002F\u002Fdashboard.render.com\u002Fnew\u002Fredis\n\n## API Access\n\nTo use the Render API from the agent (verify deploys, trigger deploys, list services\u002Flogs):\n\n1. **Get an API key:** Dashboard → Account Settings → [API Keys](https:\u002F\u002Fdashboard.render.com\u002Fu\u002F*\u002Fsettings#api-keys).\n2. **Store as env var:** Set `RENDER_API_KEY` in the environment (e.g. `skills.entries.render.env` or process env).\n3. **Authentication:** Use Bearer token: `Authorization: Bearer $RENDER_API_KEY` on all requests.\n4. **API docs:** https:\u002F\u002Fapi-docs.render.com — services, deploys, logs, validate Blueprint, etc.\n\n---\n\n# Deploy to Render (same flow as Codex render-deploy skill)\n\nGoal: get the app deployed by generating a Blueprint, then **one-click via Dashboard deeplink**; optionally **trigger or verify via API** when the user has `RENDER_API_KEY`.\n\n## Step 1: Analyze codebase and create render.yaml\n\n- Use `references\u002Fcodebase-analysis.md` to determine runtime, build\u002Fstart commands, env vars, and datastores.\n- Add or update `render.yaml` at repo root (see Blueprint sections above and `references\u002Fblueprint-spec.md`). Use `sync: false` for secrets. See `assets\u002F` for examples.\n- **Validate** before asking the user to push:\n  - CLI: `render blueprints validate render.yaml` (install: `brew install render` or [Render CLI install](https:\u002F\u002Fgithub.com\u002Frender-oss\u002Fcli)).\n  - Or API: POST to [Validate Blueprint](https:\u002F\u002Fapi-docs.render.com\u002Freference\u002Fvalidate-blueprint) with the YAML body.\n- Fix any validation errors before proceeding.\n\n## Step 2: Commit and push (required)\n\nRender reads the Blueprint from the **Git remote**. The file must be committed and pushed.\n\n```bash\ngit add render.yaml\ngit commit -m \"Add Render deployment configuration\"\ngit push origin main\n```\n\nIf there is no Git remote, stop and ask the user to create a repo on GitHub\u002FGitLab\u002FBitbucket, add it as `origin`, and push. Without a pushed repo, the Dashboard deeplink will not work.\n\n## Step 3: Dashboard deeplink (one-click deploy)\n\nGet the repo URL and build the Blueprint deeplink:\n\n```bash\ngit remote get-url origin\n```\n\nIf the URL is **SSH**, convert to **HTTPS** (Render needs HTTPS for the deeplink):\n\n| SSH | HTTPS |\n|-----|--------|\n| `git@github.com:user\u002Frepo.git` | `https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo` |\n| `git@gitlab.com:user\u002Frepo.git` | `https:\u002F\u002Fgitlab.com\u002Fuser\u002Frepo` |\n| `git@bitbucket.org:user\u002Frepo.git` | `https:\u002F\u002Fbitbucket.org\u002Fuser\u002Frepo` |\n\nPattern: replace `git@\u003Chost>:` with `https:\u002F\u002F\u003Chost>\u002F`, remove `.git` suffix.\n\n**Deeplink format:**\n```\nhttps:\u002F\u002Fdashboard.render.com\u002Fblueprint\u002Fnew?repo=\u003CREPO_HTTPS_URL>\n```\n\nExample: `https:\u002F\u002Fdashboard.render.com\u002Fblueprint\u002Fnew?repo=https:\u002F\u002Fgithub.com\u002Fusername\u002Fmy-app`\n\nGive the user this checklist:\n\n1. Confirm `render.yaml` is in the repo at the root (they just pushed it).\n2. **Click the deeplink** to open Render Dashboard.\n3. Complete Git provider OAuth if prompted.\n4. Name the Blueprint (or accept default).\n5. **Fill in secret env vars** (those with `sync: false`).\n6. Review services\u002Fdatabases, then click **Apply** to deploy.\n\nDeployment starts automatically. User can monitor in the Dashboard.\n\n## Step 4: Verify deployment (optional, needs API key)\n\nIf the user has set `RENDER_API_KEY` (e.g. in `skills.entries.render.env` or process env), the agent can verify after the user has applied the Blueprint:\n\n- **List services:** `GET https:\u002F\u002Fapi.render.com\u002Fv1\u002Fservices` — Header: `Authorization: Bearer $RENDER_API_KEY`. Find the service by name.\n- **List deploys:** `GET https:\u002F\u002Fapi.render.com\u002Fv1\u002Fservices\u002F{serviceId}\u002Fdeploys?limit=1` — Check for `status: \"live\"` to confirm success.\n- **Logs (if needed):** Render API or Dashboard → service → Logs.\n\nExample (exec tool or curl):\n```bash\ncurl -s -H \"Authorization: Bearer $RENDER_API_KEY\" \"https:\u002F\u002Fapi.render.com\u002Fv1\u002Fservices\" | head -100\ncurl -s -H \"Authorization: Bearer $RENDER_API_KEY\" \"https:\u002F\u002Fapi.render.com\u002Fv1\u002Fservices\u002F{serviceId}\u002Fdeploys?limit=1\"\n```\n\nFor a short checklist and common fixes, use `references\u002Fpost-deploy-checks.md` and `references\u002Ftroubleshooting-basics.md`.\n\n## Triggering deploys (re-deploy without push)\n\n- **After repo is connected:** Pushes to the linked branch trigger automatic deploys when auto-deploy is on.\n- **Trigger via API:** With `RENDER_API_KEY`, trigger a new deploy:\n  - **POST** `https:\u002F\u002Fapi.render.com\u002Fv1\u002Fservices\u002F{serviceId}\u002Fdeploys`\n  - Header: `Authorization: Bearer $RENDER_API_KEY`\n  - Optional body: `{ \"clearCache\": \"do_not_clear\" }` or `\"clear\"`\n- **Deploy hook (no API key):** Dashboard → service → Settings → Deploy Hook. User can set that URL as an env var (e.g. `RENDER_DEPLOY_HOOK_URL`); then the agent can run `curl -X POST \"$RENDER_DEPLOY_HOOK_URL\"` to trigger a deploy.\n\nSo: **OpenClaw can deploy** by (1) creating `render.yaml`, (2) having the user push and click the Blueprint deeplink (one-click), and optionally (3) triggering or verifying deploys via API or deploy hook when credentials are available.\n\n## Render from OpenClaw (no native MCP)\n\nOpenClaw does not load MCP servers from config. Use one of:\n\n### Option A: REST API (recommended when API key is set)\n\nUse `RENDER_API_KEY` and the Render REST API (curl\u002Fexec): create services, list services, trigger deploys, list deploys, list logs. **Request bodies and endpoints:** `references\u002Frest-api-deployment.md`.\n\n### Option B: MCP via mcporter (if installed)\n\nIf the user has **mcporter** and Render configured (URL `https:\u002F\u002Fmcp.render.com\u002Fmcp`, Bearer `$RENDER_API_KEY`), the agent can call Render MCP tools directly. **Tool list and example commands:** `references\u002Fmcp-integration.md`.\n\nExample:\n\n```bash\nmcporter call render.list_services\nmcporter call render.create_web_service name=my-api runtime=node buildCommand=\"npm ci\" startCommand=\"npm start\" repo=https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo branch=main plan=free\n```\n\nWorkspace must be set first (e.g. user: “Set my Render workspace to MyTeam”). Use `mcporter list render --schema` to see current tools and parameters.\n\n---\n\n## Checklist for New Deploys\n\n1. Add or update `render.yaml` with `services` (and optionally `databases`, `envVarGroups`, `projects`). Use `runtime` and official Key Value form (`type: keyvalue` in services, `fromService` for references).\n2. Use `sync: false` for secrets in **service** envVars only; tell user to set them in Dashboard. Never put secrets in env groups.\n3. For Key Value, set `ipAllowList` (required).\n4. Validate: `render blueprints validate render.yaml` or API.\n5. User must commit and push, then use the **Blueprint deeplink** (`https:\u002F\u002Fdashboard.render.com\u002Fblueprint\u002Fnew?repo=\u003CHTTPS_REPO_URL>`) to deploy. Optionally verify or re-deploy via API if `RENDER_API_KEY` is set.\n\n## Rules\n\n- Prefer Blueprint for full app definition; suggest Dashboard\u002FAPI only when Blueprint cannot express something.\n- Never commit real API keys or secrets; use `sync: false` and document which env vars the user must set.\n- Use `runtime` (not deprecated `env`). For Python\u002FNode set `PYTHON_VERSION`\u002F`NODE_VERSION` in envVars when required.\n- When referencing Key Value or other services, use `fromService` with correct `type` (e.g. `keyvalue`, `pserv`).\n",{"name":5,"metadata":24,"description":7},{"openclaw":25},{"emoji":26,"version":27,"homepage":28},"☁️","1.0.0","https:\u002F\u002Frender.com\u002Fdocs","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fd\u002Fdeploy-on-render",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill render",{"tool":44,"command":45},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill render",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill render","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fd\u002Fdeploy-on-render\u002FSKILL.md",true,[],[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]