[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77G2G7J2EP79X0C3RPDV6ND":3,"skill-same:01M77G2G7J2EP79X0C3RPDV6ND":45},{"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},"01M77G2G7J2EP79X0C3RPDV6ND","coalesce-transform-mcp-install",null,"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).","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-transform-mcp-install\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: coalesce-transform-mcp-install\ndescription: 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).\n---\n\u003C!-- coalesce-node-managed: true -->\n\n# Install the Coalesce Transform MCP\n\nScope: registering the hosted Coalesce Transform MCP server (HTTP transport)\nin an MCP client so agents can query Coalesce projects, environments, and\nruns. This is client configuration only — it does not touch the workspace\nrepo or the warehouse. For `coa` CLI credentials and `~\u002F.coa\u002Fconfig`, use\ncoalesce-cloud-api instead.\n\nSource of truth:\n[MCP quickstart](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fmcp-quickstart)\nand the per-client guides linked below. If this skill and the docs disagree,\nthe docs win.\n\n## What you need\n\n- **Endpoint** — `https:\u002F\u002F\u003Capp-host>\u002Fapi\u002Fv1\u002Fmcp`, where `\u003Capp-host>` is the\n  host the user signs into (e.g. `app.coalescesoftware.io`, or a custom\n  subdomain like `mycompany.app.eu.coalescesoftware.io`). Tenancy is\n  resolved from the token, but use the sign-in host so errors are obvious.\n- **Access token** — generated in the Coalesce App: **Deploy tab →\n  Generate Access Token**. This is a browser step; you cannot do it.\n  Ask the user to generate one and provide it (or export it as an env var —\n  preferred, see below). It is the same token `coa` and the REST API use,\n  so a user with a working `~\u002F.coa\u002Fconfig` already has one; with their\n  permission you may reuse the `token` value from that file rather than\n  asking them to generate another.\n\n## Token handling — read before running anything\n\n- NEVER echo, print, or repeat the token back in conversation or logs.\n- NEVER write a literal token into a file that is committed (`.mcp.json`\n  at repo root is usually committed — use env-var interpolation there).\n- Prefer an environment variable end to end: have the user\n  `export COALESCE_ACCESS_TOKEN=...` themselves, then reference\n  `$COALESCE_ACCESS_TOKEN` \u002F `${COALESCE_ACCESS_TOKEN}` in commands and\n  config so the secret never appears in shell history or the transcript.\n- Registering an MCP server stores the token in client config\n  (e.g. `~\u002F.claude.json`). That is expected, but say so, and ASK FIRST\n  before writing any config file.\n\n## Claude Code\n\nPreferred — user scope, token via env var (single quotes so the shell does\nnot expand it into history; Claude Code expands `${...}` at connect time):\n\n```sh\nclaude mcp add --transport http --scope user coalesce-transform \\\n  \"https:\u002F\u002F\u003Capp-host>\u002Fapi\u002Fv1\u002Fmcp\" \\\n  --header 'Authorization: Bearer ${COALESCE_ACCESS_TOKEN}'\n```\n\nOr project-shared: commit a `.mcp.json` at the repo root with env-var\ninterpolation, NEVER a literal token:\n\n```json\n{\n  \"mcpServers\": {\n    \"coalesce-transform\": {\n      \"type\": \"http\",\n      \"url\": \"https:\u002F\u002F\u003Capp-host>\u002Fapi\u002Fv1\u002Fmcp\",\n      \"headers\": {\n        \"Authorization\": \"Bearer ${COALESCE_ACCESS_TOKEN}\"\n      }\n    }\n  }\n}\n```\n\nA server added mid-session is NOT available until the session reconnects.\nTell the user to run `\u002Fmcp` (or restart the session) before verifying —\ndo not report failure just because the tools are not visible yet. And\n`${...}` is expanded from the environment Claude Code was LAUNCHED from:\nif the user exported the token after starting the session, `\u002Fmcp` alone\nwill not pick it up — they must restart `claude` from a shell that has\nthe variable set (e.g. after adding the export to their shell profile).\n\n## Other clients\n\nSame endpoint and header; follow the client guide for where config lives:\n\n- [Claude Desktop \u002F Claude Code](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fintegrate-mcp-claude)\n  — Desktop: Settings → Developer → Edit Config, add the `mcpServers`\n  entry, then fully quit and reopen.\n- [Cursor](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fintegrate-mcp-cursor)\n- [VS Code](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fintegrate-mcp-vscode)\n- [Snowflake Cortex Code](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fintegrate-mcp-cortex)\n\n## Verify\n\nAfter reconnect\u002Frestart, ask: \"List Coalesce projects in this\norganization.\" Success returns the org's Projects. On an auth error,\nre-check the token (regenerate if in doubt) and confirm the URL host\nmatches where the user signs in. Available tools:\n[MCP tool reference](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fmcp-available-tools).\n\n## Approval gates\n\n- Without asking: reading docs, composing the command\u002Fconfig for review,\n  and the post-install verification query (read-only cloud call).\n- ASK FIRST: writing or editing any client config (`claude mcp add`,\n  `.mcp.json`, `claude_desktop_config.json`, …), reading a token out of\n  `~\u002F.coa\u002Fconfig`, and committing `.mcp.json` to the repo.\n- NEVER: generate\u002Fscrape tokens from the browser yourself, place a literal\n  token in a committed file, or paste a token into chat output.\n","\u003C!-- coalesce-node-managed: true -->\n\n# Install the Coalesce Transform MCP\n\nScope: registering the hosted Coalesce Transform MCP server (HTTP transport)\nin an MCP client so agents can query Coalesce projects, environments, and\nruns. This is client configuration only — it does not touch the workspace\nrepo or the warehouse. For `coa` CLI credentials and `~\u002F.coa\u002Fconfig`, use\ncoalesce-cloud-api instead.\n\nSource of truth:\n[MCP quickstart](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fmcp-quickstart)\nand the per-client guides linked below. If this skill and the docs disagree,\nthe docs win.\n\n## What you need\n\n- **Endpoint** — `https:\u002F\u002F\u003Capp-host>\u002Fapi\u002Fv1\u002Fmcp`, where `\u003Capp-host>` is the\n  host the user signs into (e.g. `app.coalescesoftware.io`, or a custom\n  subdomain like `mycompany.app.eu.coalescesoftware.io`). Tenancy is\n  resolved from the token, but use the sign-in host so errors are obvious.\n- **Access token** — generated in the Coalesce App: **Deploy tab →\n  Generate Access Token**. This is a browser step; you cannot do it.\n  Ask the user to generate one and provide it (or export it as an env var —\n  preferred, see below). It is the same token `coa` and the REST API use,\n  so a user with a working `~\u002F.coa\u002Fconfig` already has one; with their\n  permission you may reuse the `token` value from that file rather than\n  asking them to generate another.\n\n## Token handling — read before running anything\n\n- NEVER echo, print, or repeat the token back in conversation or logs.\n- NEVER write a literal token into a file that is committed (`.mcp.json`\n  at repo root is usually committed — use env-var interpolation there).\n- Prefer an environment variable end to end: have the user\n  `export COALESCE_ACCESS_TOKEN=...` themselves, then reference\n  `$COALESCE_ACCESS_TOKEN` \u002F `${COALESCE_ACCESS_TOKEN}` in commands and\n  config so the secret never appears in shell history or the transcript.\n- Registering an MCP server stores the token in client config\n  (e.g. `~\u002F.claude.json`). That is expected, but say so, and ASK FIRST\n  before writing any config file.\n\n## Claude Code\n\nPreferred — user scope, token via env var (single quotes so the shell does\nnot expand it into history; Claude Code expands `${...}` at connect time):\n\n```sh\nclaude mcp add --transport http --scope user coalesce-transform \\\n  \"https:\u002F\u002F\u003Capp-host>\u002Fapi\u002Fv1\u002Fmcp\" \\\n  --header 'Authorization: Bearer ${COALESCE_ACCESS_TOKEN}'\n```\n\nOr project-shared: commit a `.mcp.json` at the repo root with env-var\ninterpolation, NEVER a literal token:\n\n```json\n{\n  \"mcpServers\": {\n    \"coalesce-transform\": {\n      \"type\": \"http\",\n      \"url\": \"https:\u002F\u002F\u003Capp-host>\u002Fapi\u002Fv1\u002Fmcp\",\n      \"headers\": {\n        \"Authorization\": \"Bearer ${COALESCE_ACCESS_TOKEN}\"\n      }\n    }\n  }\n}\n```\n\nA server added mid-session is NOT available until the session reconnects.\nTell the user to run `\u002Fmcp` (or restart the session) before verifying —\ndo not report failure just because the tools are not visible yet. And\n`${...}` is expanded from the environment Claude Code was LAUNCHED from:\nif the user exported the token after starting the session, `\u002Fmcp` alone\nwill not pick it up — they must restart `claude` from a shell that has\nthe variable set (e.g. after adding the export to their shell profile).\n\n## Other clients\n\nSame endpoint and header; follow the client guide for where config lives:\n\n- [Claude Desktop \u002F Claude Code](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fintegrate-mcp-claude)\n  — Desktop: Settings → Developer → Edit Config, add the `mcpServers`\n  entry, then fully quit and reopen.\n- [Cursor](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fintegrate-mcp-cursor)\n- [VS Code](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fintegrate-mcp-vscode)\n- [Snowflake Cortex Code](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fintegrate-mcp-cortex)\n\n## Verify\n\nAfter reconnect\u002Frestart, ask: \"List Coalesce projects in this\norganization.\" Success returns the org's Projects. On an auth error,\nre-check the token (regenerate if in doubt) and confirm the URL host\nmatches where the user signs in. Available tools:\n[MCP tool reference](https:\u002F\u002Fdocs.coalesce.io\u002Fdocs\u002Fcoalesce-ai\u002Fmcp\u002Fmcp-available-tools).\n\n## Approval gates\n\n- Without asking: reading docs, composing the command\u002Fconfig for review,\n  and the post-install verification query (read-only cloud call).\n- ASK FIRST: writing or editing any client config (`claude mcp add`,\n  `.mcp.json`, `claude_desktop_config.json`, …), reading a token out of\n  `~\u002F.coa\u002Fconfig`, and committing `.mcp.json` to the repo.\n- NEVER: generate\u002Fscrape tokens from the browser yourself, place a literal\n  token in a committed file, or paste a token into chat output.\n",{"name":5,"description":7},"develop","0380f6339f1c9c60a1129692e86be71db7c8bb89","skills\u002Fcoalesce-transform-mcp-install","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-transform-mcp-install",{"tool":37,"command":38},"bunx","bunx skills add Coalesce-Software-Inc\u002Fcoalesce-platform-skills --skill coalesce-transform-mcp-install",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Coalesce-Software-Inc\u002Fcoalesce-platform-skills --skill coalesce-transform-mcp-install","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-transform-mcp-install\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"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":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},"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":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},"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":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},"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":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},"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",[],[],{"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},"01M77G1TQGX567YQYQY734T361","coalesce-pipeline-structure","Use when creating, deleting, renaming, or rewiring Coalesce nodes, subgraphs, or jobs — changing the structural topology of the transformation DAG. Not for editing SQL inside an existing node (use coalesce-sql-transformation).","https:\u002F\u002Fgithub.com\u002FCoalesce-Software-Inc\u002Fcoalesce-platform-skills\u002Fblob\u002Fdevelop\u002Fskills\u002Fcoalesce-pipeline-structure\u002FSKILL.md",[],[]]