[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMD3V0C910EZP1VQCDRVXS":3,"skill-same:01M7EMD3V0C910EZP1VQCDRVXS":56},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M7EMD3V0C910EZP1VQCDRVXS","curviate-quickstart",null,"The first run: install the Curviate CLI, authenticate this machine with `curviate setup`, confirm with `curviate doctor`, connect a LinkedIn account, and prove the whole path works by reading the same profile live and then from the store. Use when Curviate is being set up for the first time, when `curviate` is not installed or not authenticated, when a command fails with a credential or account error, or when someone asks how to get started. Reads only: it issues no write of any kind.","marnixGeerkens\u002Frocketlauncher-claude-code","marnixGeerkens","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F143275741?v=4","01M7EJY825SFPHDDZNFDAJHCA9","Marnix Geerkens","01M7EJY82TBA6ABXJ62JWR9B9F",0,"MIT","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fcurviate\u002Fcurviate-quickstart\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: curviate-quickstart\ndescription: \"The first run: install the Curviate CLI, authenticate this machine with `curviate setup`, confirm with `curviate doctor`, connect a LinkedIn account, and prove the whole path works by reading the same profile live and then from the store. Use when Curviate is being set up for the first time, when `curviate` is not installed or not authenticated, when a command fails with a credential or account error, or when someone asks how to get started. Reads only: it issues no write of any kind.\"\nversion: 0.1.0\nauthor: Curviate\nlicense: MIT\ntags: [LinkedIn, CLI, Agents, Sales, Recruiting, Outreach]\nrepository: https:\u002F\u002Fgithub.com\u002FCurviate\u002Fcurviate-plugin\n---\n\n# Curviate: the first run\n\nFour steps, in this order: install, authenticate, connect an account, prove it. Every command here\nis a read. Nothing in this skill posts, messages, invites, follows or endorses anyone.\n\nEstablished against CLI `0.33.0`.\n\n## 1. Install the CLI\n\n```bash\nnpm install -g @curviate\u002Fcli\ncurviate --version    # needs Node 18 or newer\n```\n\n## 2. Authenticate this machine: `curviate setup`\n\n`setup` opens the dashboard, takes the short code it shows you, and saves an API key into a local\nprofile. **The key is never printed and never passed on a command line.**\n\nThe command has two shapes, and which one you get is decided by whether **stdout** is a terminal.\n\n### Agent shape: two legs, because a browser has to happen in between\n\nWhen stdout is not a terminal, or when `--json` is passed, `setup` prints a JSON object and exits\n`0`. It does not prompt and it does not open a browser:\n\n```bash\ncurviate setup --json\n# {\"authorize_url\":\"…\",\"next_step\":\"curviate setup --code -\",\"instructions\":\"…\"}\n```\n\nOpen `authorize_url` in a browser signed in to the workspace, press Authorize, and read back the\ncode it displays. Then hand that code to the second leg **on stdin**:\n\n```bash\nprintf '%s' \"$CODE\" | curviate setup --code -\n# {\"ok\":true,\"tenant\":\"…\",\"profile\":\"default\",\"account_id\":\"…\"}\n```\n\n- **`--code -` reads from stdin deliberately.** Passing the code as a flag value works but warns:\n  a value on the command line is visible to other processes through `ps` and is saved in shell\n  history.\n- **The two legs must run on the same machine, under the same configuration directory.** Leg one\n  writes a short-lived resume file beside the config file, readable only by you, holding the session\n  id and the private key that opens the delivered credential. Leg two reads it and deletes it. Split\n  the legs across machines, users, containers or config-directory overrides and the exchange cannot\n  complete.\n- **`--code -` with no setup in progress exits `2`** and says so. Run leg one first.\n- The code is short, case-insensitive, and drops anything that is not one of its own characters, so\n  a pasted code with stray spaces or punctuation is still accepted.\n\n### Human shape\n\nWith stdout on a terminal and no `--json`, `setup` prints the link, opens a browser, and prompts for\nthe code (up to three attempts). `--no-browser` prints the link rather than opening it, which is what\nyou want over SSH or anywhere a browser would open on the wrong machine.\n\nOne asymmetry to know before scripting it: **stdout on a terminal with stdin piped is refused at exit\n`2`**, because there is nowhere to paste a code into. It names `CURVIATE_API_KEY` and\n`curviate login --api-key -` as the alternatives. A *fully* piped invocation is not that case: it is\nthe agent shape above, and it exits `0`.\n\n### What each failure means\n\n| Exit | Cause | What to do |\n|---|---|---|\n| `0` | Authenticated. The key is saved to the named profile. | Continue to `doctor`. |\n| `2` | Usage: no setup in progress, or a terminal was needed and there was none. | Fix the invocation. Never retry unchanged. |\n| `3` | The code was wrong, expired, or the attempts ran out; or the workspace has no API key to deliver; or the key saved but a verifying call did not succeed. **Read the message: these are deliberately four different sentences, and only the first is fixed by starting over.** | Wrong or expired code: run `setup` again for a fresh one. No API key: create one in the dashboard first. Saved but unverified: run `doctor`. |\n| `6` | Too many attempts against this endpoint. | Wait, then try again. |\n| `7` | The API could not be reached. | Check the network, and the base URL if you overrode it. |\n| `1` | The exchange failed in a way the CLI did not expect, or the delivered credential could not be opened by this process. | Worth one retry. If it repeats it is a bug to report, not a state to work around. |\n\nA code is short-lived and allows only a handful of attempts. If in doubt, start a fresh `setup`\nrather than reusing anything.\n\n## 3. Confirm: `curviate doctor`\n\n```bash\ncurviate doctor --json\n```\n\nIt reports the CLI version, the config path, the active profile, the base URL, where the credential\nresolved from, **which workspace it authenticated as**, whether the API is reachable, whether the\ncredential is accepted, and every connected account with its status.\n\nThree things that surprise people:\n\n- **Run `setup` first, then `doctor`, not the other way round.** Reachability is only tested through\n  a real call, so with no credential resolved `doctor` reports the API as unreachable. That is not a\n  network problem; there was nothing to call with.\n- **The workspace line is populated only for a credential `setup` wrote.** A key supplied through the\n  environment or `login` authenticates perfectly well, but `doctor` has no name to show for it and\n  says so. And where a name is shown it identifies the workspace; it is not promised to be a\n  friendly, human-chosen label.\n- **Zero connected accounts is a pass, not a failure.** `doctor` reports `0 connected` and exits `0`.\n  That is the expected state of a workspace nobody has connected an account to yet.\n\n`doctor` reports rather than throws, so it prints a report and not an error envelope. Branch on the\nexit code and read `checks[]` for which stage failed:\n\n- **`0`**: every check passed.\n- **`2`**: the request was refused before it was sent, so nothing reached the network. An empty\n  credential, or a malformed base URL (the report's detail reads `Invalid base URL: expected an\n  absolute http:\u002F\u002F or https:\u002F\u002F URL`). Fix the invocation or the value; a retry cannot help.\n- **`3`**: no credential resolved, or one resolved and was rejected. Run `setup`.\n- **`7`**: the API could not be reached, or was reached and answered with a platform fault. Both are\n  worth a retry.\n\n**This list is not exhaustive, and the codes beyond it are not `doctor`'s own.** The credential check\nis a real API call, and whatever refusal comes back is passed straight through, so any code the API\ncan produce can surface here. The one a first run meets most often is **exit `5` on a workspace with\nno active seat**: the credential is fine and the network is fine, and no amount of re-running `setup`\nwill change it. Look an unfamiliar code up in the area skill for the surface you are about to use:\neach ends with a table of the codes its commands produce and the action each implies.\n\nThe `checks[]` entries separate the three stages, and the wording is exact: `api reachable` reading\n`not checked` means the request never left this machine, while `could not reach` means it left and\nfound nothing. `credential valid` reading `not checked` means nothing asked the credential anything;\nit is not a verdict on the credential, so do not go looking for a bad key on the strength of it.\n\n## 4. Connect a LinkedIn account\n\nCurviate acts on LinkedIn through an account you connect. Until one is connected, authentication is\ncomplete and correct while **every account-scoped command is unusable**: that is the whole state,\nand it is not an error to be debugged.\n\n```bash\ncurviate account list --json    # empty on a fresh workspace\n```\n\nIf `setup` reported an `account_id`, an account is already connected **and already set as this\nprofile's default**; skip the rest of this step, including the block below, and go to step 5.\n\nOtherwise, find a free seat first:\n\n```bash\ncurviate account seats --json    # seat_id of any entry with \"occupied\": false\n```\n\nThen connect one with `curviate account link --seat-id \u003Cid> ...`. It attaches a LinkedIn account to\nthat seat and usually needs a verification code, which means a human. Non-interactive shells get exit\n`12` and finish through the checkpoint flow. **The command surface, its flags and the checkpoint\ncommands are in `curviate-profile`**: read that before running it, because a half-finished connect\nleaves a session to poll rather than a clean failure.\n\nThen tell the CLI which account to act as:\n\n```bash\ncurviate account list --json              # the acc_id of the account you just connected\ncurviate config set-account \u003Cacc_id>      # make it this profile's default\n```\n\n**Do not skip this.** `setup` stores a default account only when the workspace already had one to\nhand back, which is exactly what the expected first run does not have. Without a default, every\naccount-scoped command, including the demonstration below, stops at exit `2` asking for `--account`.\nSet it once here, or pass `--account \u003Cacc_id>` on each call. **`config set-account` writes to the\nstored profile, so it needs one**: if your credential came from `CURVIATE_API_KEY` rather than\n`setup`, it exits `2` saying there is no config file, and `--account \u003Cacc_id>` per call (or\n`CURVIATE_ACCOUNT` in the environment) is the path for you. Account ids change when an account is\nreconnected, so read one live rather than hard-coding it.\n\n## 5. Prove the whole path: the same read, twice\n\nThis is the demonstration, and it is worth running because it exercises authentication, the\nconnected account, projection and the store in one pass. Both calls are reads of your own profile.\n\n```bash\ncurviate profile me --mode live --json          # \"source\":\"live\"\ncurviate profile me --mode cache_only --json    # \"source\":\"store\", with \"observed_at\"\n```\n\nThe first forces a live call to LinkedIn. The second refuses to go to LinkedIn at all and answers\nfrom the copy the first one stored, so it comes back with `source: store` and an `observed_at`\ntimestamp saying when that copy was taken.\n\n**Read `source` rather than assuming it.** That field, not the freshness you asked for, is what\nactually happened. The full set of modes, and what a `cache_only` read does when nothing is stored,\nare in `curviate-profile`.\n\n## Full command surface\n\n\u003C!-- generated: command surface, CLI 0.33.0 -->\n\nRead from the CLI's own `--help` at version 0.33.0. Descriptions, traps and confidence\ntags elsewhere in this skill are hand-written and carry the version they were established against.\n\nEvery command below that takes flags at all also accepts `--base-url`, `--json`, `--profile`.\n\n| Command | Arguments | Flags |\n|---|---|---|\n| `curviate setup` | *(none)* | `--no-browser`, `--code` |\n| `curviate doctor` | *(none)* | `--api-key`, `--timeout` |\n| `curviate login` | *(none)* | `--api-key`, `--account` |\n\n\u003C!-- \u002Fgenerated -->\n\n## Where to go next\n\nBack to `curviate` for the dispatch table. The common first tasks: look someone up\n(`curviate-profile`), find a set of people (`curviate-search`), read your inbox (`curviate-inbox`).\nEach area skill ends with the exit codes its commands can produce and what each one implies; branch\non those, never on the message text.\n","# Curviate: the first run\n\nFour steps, in this order: install, authenticate, connect an account, prove it. Every command here\nis a read. Nothing in this skill posts, messages, invites, follows or endorses anyone.\n\nEstablished against CLI `0.33.0`.\n\n## 1. Install the CLI\n\n```bash\nnpm install -g @curviate\u002Fcli\ncurviate --version    # needs Node 18 or newer\n```\n\n## 2. Authenticate this machine: `curviate setup`\n\n`setup` opens the dashboard, takes the short code it shows you, and saves an API key into a local\nprofile. **The key is never printed and never passed on a command line.**\n\nThe command has two shapes, and which one you get is decided by whether **stdout** is a terminal.\n\n### Agent shape: two legs, because a browser has to happen in between\n\nWhen stdout is not a terminal, or when `--json` is passed, `setup` prints a JSON object and exits\n`0`. It does not prompt and it does not open a browser:\n\n```bash\ncurviate setup --json\n# {\"authorize_url\":\"…\",\"next_step\":\"curviate setup --code -\",\"instructions\":\"…\"}\n```\n\nOpen `authorize_url` in a browser signed in to the workspace, press Authorize, and read back the\ncode it displays. Then hand that code to the second leg **on stdin**:\n\n```bash\nprintf '%s' \"$CODE\" | curviate setup --code -\n# {\"ok\":true,\"tenant\":\"…\",\"profile\":\"default\",\"account_id\":\"…\"}\n```\n\n- **`--code -` reads from stdin deliberately.** Passing the code as a flag value works but warns:\n  a value on the command line is visible to other processes through `ps` and is saved in shell\n  history.\n- **The two legs must run on the same machine, under the same configuration directory.** Leg one\n  writes a short-lived resume file beside the config file, readable only by you, holding the session\n  id and the private key that opens the delivered credential. Leg two reads it and deletes it. Split\n  the legs across machines, users, containers or config-directory overrides and the exchange cannot\n  complete.\n- **`--code -` with no setup in progress exits `2`** and says so. Run leg one first.\n- The code is short, case-insensitive, and drops anything that is not one of its own characters, so\n  a pasted code with stray spaces or punctuation is still accepted.\n\n### Human shape\n\nWith stdout on a terminal and no `--json`, `setup` prints the link, opens a browser, and prompts for\nthe code (up to three attempts). `--no-browser` prints the link rather than opening it, which is what\nyou want over SSH or anywhere a browser would open on the wrong machine.\n\nOne asymmetry to know before scripting it: **stdout on a terminal with stdin piped is refused at exit\n`2`**, because there is nowhere to paste a code into. It names `CURVIATE_API_KEY` and\n`curviate login --api-key -` as the alternatives. A *fully* piped invocation is not that case: it is\nthe agent shape above, and it exits `0`.\n\n### What each failure means\n\n| Exit | Cause | What to do |\n|---|---|---|\n| `0` | Authenticated. The key is saved to the named profile. | Continue to `doctor`. |\n| `2` | Usage: no setup in progress, or a terminal was needed and there was none. | Fix the invocation. Never retry unchanged. |\n| `3` | The code was wrong, expired, or the attempts ran out; or the workspace has no API key to deliver; or the key saved but a verifying call did not succeed. **Read the message: these are deliberately four different sentences, and only the first is fixed by starting over.** | Wrong or expired code: run `setup` again for a fresh one. No API key: create one in the dashboard first. Saved but unverified: run `doctor`. |\n| `6` | Too many attempts against this endpoint. | Wait, then try again. |\n| `7` | The API could not be reached. | Check the network, and the base URL if you overrode it. |\n| `1` | The exchange failed in a way the CLI did not expect, or the delivered credential could not be opened by this process. | Worth one retry. If it repeats it is a bug to report, not a state to work around. |\n\nA code is short-lived and allows only a handful of attempts. If in doubt, start a fresh `setup`\nrather than reusing anything.\n\n## 3. Confirm: `curviate doctor`\n\n```bash\ncurviate doctor --json\n```\n\nIt reports the CLI version, the config path, the active profile, the base URL, where the credential\nresolved from, **which workspace it authenticated as**, whether the API is reachable, whether the\ncredential is accepted, and every connected account with its status.\n\nThree things that surprise people:\n\n- **Run `setup` first, then `doctor`, not the other way round.** Reachability is only tested through\n  a real call, so with no credential resolved `doctor` reports the API as unreachable. That is not a\n  network problem; there was nothing to call with.\n- **The workspace line is populated only for a credential `setup` wrote.** A key supplied through the\n  environment or `login` authenticates perfectly well, but `doctor` has no name to show for it and\n  says so. And where a name is shown it identifies the workspace; it is not promised to be a\n  friendly, human-chosen label.\n- **Zero connected accounts is a pass, not a failure.** `doctor` reports `0 connected` and exits `0`.\n  That is the expected state of a workspace nobody has connected an account to yet.\n\n`doctor` reports rather than throws, so it prints a report and not an error envelope. Branch on the\nexit code and read `checks[]` for which stage failed:\n\n- **`0`**: every check passed.\n- **`2`**: the request was refused before it was sent, so nothing reached the network. An empty\n  credential, or a malformed base URL (the report's detail reads `Invalid base URL: expected an\n  absolute http:\u002F\u002F or https:\u002F\u002F URL`). Fix the invocation or the value; a retry cannot help.\n- **`3`**: no credential resolved, or one resolved and was rejected. Run `setup`.\n- **`7`**: the API could not be reached, or was reached and answered with a platform fault. Both are\n  worth a retry.\n\n**This list is not exhaustive, and the codes beyond it are not `doctor`'s own.** The credential check\nis a real API call, and whatever refusal comes back is passed straight through, so any code the API\ncan produce can surface here. The one a first run meets most often is **exit `5` on a workspace with\nno active seat**: the credential is fine and the network is fine, and no amount of re-running `setup`\nwill change it. Look an unfamiliar code up in the area skill for the surface you are about to use:\neach ends with a table of the codes its commands produce and the action each implies.\n\nThe `checks[]` entries separate the three stages, and the wording is exact: `api reachable` reading\n`not checked` means the request never left this machine, while `could not reach` means it left and\nfound nothing. `credential valid` reading `not checked` means nothing asked the credential anything;\nit is not a verdict on the credential, so do not go looking for a bad key on the strength of it.\n\n## 4. Connect a LinkedIn account\n\nCurviate acts on LinkedIn through an account you connect. Until one is connected, authentication is\ncomplete and correct while **every account-scoped command is unusable**: that is the whole state,\nand it is not an error to be debugged.\n\n```bash\ncurviate account list --json    # empty on a fresh workspace\n```\n\nIf `setup` reported an `account_id`, an account is already connected **and already set as this\nprofile's default**; skip the rest of this step, including the block below, and go to step 5.\n\nOtherwise, find a free seat first:\n\n```bash\ncurviate account seats --json    # seat_id of any entry with \"occupied\": false\n```\n\nThen connect one with `curviate account link --seat-id \u003Cid> ...`. It attaches a LinkedIn account to\nthat seat and usually needs a verification code, which means a human. Non-interactive shells get exit\n`12` and finish through the checkpoint flow. **The command surface, its flags and the checkpoint\ncommands are in `curviate-profile`**: read that before running it, because a half-finished connect\nleaves a session to poll rather than a clean failure.\n\nThen tell the CLI which account to act as:\n\n```bash\ncurviate account list --json              # the acc_id of the account you just connected\ncurviate config set-account \u003Cacc_id>      # make it this profile's default\n```\n\n**Do not skip this.** `setup` stores a default account only when the workspace already had one to\nhand back, which is exactly what the expected first run does not have. Without a default, every\naccount-scoped command, including the demonstration below, stops at exit `2` asking for `--account`.\nSet it once here, or pass `--account \u003Cacc_id>` on each call. **`config set-account` writes to the\nstored profile, so it needs one**: if your credential came from `CURVIATE_API_KEY` rather than\n`setup`, it exits `2` saying there is no config file, and `--account \u003Cacc_id>` per call (or\n`CURVIATE_ACCOUNT` in the environment) is the path for you. Account ids change when an account is\nreconnected, so read one live rather than hard-coding it.\n\n## 5. Prove the whole path: the same read, twice\n\nThis is the demonstration, and it is worth running because it exercises authentication, the\nconnected account, projection and the store in one pass. Both calls are reads of your own profile.\n\n```bash\ncurviate profile me --mode live --json          # \"source\":\"live\"\ncurviate profile me --mode cache_only --json    # \"source\":\"store\", with \"observed_at\"\n```\n\nThe first forces a live call to LinkedIn. The second refuses to go to LinkedIn at all and answers\nfrom the copy the first one stored, so it comes back with `source: store` and an `observed_at`\ntimestamp saying when that copy was taken.\n\n**Read `source` rather than assuming it.** That field, not the freshness you asked for, is what\nactually happened. The full set of modes, and what a `cache_only` read does when nothing is stored,\nare in `curviate-profile`.\n\n## Full command surface\n\n\u003C!-- generated: command surface, CLI 0.33.0 -->\n\nRead from the CLI's own `--help` at version 0.33.0. Descriptions, traps and confidence\ntags elsewhere in this skill are hand-written and carry the version they were established against.\n\nEvery command below that takes flags at all also accepts `--base-url`, `--json`, `--profile`.\n\n| Command | Arguments | Flags |\n|---|---|---|\n| `curviate setup` | *(none)* | `--no-browser`, `--code` |\n| `curviate doctor` | *(none)* | `--api-key`, `--timeout` |\n| `curviate login` | *(none)* | `--api-key`, `--account` |\n\n\u003C!-- \u002Fgenerated -->\n\n## Where to go next\n\nBack to `curviate` for the dispatch table. The common first tasks: look someone up\n(`curviate-profile`), find a set of people (`curviate-search`), read your inbox (`curviate-inbox`).\nEach area skill ends with the exit codes its commands can produce and what each one implies; branch\non those, never on the message text.\n",{"name":5,"tags":24,"author":31,"license":15,"version":32,"repository":33,"description":7},[25,26,27,28,29,30],"LinkedIn","CLI","Agents","Sales","Recruiting","Outreach","Curviate","0.1.0","https:\u002F\u002Fgithub.com\u002FCurviate\u002Fcurviate-plugin","main","4e647b68aabe849e143b6950971c380f7adccdef","components\u002Fskills\u002Fcurviate\u002Fcurviate-quickstart","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code","https:\u002F\u002Frocketlauncher.ai\u002Fclaude-code","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens","CEO of Rocketlauncher.ai\r\n\r\nObsessed with AI\r\n\r\njoin  https:\u002F\u002Fwww.skool.com\u002Frocketlauncher-university\r\n👉🏻 it's free ","2026-10-13 00:52:14",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill curviate-quickstart",{"tool":48,"command":49},"bunx","bunx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill curviate-quickstart",{"tool":51,"command":52},"pnpm","pnpm dlx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill curviate-quickstart","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fcurviate\u002Fcurviate-quickstart\u002FSKILL.md",true,[],[57,64,73,80,87,94],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7EQFDF4T3K89WMFVFQVT3C8","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7EQFA5XQ0811Q4Q0WCFASZG","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\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},"01M7EQF4J6C2WKQWD9E2RQC6MJ","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\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},"01M7EQF1AT655CYYZBEQ8V6Z9D","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\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},"01M7EQEY9ENH0G2EJ1WD6C1CE8","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7EQESHEKPTE0QPW9R6XV5K2","rote","Compile a proven agent skill (a SKILL.md plus references) into a deterministic pipeline that runs without an LLM in the loop, then serve it back to Claude as an MCP tool. Use when: rote, compile this skill, turn this skill into a workflow, make this skill deterministic, make this skill cheaper or faster, harden this skill for production, run this skill as a background job.","https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Frote\u002FSKILL.md",[],[]]