[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77G11NS6FSMVRPYH5115NHR":3,"skill-same:01M77G11NS6FSMVRPYH5115NHR":51},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M77G11NS6FSMVRPYH5115NHR","coalesce-create-app",null,"Use when building, changing, or debugging a Coalesce workspace app — a small local web app in a Transform workspace's apps\u002F\u003Cid>\u002F folder that Coalesce Desktop or coa serve runs and opens as a tab from the Build rail's Apps menu (dashboards, modelers, generators, review tools over the workspace's nodes and YAML). Covers the runtime contract (node \u003Cfile> start script, PORT and WORKSPACE_DIR, no npm), the sandboxed \u003Capp>.localhost origin, reading and writing workspace files safely, running coa from an app, and testing.","Coalesce-Software-Inc\u002Fcoalesce-platform-skills","Coalesce-Software-Inc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F91339100?v=4","01M77G0R46A1FMHGV0DGAD04DG","Coalesce.io","01M77G0R4VFVRVQ4ZYKPE8CABW",0,"MIT","https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-create-app\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: coalesce-create-app\ndescription: Use when building, changing, or debugging a Coalesce workspace app — a small local web app in a Transform workspace's apps\u002F\u003Cid>\u002F folder that Coalesce Desktop or coa serve runs and opens as a tab from the Build rail's Apps menu (dashboards, modelers, generators, review tools over the workspace's nodes and YAML). Covers the runtime contract (node \u003Cfile> start script, PORT and WORKSPACE_DIR, no npm), the sandboxed \u003Capp>.localhost origin, reading and writing workspace files safely, running coa from an app, and testing.\n---\n\u003C!-- coalesce-node-managed: true -->\n\n# Create a Coalesce workspace app\n\nA **workspace app** is a folder `apps\u002F\u003CappId>\u002F` inside a Transform workspace\n(the folder with `data.yml`) containing a `package.json` and a Node server.\nWhen the workspace is open in Coalesce Desktop or `coa serve`, the watch server\nlists every such folder under **Apps** on the Build rail. Opening one starts\nits server on demand and shows it in a canvas tab, in an iframe served from the\napp's own origin. The app reads and writes the workspace on disk, so whatever\nit saves shows up in Coalesce and in git like any other edit.\n\nApps run only in local mode (Desktop or `coa serve`), never in the cloud\nCoalesce app.\n\nIf the app reads or writes Coalesce files (`nodes\u002F`, `jobs\u002F`, `nodeTypes\u002F`,\n`locations.yml`), also load `coalesce-pipelines` for the file formats and\nauthoring rules.\n\n## The runtime contract\n\nThese rules come from the watch server's app manager. Break one and the app\nfails to start or never appears.\n\n| Rule | Detail |\n|---|---|\n| **Discovery** | Every non-hidden folder in `apps\u002F` with a parseable `package.json` is an app. The folder name is the **app id**. Folders starting with `.` are ignored. |\n| **Menu label** | `name` from `package.json`, else the folder name. `description` is shown too. |\n| **Start script** | `scripts.start` must be exactly `node \u003Cfile> [args]`. It is not run by npm or a shell, so no `npm`, `npx`, `vite`, `&&`, pipes, quotes, `$VARS`, globs, or `~`. Anything else fails with \"Unsupported start script\". |\n| **No install step** | Nothing runs `npm install`, and `node_modules\u002F` is not consulted for you. Use Node built-ins, or bundle dependencies into one committed file (see [Dependencies](#dependencies)). |\n| **Runtime** | Coalesce's own Node: Electron's Node (v24 at the time of writing) in Desktop, or whatever Node runs `coa` under `coa serve`. Write for Node 20+ and use only built-ins (`http`, `fs`, `path`, `child_process`, `crypto`, global `fetch`). No native `.node` addons. |\n| **Environment** | Always read `PORT` (the port to listen on) and `WORKSPACE_DIR` (absolute workspace root). Don't hardcode a port or work out the workspace from the app's own path. The rest of the parent environment is inherited; in Desktop `PATH` can be the bare system one (`\u002Fusr\u002Fbin:\u002Fbin:...`). Working directory is the app folder. |\n| **Readiness** | Coalesce polls `GET http:\u002F\u002Flocalhost:$PORT\u002F` every 0.5 s for 15 s; any HTTP response counts. Listen at once and do slow work (scans, warehouse calls) after listening or per request. |\n| **Lifetime** | Started on first open, kept running across tab switches, stopped when Coalesce or `coa serve` exits. A crashed app restarts on its next request. Editing `server.js` does not restart a running app (see [Test it](#step-4--test-it)). |\n| **Logs** | stdout and stderr go to the Coalesce log as `[App:\u003CappId>]`. If the app exits before it is ready, the tail of stderr is shown in the tab. |\n| **Host name** | Served at `http:\u002F\u002F\u003Clabel>.localhost:\u003Cwatch port>\u002F`, where `\u003Clabel>` is the app id lowercased with every run of other characters turned into `-`. Two folders whose ids map to the same label collide and neither opens. Use a lowercase `[a-z0-9-]` id and make `name` the same. |\n\n### The sandbox the UI runs in\n\nThe tab is an iframe with `sandbox=\"allow-scripts allow-same-origin\nallow-forms allow-popups\"` on the app's own origin. In practice:\n\n- **No access to Coalesce.** `window.parent` is cross-origin: the app cannot\n  read Coalesce's DOM, theme, storage, auth, selection, or the watch API from\n  the browser.\n- **Blocked:** `alert`, `confirm`, `prompt` (no `allow-modals`; they return\n  immediately without showing), file downloads (no `allow-downloads`; save\n  output into the workspace instead), and navigating the top window.\n- **Allowed:** scripts, forms, `fetch` to the app's own server, its own\n  `localStorage`, and `window.open` \u002F `target=\"_blank\"` links.\n- **Theme:** follow `prefers-color-scheme`. The app cannot read Coalesce's\n  light\u002Fdark setting.\n- **Paths:** the app is served at `\u002F` of its own origin. Root-relative\n  (`\u002Fapi\u002F...`) and relative URLs both work; no `\u003Cbase>` tricks or `\u002Fproxy`\n  prefixes are needed (those were for the old path-prefixed proxy).\n- Coalesce refuses requests to `\u003Clabel>.localhost` from other websites, but\n  the app also listens directly on `localhost:$PORT`, and that port has no\n  guard. See the next section.\n\n### Guard the app's own port\n\nThe app's port (`localhost:$PORT`) is reachable from any page in the user's\nbrowser, not just from Coalesce. The template includes three checks so only\nthe app's own page can use it; keep them:\n\n1. **`Host` is a loopback name** (`localhost`, `127.0.0.1`, `[::1]`, or\n   `*.localhost`), which rules out DNS rebinding. Requests through Coalesce\n   keep their `\u003Clabel>.localhost` host, so they pass.\n2. **Writes are same-origin JSON.** Anything other than `GET`\u002F`HEAD` needs\n   `Content-Type: application\u002Fjson` and a `Sec-Fetch-Site` of `same-origin` or\n   none (`curl` sends none). Have the UI set the content type on writes, and\n   don't change state on a `GET`.\n3. **No CORS headers.**\n\nThese checks cover browser pages. Other programs on the machine aren't in\nscope, since they can already read the workspace directly.\n\n### Render workspace content as text\n\nNode names, descriptions and SQL come from git, and the app's own page is\ntrusted to write. Put workspace values on the page with `textContent` (or a\nframework's default escaping) rather than `innerHTML` or HTML built from a\ntemplate string, as the template's table does. Don't `eval` or `require`\nworkspace files.\n\n### Run commands without a shell\n\nUse `execFile` or `spawn` with an argument array, as the\n[coa snippet](#running-coa-from-an-app) does, rather than `exec` or\n`shell: true`. Check values that become arguments (node names, locations,\nselectors) against a simple pattern such as `^[A-Za-z0-9_]+$`, and return a\n400 otherwise.\n\n### Keep secrets on the server\n\n- Anything an app writes to the workspace ends up in git, so read API keys\n  from a file outside it (such as `~\u002F.config\u002F\u003CappId>\u002F`) or an environment\n  variable. Desktop opened from the Dock or Finder doesn't see shell profile\n  variables, so a file is more reliable there.\n- Keep keys out of responses, pages and logs, and don't read `~\u002F.coa\u002Fconfig`.\n- If the app sends workspace content to an outside service, say which\n  service and what is sent in its README and UI, and send it only when the\n  user asks. Check with the user before building one.\n\n## Step 0 — Orient\n\n1. `ls apps\u002F` for existing apps and id collisions. Apps run with the user's\n   permissions when opened, so read any app you didn't write before starting it.\n2. If `~\u002F.coalesce\u002Fdesktop\u002Fagent.json` exists, `serving.port` is the port apps\n   are served on. Otherwise use the port `coa serve` printed.\n3. Decide where the app writes:\n   - `nodes\u002F`, `jobs\u002F` and `subgraphs\u002F` follow `coalesce-pipelines` and need\n     the user's OK.\n   - Never `data.yml`, `workspace.yml`, `environments\u002F`, `.coa\u002F` or\n     `~\u002F.coa\u002Fconfig`.\n\n## Step 1 — Scaffold\n\nWrite the three files in [reference\u002Ftemplate.md](reference\u002Ftemplate.md) into\n`apps\u002F\u003CappId>\u002F` verbatim, and set `name` (same as the folder) and\n`description` in `package.json`. The template already handles loopback\nlistening, the port checks and workspace path checks (`wsPath()`).\n\n## Step 2 — Build the server\n\n- Answer `GET \u002F` fast; it's the readiness probe.\n- Read workspace files per request so the app sees edits made in Coalesce.\n  `coalesce-pipelines` documents the node and node type file shapes.\n- Return JSON errors with a 4xx status, and log to stdout\u002Fstderr.\n\n### Running coa from an app\n\n`coa` usually isn't on `PATH` in Desktop. Resolve it from `agent.json`:\n\n```js\nconst { execFile } = require(\"child_process\");\nconst os = require(\"os\"), fs = require(\"fs\"), path = require(\"path\");\n\nfunction coaCommand() {\n  try {\n    const a = JSON.parse(fs.readFileSync(path.join(os.homedir(), \".coalesce\u002Fdesktop\u002Fagent.json\"), \"utf-8\"));\n    const [cmd, ...pre] = a.coa.runInvocation;\n    return { cmd, pre, env: { ...process.env, ...a.coa.env } };\n  } catch {\n    return { cmd: \"coa\", pre: [], env: process.env };\n  }\n}\n\nfunction runCoa(args) {\n  const { cmd, pre, env } = coaCommand();\n  return new Promise((resolve) =>\n    execFile(cmd, [...pre, ...args, \"-d\", process.env.WORKSPACE_DIR], { env, maxBuffer: 20 \u003C\u003C 20 }, (err, stdout, stderr) =>\n      resolve({ ok: !err, stdout, stderr })));\n}\n\u002F\u002F e.g. await runCoa([\"--json\", \"validate\"]); stdout holds the JSON even when ok is false\n```\n\nStick to read-only commands (`validate`, `describe`, `--dry-run`).\n\n## Step 3 — Build the UI\n\n- Plain HTML\u002FJS is usually enough. A framework build must be committed as\n  static files; nothing builds inside Coalesce.\n- `fetch(\"\u002Fapi\u002F...\")` with `content-type: application\u002Fjson` on writes, and\n  workspace values rendered with `textContent`.\n- Show errors inline (no dialogs), follow `prefers-color-scheme`, and fill\n  the tab's height.\n\n## Dependencies\n\nPrefer none. Otherwise bundle into one committed file and start that:\n\n```sh\nnpx esbuild server.src.js --bundle --platform=node --target=node20 --outfile=dist\u002Fserver.js\n```\n\n## Step 4 — Test it\n\n1. Standalone: `PORT=4310 WORKSPACE_DIR=\"$WORKSPACE\" node server.js`, then\n   `curl localhost:4310\u002F` and open it in a browser.\n2. Check `scripts.start` is `node \u003Cfile>`, `node --check` passes, and `name`\n   matches the folder.\n3. In Coalesce: Build › Apps › your app (reload the page to see a new app).\n   Restart Coalesce or `coa serve` after server changes; UI changes only need\n   a tab reload. Start failures are shown in the tab.\n\n## Step 5 — Commit\n\nStage the app folder per `coalesce-git-publication`.\nCommit and push only with the user's approval.\n\n## Approval gates\n\n- Without asking: reading the workspace, scaffolding the requested app,\n  running it standalone, read-only `coa` commands.\n- ASK FIRST: apps that write `nodes\u002F`, `jobs\u002F`, `subgraphs\u002F` or other shared\n  config, or send workspace content to an outside service; changing another\n  app; adding dependencies; committing; pushing.\n- NEVER: have an app run deploy, refresh, init or profile commands, read\n  `~\u002F.coa\u002Fconfig`, listen beyond loopback, or reach into the Coalesce page.\n","\u003C!-- coalesce-node-managed: true -->\n\n# Create a Coalesce workspace app\n\nA **workspace app** is a folder `apps\u002F\u003CappId>\u002F` inside a Transform workspace\n(the folder with `data.yml`) containing a `package.json` and a Node server.\nWhen the workspace is open in Coalesce Desktop or `coa serve`, the watch server\nlists every such folder under **Apps** on the Build rail. Opening one starts\nits server on demand and shows it in a canvas tab, in an iframe served from the\napp's own origin. The app reads and writes the workspace on disk, so whatever\nit saves shows up in Coalesce and in git like any other edit.\n\nApps run only in local mode (Desktop or `coa serve`), never in the cloud\nCoalesce app.\n\nIf the app reads or writes Coalesce files (`nodes\u002F`, `jobs\u002F`, `nodeTypes\u002F`,\n`locations.yml`), also load `coalesce-pipelines` for the file formats and\nauthoring rules.\n\n## The runtime contract\n\nThese rules come from the watch server's app manager. Break one and the app\nfails to start or never appears.\n\n| Rule | Detail |\n|---|---|\n| **Discovery** | Every non-hidden folder in `apps\u002F` with a parseable `package.json` is an app. The folder name is the **app id**. Folders starting with `.` are ignored. |\n| **Menu label** | `name` from `package.json`, else the folder name. `description` is shown too. |\n| **Start script** | `scripts.start` must be exactly `node \u003Cfile> [args]`. It is not run by npm or a shell, so no `npm`, `npx`, `vite`, `&&`, pipes, quotes, `$VARS`, globs, or `~`. Anything else fails with \"Unsupported start script\". |\n| **No install step** | Nothing runs `npm install`, and `node_modules\u002F` is not consulted for you. Use Node built-ins, or bundle dependencies into one committed file (see [Dependencies](#dependencies)). |\n| **Runtime** | Coalesce's own Node: Electron's Node (v24 at the time of writing) in Desktop, or whatever Node runs `coa` under `coa serve`. Write for Node 20+ and use only built-ins (`http`, `fs`, `path`, `child_process`, `crypto`, global `fetch`). No native `.node` addons. |\n| **Environment** | Always read `PORT` (the port to listen on) and `WORKSPACE_DIR` (absolute workspace root). Don't hardcode a port or work out the workspace from the app's own path. The rest of the parent environment is inherited; in Desktop `PATH` can be the bare system one (`\u002Fusr\u002Fbin:\u002Fbin:...`). Working directory is the app folder. |\n| **Readiness** | Coalesce polls `GET http:\u002F\u002Flocalhost:$PORT\u002F` every 0.5 s for 15 s; any HTTP response counts. Listen at once and do slow work (scans, warehouse calls) after listening or per request. |\n| **Lifetime** | Started on first open, kept running across tab switches, stopped when Coalesce or `coa serve` exits. A crashed app restarts on its next request. Editing `server.js` does not restart a running app (see [Test it](#step-4--test-it)). |\n| **Logs** | stdout and stderr go to the Coalesce log as `[App:\u003CappId>]`. If the app exits before it is ready, the tail of stderr is shown in the tab. |\n| **Host name** | Served at `http:\u002F\u002F\u003Clabel>.localhost:\u003Cwatch port>\u002F`, where `\u003Clabel>` is the app id lowercased with every run of other characters turned into `-`. Two folders whose ids map to the same label collide and neither opens. Use a lowercase `[a-z0-9-]` id and make `name` the same. |\n\n### The sandbox the UI runs in\n\nThe tab is an iframe with `sandbox=\"allow-scripts allow-same-origin\nallow-forms allow-popups\"` on the app's own origin. In practice:\n\n- **No access to Coalesce.** `window.parent` is cross-origin: the app cannot\n  read Coalesce's DOM, theme, storage, auth, selection, or the watch API from\n  the browser.\n- **Blocked:** `alert`, `confirm`, `prompt` (no `allow-modals`; they return\n  immediately without showing), file downloads (no `allow-downloads`; save\n  output into the workspace instead), and navigating the top window.\n- **Allowed:** scripts, forms, `fetch` to the app's own server, its own\n  `localStorage`, and `window.open` \u002F `target=\"_blank\"` links.\n- **Theme:** follow `prefers-color-scheme`. The app cannot read Coalesce's\n  light\u002Fdark setting.\n- **Paths:** the app is served at `\u002F` of its own origin. Root-relative\n  (`\u002Fapi\u002F...`) and relative URLs both work; no `\u003Cbase>` tricks or `\u002Fproxy`\n  prefixes are needed (those were for the old path-prefixed proxy).\n- Coalesce refuses requests to `\u003Clabel>.localhost` from other websites, but\n  the app also listens directly on `localhost:$PORT`, and that port has no\n  guard. See the next section.\n\n### Guard the app's own port\n\nThe app's port (`localhost:$PORT`) is reachable from any page in the user's\nbrowser, not just from Coalesce. The template includes three checks so only\nthe app's own page can use it; keep them:\n\n1. **`Host` is a loopback name** (`localhost`, `127.0.0.1`, `[::1]`, or\n   `*.localhost`), which rules out DNS rebinding. Requests through Coalesce\n   keep their `\u003Clabel>.localhost` host, so they pass.\n2. **Writes are same-origin JSON.** Anything other than `GET`\u002F`HEAD` needs\n   `Content-Type: application\u002Fjson` and a `Sec-Fetch-Site` of `same-origin` or\n   none (`curl` sends none). Have the UI set the content type on writes, and\n   don't change state on a `GET`.\n3. **No CORS headers.**\n\nThese checks cover browser pages. Other programs on the machine aren't in\nscope, since they can already read the workspace directly.\n\n### Render workspace content as text\n\nNode names, descriptions and SQL come from git, and the app's own page is\ntrusted to write. Put workspace values on the page with `textContent` (or a\nframework's default escaping) rather than `innerHTML` or HTML built from a\ntemplate string, as the template's table does. Don't `eval` or `require`\nworkspace files.\n\n### Run commands without a shell\n\nUse `execFile` or `spawn` with an argument array, as the\n[coa snippet](#running-coa-from-an-app) does, rather than `exec` or\n`shell: true`. Check values that become arguments (node names, locations,\nselectors) against a simple pattern such as `^[A-Za-z0-9_]+$`, and return a\n400 otherwise.\n\n### Keep secrets on the server\n\n- Anything an app writes to the workspace ends up in git, so read API keys\n  from a file outside it (such as `~\u002F.config\u002F\u003CappId>\u002F`) or an environment\n  variable. Desktop opened from the Dock or Finder doesn't see shell profile\n  variables, so a file is more reliable there.\n- Keep keys out of responses, pages and logs, and don't read `~\u002F.coa\u002Fconfig`.\n- If the app sends workspace content to an outside service, say which\n  service and what is sent in its README and UI, and send it only when the\n  user asks. Check with the user before building one.\n\n## Step 0 — Orient\n\n1. `ls apps\u002F` for existing apps and id collisions. Apps run with the user's\n   permissions when opened, so read any app you didn't write before starting it.\n2. If `~\u002F.coalesce\u002Fdesktop\u002Fagent.json` exists, `serving.port` is the port apps\n   are served on. Otherwise use the port `coa serve` printed.\n3. Decide where the app writes:\n   - `nodes\u002F`, `jobs\u002F` and `subgraphs\u002F` follow `coalesce-pipelines` and need\n     the user's OK.\n   - Never `data.yml`, `workspace.yml`, `environments\u002F`, `.coa\u002F` or\n     `~\u002F.coa\u002Fconfig`.\n\n## Step 1 — Scaffold\n\nWrite the three files in [reference\u002Ftemplate.md](reference\u002Ftemplate.md) into\n`apps\u002F\u003CappId>\u002F` verbatim, and set `name` (same as the folder) and\n`description` in `package.json`. The template already handles loopback\nlistening, the port checks and workspace path checks (`wsPath()`).\n\n## Step 2 — Build the server\n\n- Answer `GET \u002F` fast; it's the readiness probe.\n- Read workspace files per request so the app sees edits made in Coalesce.\n  `coalesce-pipelines` documents the node and node type file shapes.\n- Return JSON errors with a 4xx status, and log to stdout\u002Fstderr.\n\n### Running coa from an app\n\n`coa` usually isn't on `PATH` in Desktop. Resolve it from `agent.json`:\n\n```js\nconst { execFile } = require(\"child_process\");\nconst os = require(\"os\"), fs = require(\"fs\"), path = require(\"path\");\n\nfunction coaCommand() {\n  try {\n    const a = JSON.parse(fs.readFileSync(path.join(os.homedir(), \".coalesce\u002Fdesktop\u002Fagent.json\"), \"utf-8\"));\n    const [cmd, ...pre] = a.coa.runInvocation;\n    return { cmd, pre, env: { ...process.env, ...a.coa.env } };\n  } catch {\n    return { cmd: \"coa\", pre: [], env: process.env };\n  }\n}\n\nfunction runCoa(args) {\n  const { cmd, pre, env } = coaCommand();\n  return new Promise((resolve) =>\n    execFile(cmd, [...pre, ...args, \"-d\", process.env.WORKSPACE_DIR], { env, maxBuffer: 20 \u003C\u003C 20 }, (err, stdout, stderr) =>\n      resolve({ ok: !err, stdout, stderr })));\n}\n\u002F\u002F e.g. await runCoa([\"--json\", \"validate\"]); stdout holds the JSON even when ok is false\n```\n\nStick to read-only commands (`validate`, `describe`, `--dry-run`).\n\n## Step 3 — Build the UI\n\n- Plain HTML\u002FJS is usually enough. A framework build must be committed as\n  static files; nothing builds inside Coalesce.\n- `fetch(\"\u002Fapi\u002F...\")` with `content-type: application\u002Fjson` on writes, and\n  workspace values rendered with `textContent`.\n- Show errors inline (no dialogs), follow `prefers-color-scheme`, and fill\n  the tab's height.\n\n## Dependencies\n\nPrefer none. Otherwise bundle into one committed file and start that:\n\n```sh\nnpx esbuild server.src.js --bundle --platform=node --target=node20 --outfile=dist\u002Fserver.js\n```\n\n## Step 4 — Test it\n\n1. Standalone: `PORT=4310 WORKSPACE_DIR=\"$WORKSPACE\" node server.js`, then\n   `curl localhost:4310\u002F` and open it in a browser.\n2. Check `scripts.start` is `node \u003Cfile>`, `node --check` passes, and `name`\n   matches the folder.\n3. In Coalesce: Build › Apps › your app (reload the page to see a new app).\n   Restart Coalesce or `coa serve` after server changes; UI changes only need\n   a tab reload. Start failures are shown in the tab.\n\n## Step 5 — Commit\n\nStage the app folder per `coalesce-git-publication`.\nCommit and push only with the user's approval.\n\n## Approval gates\n\n- Without asking: reading the workspace, scaffolding the requested app,\n  running it standalone, read-only `coa` commands.\n- ASK FIRST: apps that write `nodes\u002F`, `jobs\u002F`, `subgraphs\u002F` or other shared\n  config, or send workspace content to an outside service; changing another\n  app; adding dependencies; committing; pushing.\n- NEVER: have an app run deploy, refresh, init or profile commands, read\n  `~\u002F.coa\u002Fconfig`, listen beyond loopback, or reach into the Coalesce page.\n",{"name":5,"description":7},"develop","0380f6339f1c9c60a1129692e86be71db7c8bb89","skills\u002Fcoalesce-create-app","https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills","https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc","coalesce.io","2026-11-11 05:53:06",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Coalesce-Software-Inc\u002Fcoalesce-platform-skills --skill coalesce-create-app",{"tool":37,"command":38},"bunx","bunx skills add Coalesce-Software-Inc\u002Fcoalesce-platform-skills --skill coalesce-create-app",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Coalesce-Software-Inc\u002Fcoalesce-platform-skills --skill coalesce-create-app","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-create-app\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"reference\u002Ftemplate.md","REFERENCE","参考文档",7814,"https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-create-app\u002Freference\u002Ftemplate.md",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M77G2G7J2EP79X0C3RPDV6ND","coalesce-transform-mcp-install","Use when installing, connecting, or troubleshooting the hosted Coalesce Transform MCP server in an MCP client (Claude Code, Claude Desktop, Cursor, VS Code, Cortex Code) — endpoint URL, access token handling, registration, and verification. Not for coa CLI auth (use coalesce-cloud-api).","https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-transform-mcp-install\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M77G2CPHB84J4S949VJ4DXB4","coalesce-sql-transformation","Use when editing the SQL inside existing Coalesce V2 node files (.sql) — changing column expressions, joins, filters, CTEs, inline column annotations, or ref() macros. Not for creating\u002Fdeleting node files (use coalesce-pipeline-structure).","https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-sql-transformation\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M77G29YB2RF8F7KYB3Y6T4ZS","coalesce-review-risk","Use when reviewing Coalesce pipeline changes for correctness, impact, and risk before approval — READ-ONLY analysis of diffs, coa validate\u002Fdry-run evidence, and downstream blast radius. Never edits files or runs warehouse-mutating commands.","https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-review-risk\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M77G27472MK0Q5HEXTTAF9RG","coalesce-rename-node-cascade","Rename a Coalesce node and cascade the new name through every downstream ref(), job selector, and subgraph selector, with quote-agnostic matching and validation.","https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-rename-node-cascade\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M77G2318E8JZ2FM523VSJEB2","coalesce-quality-test-authoring","Decide which data quality tests a table, view or model needs, and write them in whatever test format the project already uses (dbt, SYNQ YAML, SQLMesh audits, Soda, Great Expectations, custom SQL, and so on). Use it when asked to add, suggest, review or extend data tests for a warehouse asset, or when a change to a model should come with tests.","https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-quality-test-authoring\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M77G1YM5TCKSHQA6QZRERXF2","coalesce-pipelines","Use when working in a Coalesce Transform repository (data.yml + nodes\u002F with \u003CLOCATION>-\u003CNAME>.sql\u002F.yml files) — building, editing, validating, or running data transformation pipelines with the coa CLI, including editing V1 .yml nodes and shared config (data.yml, locations, environments, jobs, node types). Start here; it routes to the more specific coalesce-* skills.","https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-pipelines\u002FSKILL.md",[],[]]