[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FFKB40Z9WFQ4ZBDFV3JMM":3,"skill-same:01M79FFKB40Z9WFQ4ZBDFV3JMM":64},{"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},"01M79FFKB40Z9WFQ4ZBDFV3JMM","render-env-vars",null,"Configures environment variables, secrets, and env groups on Render. Use when the user needs to set env vars, wire secrets between services, create env groups, use generateValue, set sync: false, or troubleshoot missing or incorrect environment variable values in Blueprints or the Dashboard.","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-env-vars\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: render-env-vars\ndescription: >-\n  Configures environment variables, secrets, and env groups on Render. Use when\n  the user needs to set env vars, wire secrets between services, create env\n  groups, use generateValue, set sync: false, or troubleshoot missing or\n  incorrect environment variable values in Blueprints or the Dashboard.\nlicense: MIT\ncompatibility: Render Dashboard, CLI, or MCP tools\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: configuration\n---\n\n# Environment Variables on Render\n\nRender exposes configuration to services as **environment variables**. Values are always **strings** at the platform layer—applications must parse numbers, booleans, and structured data explicitly.\n\nThere are **three** primary ways to set variables:\n\n1. **Render Dashboard** — per-service UI, bulk import from `.env`, save\u002Fredeploy options\n2. **Blueprint** — `envVars` (and related keys) in `render.yaml`\n3. **MCP \u002F API** — e.g. `update_environment_variables` on a service\n\nDeep wiring patterns, full platform variable tables, and language-specific notes live under `references\u002F`.\n\n## When to Use This Skill\n\nUse this skill when users want to:\n\n- Add, change, or remove environment variables or secrets\n- Understand Dashboard vs Blueprint vs API\u002FMCP flows\n- Use **environment groups** for shared configuration\n- Wire `fromDatabase`, `fromService`, `fromGroup`, `sync: false`, or `generateValue` in Blueprints\n- Debug missing vars, secret files, precedence, or platform-injected names\n\nFor full Blueprint authoring, pair with **render-blueprints**. For first-time deploys, **render-deploy**. For web service behavior and ports, **render-web-services**.\n\n## Setting Variables\n\n### Dashboard\n\n- Add variables **individually** (name + value) or **in bulk** by pasting\u002Fuploading a `.env`-style file.\n- **Save options** typically include:\n  - **Save and rebuild & deploy** — picks up build-time changes\n  - **Deploy only** — runtime change without a full rebuild (when applicable)\n  - **Save only** — persist without triggering a deploy\n\nUse Dashboard edits when iterating quickly or when the repo should not carry certain values.\n\n### Blueprint (`render.yaml`)\n\nDeclare `envVars` on each service. Values can be literals, generated secrets, sync-disabled prompts, or references to databases, other services, or env groups. See **Blueprint Wiring** below and `references\u002Fwiring-reference.md` for exhaustive patterns and YAML.\n\n### MCP \u002F API\n\nAutomation tools can set variables on existing services (e.g. `update_environment_variables`). Useful for CI, rotation, or keeping Dashboard state in sync with external secret stores—without committing secrets to Git.\n\n## Secret Management\n\n- **`sync: false`** — Render prompts in the Dashboard for the value **only on initial Blueprint setup** when the resource is first created. On **Blueprint updates**, `sync: false` is **ignored** (values are not re-prompted from the file alone). These vars are **excluded from preview environments** and are **invalid inside environment groups**.\n- **`generateValue: true`** — Render generates a **base64-encoded 256-bit** random value at provision time. Use for passwords, signing keys, or tokens that do not need human-chosen values.\n- **Never commit real secrets** in `render.yaml` as plain `value:` entries. Prefer Dashboard, secret manager integration, `generateValue`, or `sync: false` with Dashboard entry.\n\n### Secret files\n\n- Store sensitive file content as **secret files** (not inline env strings). They appear as **plaintext files** under **`\u002Fetc\u002Fsecrets\u002F\u003Cfilename>`**.\n- **Combined limit**: **1 MB** total secret file payload per service or per linked env group (as applicable to your setup).\n- **Docker**: secret files are available under **`\u002Fetc\u002Fsecrets\u002F`** on the running instance.\n\n## Environment Groups\n\n**Environment groups** are named collections of variables linked to **multiple services**.\n\n- **Precedence**: **Service-level** variables **override** variables from linked groups with the same name.\n- **Multiple groups** on one service: the group that was **most recently created** wins for overlapping keys. This ordering is **not documented as stable**—avoid relying on it; use distinct names or consolidate groups.\n- Groups can be **scoped to a project environment** so staging and production differ without duplicating every service definition.\n\n## Blueprint Wiring (Summary)\n\nFull syntax, examples, and edge cases: `references\u002Fwiring-reference.md`. Authoritative Blueprint docs: **render-blueprints** skill.\n\n| Mechanism | Role |\n|-----------|------|\n| `value` | Hardcoded string (non-secret config only) |\n| `generateValue: true` | Platform-generated secret |\n| `sync: false` | Dashboard prompt on **initial** create only |\n| `fromDatabase` | Inject DB fields (`connectionString`, `host`, `port`, `user`, `password`, `database`) |\n| `fromService` | Key Value: `type: keyvalue` + properties; private\u002Fweb: `host`, `hostport`, or `envVarKey` |\n| `fromGroup` | Link all vars from a named group |\n\n## Platform-Injected Variables\n\nRender sets **read-only** variables your app can read at runtime (and some at build). A concise list:\n\n| Variable | Typical meaning |\n|----------|-----------------|\n| `RENDER` | `\"true\"` when running on Render |\n| `RENDER_SERVICE_TYPE` | Service kind (e.g. web, worker) |\n| `RENDER_SERVICE_ID` | Service identifier |\n| `RENDER_SERVICE_NAME` | Human-readable service name |\n| `RENDER_INSTANCE_ID` | Current instance |\n| `RENDER_EXTERNAL_URL` | Public URL (when applicable) |\n| `RENDER_EXTERNAL_HOSTNAME` | Public hostname |\n| `RENDER_DISCOVERY_SERVICE` | Service discovery hostname (private network) |\n| `RENDER_GIT_COMMIT` | Deployed commit SHA |\n| `RENDER_GIT_BRANCH` | Branch for this deploy |\n| `PORT` | HTTP port to bind (**default `10000`**) |\n| `IS_PULL_REQUEST` | Preview deploy indicator |\n| `RENDER_CPU_COUNT` | vCPU count for the instance |\n| `RENDER_WEB_CONCURRENCY` | Suggested worker\u002Fprocess count hint |\n\nBuild vs runtime availability, language version env vars, and **WEB_CONCURRENCY** defaults: `references\u002Fplatform-variables.md`.\n\n## Runtime-Specific Defaults\n\nRender and buildpacks may set defaults (verify in your service’s **Environment** tab):\n\n| Runtime | Notable defaults |\n|---------|------------------|\n| **Node.js** | `NODE_ENV=production` |\n| **Python** | `PYTHON_VERSION` (pinned by build); Gunicorn-oriented images often set `GUNICORN_CMD_ARGS` to bind **`0.0.0.0:10000`** |\n| **Ruby** | `RAILS_ENV=production`, `RAILS_LOG_TO_STDOUT=true` |\n| **Go** | `GO111MODULE=on` (legacy modules flag; still seen on older stacks) |\n| **Rust** | `ROCKET_PORT=10000` (Rocket convention) |\n\nAlways bind HTTP servers to **`0.0.0.0`** and **`PORT`** (or the stack’s documented port env) unless using a static site or custom Docker entrypoint.\n\n## Common Issues\n\n1. **Everything is a string** — `DEBUG=false` is truthy in many parsers; use explicit comparison or typed config loaders.\n2. **`WEB_CONCURRENCY`** — Default behavior changed for services **created after December 8, 2025**. Compare with older services when debugging worker counts; see `references\u002Fplatform-variables.md`.\n3. **Undocumented `RENDER_*` variables** — Names and semantics may change; do not depend on undocumented injection for critical logic.\n4. **Blueprint vs Dashboard drift** — Editing only `render.yaml` does not retroactively apply `sync: false` prompts on update; merge strategy for env keys is easy to misunderstand—test in a scratch service.\n5. **Secret file paths** — Code must read **`\u002Fetc\u002Fsecrets\u002F\u003Cfilename>`**; wrong paths or missing mounts usually show as file-not-found at runtime.\n\n## References\n\n- `references\u002Fwiring-reference.md` — Complete Blueprint `envVar` wiring, YAML examples, precedence, edge cases\n- `references\u002Fplatform-variables.md` — Injected variables (build vs runtime), language versions, concurrency, reading vars from code\n\n## Related Skills\n\n- **render-blueprints** — Full Blueprint authoring, validation, multi-service layouts\n- **render-deploy** — First deploy, repo requirements, MCP vs YAML\n- **render-web-services** — Ports, health checks, scaling behavior tied to env-driven servers\n","# Environment Variables on Render\n\nRender exposes configuration to services as **environment variables**. Values are always **strings** at the platform layer—applications must parse numbers, booleans, and structured data explicitly.\n\nThere are **three** primary ways to set variables:\n\n1. **Render Dashboard** — per-service UI, bulk import from `.env`, save\u002Fredeploy options\n2. **Blueprint** — `envVars` (and related keys) in `render.yaml`\n3. **MCP \u002F API** — e.g. `update_environment_variables` on a service\n\nDeep wiring patterns, full platform variable tables, and language-specific notes live under `references\u002F`.\n\n## When to Use This Skill\n\nUse this skill when users want to:\n\n- Add, change, or remove environment variables or secrets\n- Understand Dashboard vs Blueprint vs API\u002FMCP flows\n- Use **environment groups** for shared configuration\n- Wire `fromDatabase`, `fromService`, `fromGroup`, `sync: false`, or `generateValue` in Blueprints\n- Debug missing vars, secret files, precedence, or platform-injected names\n\nFor full Blueprint authoring, pair with **render-blueprints**. For first-time deploys, **render-deploy**. For web service behavior and ports, **render-web-services**.\n\n## Setting Variables\n\n### Dashboard\n\n- Add variables **individually** (name + value) or **in bulk** by pasting\u002Fuploading a `.env`-style file.\n- **Save options** typically include:\n  - **Save and rebuild & deploy** — picks up build-time changes\n  - **Deploy only** — runtime change without a full rebuild (when applicable)\n  - **Save only** — persist without triggering a deploy\n\nUse Dashboard edits when iterating quickly or when the repo should not carry certain values.\n\n### Blueprint (`render.yaml`)\n\nDeclare `envVars` on each service. Values can be literals, generated secrets, sync-disabled prompts, or references to databases, other services, or env groups. See **Blueprint Wiring** below and `references\u002Fwiring-reference.md` for exhaustive patterns and YAML.\n\n### MCP \u002F API\n\nAutomation tools can set variables on existing services (e.g. `update_environment_variables`). Useful for CI, rotation, or keeping Dashboard state in sync with external secret stores—without committing secrets to Git.\n\n## Secret Management\n\n- **`sync: false`** — Render prompts in the Dashboard for the value **only on initial Blueprint setup** when the resource is first created. On **Blueprint updates**, `sync: false` is **ignored** (values are not re-prompted from the file alone). These vars are **excluded from preview environments** and are **invalid inside environment groups**.\n- **`generateValue: true`** — Render generates a **base64-encoded 256-bit** random value at provision time. Use for passwords, signing keys, or tokens that do not need human-chosen values.\n- **Never commit real secrets** in `render.yaml` as plain `value:` entries. Prefer Dashboard, secret manager integration, `generateValue`, or `sync: false` with Dashboard entry.\n\n### Secret files\n\n- Store sensitive file content as **secret files** (not inline env strings). They appear as **plaintext files** under **`\u002Fetc\u002Fsecrets\u002F\u003Cfilename>`**.\n- **Combined limit**: **1 MB** total secret file payload per service or per linked env group (as applicable to your setup).\n- **Docker**: secret files are available under **`\u002Fetc\u002Fsecrets\u002F`** on the running instance.\n\n## Environment Groups\n\n**Environment groups** are named collections of variables linked to **multiple services**.\n\n- **Precedence**: **Service-level** variables **override** variables from linked groups with the same name.\n- **Multiple groups** on one service: the group that was **most recently created** wins for overlapping keys. This ordering is **not documented as stable**—avoid relying on it; use distinct names or consolidate groups.\n- Groups can be **scoped to a project environment** so staging and production differ without duplicating every service definition.\n\n## Blueprint Wiring (Summary)\n\nFull syntax, examples, and edge cases: `references\u002Fwiring-reference.md`. Authoritative Blueprint docs: **render-blueprints** skill.\n\n| Mechanism | Role |\n|-----------|------|\n| `value` | Hardcoded string (non-secret config only) |\n| `generateValue: true` | Platform-generated secret |\n| `sync: false` | Dashboard prompt on **initial** create only |\n| `fromDatabase` | Inject DB fields (`connectionString`, `host`, `port`, `user`, `password`, `database`) |\n| `fromService` | Key Value: `type: keyvalue` + properties; private\u002Fweb: `host`, `hostport`, or `envVarKey` |\n| `fromGroup` | Link all vars from a named group |\n\n## Platform-Injected Variables\n\nRender sets **read-only** variables your app can read at runtime (and some at build). A concise list:\n\n| Variable | Typical meaning |\n|----------|-----------------|\n| `RENDER` | `\"true\"` when running on Render |\n| `RENDER_SERVICE_TYPE` | Service kind (e.g. web, worker) |\n| `RENDER_SERVICE_ID` | Service identifier |\n| `RENDER_SERVICE_NAME` | Human-readable service name |\n| `RENDER_INSTANCE_ID` | Current instance |\n| `RENDER_EXTERNAL_URL` | Public URL (when applicable) |\n| `RENDER_EXTERNAL_HOSTNAME` | Public hostname |\n| `RENDER_DISCOVERY_SERVICE` | Service discovery hostname (private network) |\n| `RENDER_GIT_COMMIT` | Deployed commit SHA |\n| `RENDER_GIT_BRANCH` | Branch for this deploy |\n| `PORT` | HTTP port to bind (**default `10000`**) |\n| `IS_PULL_REQUEST` | Preview deploy indicator |\n| `RENDER_CPU_COUNT` | vCPU count for the instance |\n| `RENDER_WEB_CONCURRENCY` | Suggested worker\u002Fprocess count hint |\n\nBuild vs runtime availability, language version env vars, and **WEB_CONCURRENCY** defaults: `references\u002Fplatform-variables.md`.\n\n## Runtime-Specific Defaults\n\nRender and buildpacks may set defaults (verify in your service’s **Environment** tab):\n\n| Runtime | Notable defaults |\n|---------|------------------|\n| **Node.js** | `NODE_ENV=production` |\n| **Python** | `PYTHON_VERSION` (pinned by build); Gunicorn-oriented images often set `GUNICORN_CMD_ARGS` to bind **`0.0.0.0:10000`** |\n| **Ruby** | `RAILS_ENV=production`, `RAILS_LOG_TO_STDOUT=true` |\n| **Go** | `GO111MODULE=on` (legacy modules flag; still seen on older stacks) |\n| **Rust** | `ROCKET_PORT=10000` (Rocket convention) |\n\nAlways bind HTTP servers to **`0.0.0.0`** and **`PORT`** (or the stack’s documented port env) unless using a static site or custom Docker entrypoint.\n\n## Common Issues\n\n1. **Everything is a string** — `DEBUG=false` is truthy in many parsers; use explicit comparison or typed config loaders.\n2. **`WEB_CONCURRENCY`** — Default behavior changed for services **created after December 8, 2025**. Compare with older services when debugging worker counts; see `references\u002Fplatform-variables.md`.\n3. **Undocumented `RENDER_*` variables** — Names and semantics may change; do not depend on undocumented injection for critical logic.\n4. **Blueprint vs Dashboard drift** — Editing only `render.yaml` does not retroactively apply `sync: false` prompts on update; merge strategy for env keys is easy to misunderstand—test in a scratch service.\n5. **Secret file paths** — Code must read **`\u002Fetc\u002Fsecrets\u002F\u003Cfilename>`**; wrong paths or missing mounts usually show as file-not-found at runtime.\n\n## References\n\n- `references\u002Fwiring-reference.md` — Complete Blueprint `envVar` wiring, YAML examples, precedence, edge cases\n- `references\u002Fplatform-variables.md` — Injected variables (build vs runtime), language versions, concurrency, reading vars from code\n\n## Related Skills\n\n- **render-blueprints** — Full Blueprint authoring, validation, multi-service layouts\n- **render-deploy** — First deploy, repo requirements, MCP vs YAML\n- **render-web-services** — Ports, health checks, scaling behavior tied to env-driven servers\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"author":25,"version":26,"category":27},"Render","1.0.0","configuration","Render Dashboard, CLI, or MCP tools","main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Frender-env-vars","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-env-vars",{"tool":42,"command":43},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill render-env-vars",{"tool":45,"command":46},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill render-env-vars","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Frender-env-vars\u002FSKILL.md",true,[50,56,60],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"agents\u002Fopenai.yaml","REFERENCE","参考文档",230,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Frender-env-vars\u002Fagents\u002Fopenai.yaml",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fplatform-variables.md",5014,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Frender-env-vars\u002Freferences\u002Fplatform-variables.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fwiring-reference.md",6628,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Frender-env-vars\u002Freferences\u002Fwiring-reference.md",[65,72,79,86,95,102],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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",[],[]]