[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMCBJNWBB3P7T8APBYNDWD":3,"skill-same:01M7EMCBJNWBB3P7T8APBYNDWD":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},"01M7EMCBJNWBB3P7T8APBYNDWD","curviate-jobs",null,"Create, publish and manage classic LinkedIn job postings with the Curviate CLI, and read their applicants. Covers `job` (get, list, create, update, budget, publish, close) and `job applicants` \u002F `job applicant get|resume`, the draft-then-publish flow, the subscription gate that stops a publish even on the free mode, and the read-back delay after an update. Use when drafting or updating a posting, pricing or publishing one, closing one, or pulling applicants and résumés.","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-jobs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: curviate-jobs\ndescription: \"Create, publish and manage classic LinkedIn job postings with the Curviate CLI, and read their applicants. Covers `job` (get, list, create, update, budget, publish, close) and `job applicants` \u002F `job applicant get|resume`, the draft-then-publish flow, the subscription gate that stops a publish even on the free mode, and the read-back delay after an update. Use when drafting or updating a posting, pricing or publishing one, closing one, or pulling applicants and résumés.\"\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: job postings and applicants\n\nEvery posting starts as a draft. Drafts are free and reversible; publishing is neither. The two\nthings that surprise agents here are that **a free publish is still subscription-gated** and that\n**an update's read-back lags the write**.\n\nCommand surface established against CLI `0.33.0`.\n\n## Before any command\n\n```bash\nnpm install -g @curviate\u002Fcli && curviate --version    # needs Node 18 or newer\ncurviate login --api-key \u003Ckey>                        # or export CURVIATE_API_KEY\ncurviate account list --json                          # the acc_id for --account\n```\n\n- **Credentials resolve flag > environment > stored profile** (`CURVIATE_API_KEY`,\n  `CURVIATE_BASE_URL`, `CURVIATE_ACCOUNT`).\n- **`--profile \u003Cname>` picks the stored credential set; `--account \u003Cacc_id>` picks which connected\n  LinkedIn account owns the posting.**\n- **`--preview` before every write**, and especially before a publish. On a read command it is\n  refused with exit `2`.\n- **`--json` on anything you parse**; **`--fields a,b,c`** to project; **`--verbose`** when a slim\n  response looks suspiciously empty.\n- **Put global flags at the end of the command.**\n- **Branch on the exit code, never on prose.** See the table at the end.\n- These are not retrieval-mode commands: `--mode`\u002F`--max-age` are refused here with `unknown flag`,\n  exit `2`. **`job publish --mode` is a different flag with the same name**: it selects a publishing\n  publishing mode and can spend real money. See `curviate-profile` for retrieval mode.\n\n## The commands\n\n| Command | What it does | Confidence |\n|---|---|---|\n| `curviate job get \u003Cid>` | One public posting's full detail. Takes a job URL or a bare numeric id. No seat needed. | proven |\n| `curviate job list --state \u003CDRAFT\\|OPEN\\|CLOSED\\|REVIEW\\|SUSPENDED>` | Your own postings by state. `--state` is required. | proven |\n| `curviate job create …` | Create a **draft**. Never publishes, never spends. | proven |\n| `curviate job update \u003Cid> …` | Partial update to a posting you own; same flags as `create`. | proven |\n| `curviate job budget \u003Cid>` | Price a publish before committing any money. | proven |\n| `curviate job publish \u003Cid> --mode FREE\\|PROMOTED\\|PROMOTED_PLUS` | Publish a draft. `PROMOTED` and `PROMOTED_PLUS` spend real money and additionally require `--budget-currency` (ISO-4217), `--budget-amount` and `--budget-scope` (`DAILY` or `TOTAL`). | wired, never live-fired |\n| `curviate job close \u003Cid>` | Stop a posting accepting applications. **Irreversible once listed.** | wired, never live-fired |\n| `curviate job applicants \u003Cid>` | Applicants to a posting you own. | proven (shape only, exercised on a draft with no applicants) |\n| `curviate job applicant get \u003Cid> \u003Capplicant_id>` | One applicant's full detail, including contact information. | proven (shape only) |\n| `curviate job applicant resume \u003Cid> \u003Capplicant_id>` | Download an applicant's résumé. Binary, write it with `-o \u003Cfile>`. | proven (shape only) |\n\n### `job create`: the required set\n\n`--description` (minimum 200 characters, enforced server-side), `--workplace-type`\n(`ON_SITE|HYBRID|REMOTE`), `--location` (a `LOCATION` parameter id, resolved via\n`curviate search parameters --type LOCATION`), `--employment-status`\n(`FULL_TIME|PART_TIME|CONTRACT|TEMPORARY|OTHER|VOLUNTEER|INTERNSHIP`), `--apply-method`\n(`linkedin` or `external`), plus a title and a company.\n\n- Title: `--job-title` as free text, or `--job-title-id` for an existing LinkedIn title.\n- Company: `--company` as free text, or `--company-id`.\n- `--apply-method linkedin` requires `--notification-email`; `--apply-method external` requires\n  `--website-url`.\n- `--skills` takes comma-separated skill parameter ids and is optional.\n\nRun `curviate job create --help` for the current required set before building a call.\n\n### Traps\n\n- **A publish is subscription-gated in practice, not just on the paid modes.** `--mode FREE` (the\n  money-free mode) still returns `LINKEDIN_FEATURE_NOT_SUBSCRIBED`, exit `5`, on an account with no\n  LinkedIn job-posting subscription. On that error nothing goes public and the draft stays a draft.\n  Expect exit `5` unless you have confirmed the subscription; do not read it as a malformed request.\n- **`publish` and `close` are wired, never live-fired.** Every test account run against this surface\n  hit the subscription gate above before a posting ever went public, so a live `200` from either\n  command has not been observed; `close`'s happy path is unreachable the same way, since nothing gets\n  published to close. The response shapes are cross-checked against the substrate's own types rather\n  than an observed call. The read and draft surface above `publish` (list\u002Fget\u002Fbudget\u002Fcreate\u002Fupdate,\n  plus the three applicant reads) does not depend on that subscription and is proven.\n- **An update lands before the read-back reflects it.** `job update` returning exit `0` was applied,\n  but its own response and an immediate `job get` can both still show the old value, while\n  `job list` (the owner view, checked minutes later) shows the update did land. Do not conclude a\n  silent no-op from a stale-looking immediate read.\n- **`job list --state` filters client-side and says so on stderr.** LinkedIn's own state filter is\n  best-effort, so the CLI re-fetches the unfiltered page walk and drops non-matching items itself,\n  logging what it dropped. Read stdout for data and stderr for what was dropped, and note that\n  `--all` may walk far more upstream pages than the filtered item count suggests.\n- **`job close` is irreversible once the posting is listed.** Preview it, and be sure.\n- **Price before you publish.** `job budget \u003Cid>` costs nothing and is the only way to know what a\n  promoted publish will spend.\n\n## A safe posting flow\n\n```bash\ncurviate job create --job-title \"…\" --company \"…\" --workplace-type REMOTE \\\n  --location \u003Cloc_id> --employment-status FULL_TIME --description \"$(cat jd.md)\" \\\n  --apply-method linkedin --notification-email \u003Cemail> --account \u003Cacc_id> --preview --json\n# re-run without --preview to create the draft, then:\ncurviate job get \u003Cid> --account \u003Cacc_id> --json          # confirm the draft\ncurviate job budget \u003Cid> --account \u003Cacc_id> --json       # price it\ncurviate job publish \u003Cid> --mode FREE --account \u003Cacc_id> --preview --json\n```\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 `--account`, `--api-key`, `--base-url`, `--beta`, `--fields`, `--json`, `--preview`, `--profile`, `--timeout`, `--verbose`.\n\n| Command | Arguments | Flags |\n|---|---|---|\n| `curviate job get` | `ID` | *(none)* |\n| `curviate job list` | *(none)* | `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay`, `--state` *(required)* |\n| `curviate job create` | *(none)* | `--job-title`, `--job-title-id`, `--company`, `--company-id`, `--workplace-type`, `--location`, `--employment-status`, `--description`, `--apply-method`, `--notification-email`, `--website-url`, `--skills` |\n| `curviate job update` | `ID` | `--job-title`, `--job-title-id`, `--company`, `--company-id`, `--workplace-type`, `--location`, `--employment-status`, `--description`, `--apply-method`, `--notification-email`, `--website-url`, `--skills` |\n| `curviate job budget` | `ID` | *(none)* |\n| `curviate job publish` | `ID` | `--mode` *(required)*, `--budget-currency`, `--budget-amount`, `--budget-scope` |\n| `curviate job close` | `ID` | *(none)* |\n| `curviate job applicants` | `ID` | `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay`, `--ratings` |\n| `curviate job applicant get` | `ID` `APPLICANTID` | *(none)* |\n| `curviate job applicant resume` | `ID` `APPLICANTID` | `-o, --output` |\n\n\u003C!-- \u002Fgenerated -->\n\n## Exit codes to branch on here\n\n| Code | Meaning | What to do |\n|---|---|---|\n| `1` | `INTERNAL` from the server itself: a genuine bug on the platform side. | Worth one retry; if it repeats it is a bug to report, not a state to work around. |\n| `2` | Usage or invalid input, often raised before any network call: a missing required flag, a description under 200 characters, a location passed as a name rather than an id. | Fix the invocation. Never retry unchanged. |\n| `4` | Not found: the posting does not exist, or is not yours. | Re-check the id and the acting account. |\n| `5` | Three causes, one code: read `error.code`. `NO_ACTIVE_SEAT`: the account is on no active seat. `LINKEDIN_FEATURE_NOT_SUBSCRIBED`: LinkedIn itself lacks the feature. `BETA_NOT_ENABLED`: the operation is beta-gated and this workspace has not opted in. | Branch on `error.code`: the three fixes have nothing in common, and none is fixed by retrying unchanged. |\n| `6` | `PLATFORM_RATE_LIMIT` and its siblings. Carries `retry_after` in whole seconds. A response naming `budgetRow` means only that row is paused; every other row on the account keeps working. | **Back off and retry** after that many seconds. On a named `budgetRow`, switch to other work on the account rather than backing off across the board. |\n| `7` | Transient platform fault: a request that got no response at all (network error, DNS failure, timeout) or one that came back as something other than a valid API answer. Carries `retryLikelyToSucceed: true`. | Retry with backoff. |\n| `11` | Billing: payment, a cancelled seat, or a subscription lock. `SUBSCRIPTION_BUSY` is retry-likely; check the envelope. | Resolve it in the dashboard. |\n| `13` | `BUDGET_EXHAUSTED`: a safety rule of your own refused the action, not LinkedIn. Read `error.safetyReason`: `ceiling` means the row named in `error.budgetRow` hit its configured limit; `activity_window` means the account is outside the hours it works in (no `budgetRow` on that one). **Nothing reached LinkedIn and nothing was spent.** `reset_at` can be weeks out, and may be `null` where no clock frees it. | **Do not back off and retry.** `error.safetyHint.parameter` names the exact setting to change. Read `quotas[]` via `curviate account get \u003Cacc_id> --json`, then wait for the named reset or change that setting. |\n","# Curviate: job postings and applicants\n\nEvery posting starts as a draft. Drafts are free and reversible; publishing is neither. The two\nthings that surprise agents here are that **a free publish is still subscription-gated** and that\n**an update's read-back lags the write**.\n\nCommand surface established against CLI `0.33.0`.\n\n## Before any command\n\n```bash\nnpm install -g @curviate\u002Fcli && curviate --version    # needs Node 18 or newer\ncurviate login --api-key \u003Ckey>                        # or export CURVIATE_API_KEY\ncurviate account list --json                          # the acc_id for --account\n```\n\n- **Credentials resolve flag > environment > stored profile** (`CURVIATE_API_KEY`,\n  `CURVIATE_BASE_URL`, `CURVIATE_ACCOUNT`).\n- **`--profile \u003Cname>` picks the stored credential set; `--account \u003Cacc_id>` picks which connected\n  LinkedIn account owns the posting.**\n- **`--preview` before every write**, and especially before a publish. On a read command it is\n  refused with exit `2`.\n- **`--json` on anything you parse**; **`--fields a,b,c`** to project; **`--verbose`** when a slim\n  response looks suspiciously empty.\n- **Put global flags at the end of the command.**\n- **Branch on the exit code, never on prose.** See the table at the end.\n- These are not retrieval-mode commands: `--mode`\u002F`--max-age` are refused here with `unknown flag`,\n  exit `2`. **`job publish --mode` is a different flag with the same name**: it selects a publishing\n  publishing mode and can spend real money. See `curviate-profile` for retrieval mode.\n\n## The commands\n\n| Command | What it does | Confidence |\n|---|---|---|\n| `curviate job get \u003Cid>` | One public posting's full detail. Takes a job URL or a bare numeric id. No seat needed. | proven |\n| `curviate job list --state \u003CDRAFT\\|OPEN\\|CLOSED\\|REVIEW\\|SUSPENDED>` | Your own postings by state. `--state` is required. | proven |\n| `curviate job create …` | Create a **draft**. Never publishes, never spends. | proven |\n| `curviate job update \u003Cid> …` | Partial update to a posting you own; same flags as `create`. | proven |\n| `curviate job budget \u003Cid>` | Price a publish before committing any money. | proven |\n| `curviate job publish \u003Cid> --mode FREE\\|PROMOTED\\|PROMOTED_PLUS` | Publish a draft. `PROMOTED` and `PROMOTED_PLUS` spend real money and additionally require `--budget-currency` (ISO-4217), `--budget-amount` and `--budget-scope` (`DAILY` or `TOTAL`). | wired, never live-fired |\n| `curviate job close \u003Cid>` | Stop a posting accepting applications. **Irreversible once listed.** | wired, never live-fired |\n| `curviate job applicants \u003Cid>` | Applicants to a posting you own. | proven (shape only, exercised on a draft with no applicants) |\n| `curviate job applicant get \u003Cid> \u003Capplicant_id>` | One applicant's full detail, including contact information. | proven (shape only) |\n| `curviate job applicant resume \u003Cid> \u003Capplicant_id>` | Download an applicant's résumé. Binary, write it with `-o \u003Cfile>`. | proven (shape only) |\n\n### `job create`: the required set\n\n`--description` (minimum 200 characters, enforced server-side), `--workplace-type`\n(`ON_SITE|HYBRID|REMOTE`), `--location` (a `LOCATION` parameter id, resolved via\n`curviate search parameters --type LOCATION`), `--employment-status`\n(`FULL_TIME|PART_TIME|CONTRACT|TEMPORARY|OTHER|VOLUNTEER|INTERNSHIP`), `--apply-method`\n(`linkedin` or `external`), plus a title and a company.\n\n- Title: `--job-title` as free text, or `--job-title-id` for an existing LinkedIn title.\n- Company: `--company` as free text, or `--company-id`.\n- `--apply-method linkedin` requires `--notification-email`; `--apply-method external` requires\n  `--website-url`.\n- `--skills` takes comma-separated skill parameter ids and is optional.\n\nRun `curviate job create --help` for the current required set before building a call.\n\n### Traps\n\n- **A publish is subscription-gated in practice, not just on the paid modes.** `--mode FREE` (the\n  money-free mode) still returns `LINKEDIN_FEATURE_NOT_SUBSCRIBED`, exit `5`, on an account with no\n  LinkedIn job-posting subscription. On that error nothing goes public and the draft stays a draft.\n  Expect exit `5` unless you have confirmed the subscription; do not read it as a malformed request.\n- **`publish` and `close` are wired, never live-fired.** Every test account run against this surface\n  hit the subscription gate above before a posting ever went public, so a live `200` from either\n  command has not been observed; `close`'s happy path is unreachable the same way, since nothing gets\n  published to close. The response shapes are cross-checked against the substrate's own types rather\n  than an observed call. The read and draft surface above `publish` (list\u002Fget\u002Fbudget\u002Fcreate\u002Fupdate,\n  plus the three applicant reads) does not depend on that subscription and is proven.\n- **An update lands before the read-back reflects it.** `job update` returning exit `0` was applied,\n  but its own response and an immediate `job get` can both still show the old value, while\n  `job list` (the owner view, checked minutes later) shows the update did land. Do not conclude a\n  silent no-op from a stale-looking immediate read.\n- **`job list --state` filters client-side and says so on stderr.** LinkedIn's own state filter is\n  best-effort, so the CLI re-fetches the unfiltered page walk and drops non-matching items itself,\n  logging what it dropped. Read stdout for data and stderr for what was dropped, and note that\n  `--all` may walk far more upstream pages than the filtered item count suggests.\n- **`job close` is irreversible once the posting is listed.** Preview it, and be sure.\n- **Price before you publish.** `job budget \u003Cid>` costs nothing and is the only way to know what a\n  promoted publish will spend.\n\n## A safe posting flow\n\n```bash\ncurviate job create --job-title \"…\" --company \"…\" --workplace-type REMOTE \\\n  --location \u003Cloc_id> --employment-status FULL_TIME --description \"$(cat jd.md)\" \\\n  --apply-method linkedin --notification-email \u003Cemail> --account \u003Cacc_id> --preview --json\n# re-run without --preview to create the draft, then:\ncurviate job get \u003Cid> --account \u003Cacc_id> --json          # confirm the draft\ncurviate job budget \u003Cid> --account \u003Cacc_id> --json       # price it\ncurviate job publish \u003Cid> --mode FREE --account \u003Cacc_id> --preview --json\n```\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 `--account`, `--api-key`, `--base-url`, `--beta`, `--fields`, `--json`, `--preview`, `--profile`, `--timeout`, `--verbose`.\n\n| Command | Arguments | Flags |\n|---|---|---|\n| `curviate job get` | `ID` | *(none)* |\n| `curviate job list` | *(none)* | `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay`, `--state` *(required)* |\n| `curviate job create` | *(none)* | `--job-title`, `--job-title-id`, `--company`, `--company-id`, `--workplace-type`, `--location`, `--employment-status`, `--description`, `--apply-method`, `--notification-email`, `--website-url`, `--skills` |\n| `curviate job update` | `ID` | `--job-title`, `--job-title-id`, `--company`, `--company-id`, `--workplace-type`, `--location`, `--employment-status`, `--description`, `--apply-method`, `--notification-email`, `--website-url`, `--skills` |\n| `curviate job budget` | `ID` | *(none)* |\n| `curviate job publish` | `ID` | `--mode` *(required)*, `--budget-currency`, `--budget-amount`, `--budget-scope` |\n| `curviate job close` | `ID` | *(none)* |\n| `curviate job applicants` | `ID` | `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay`, `--ratings` |\n| `curviate job applicant get` | `ID` `APPLICANTID` | *(none)* |\n| `curviate job applicant resume` | `ID` `APPLICANTID` | `-o, --output` |\n\n\u003C!-- \u002Fgenerated -->\n\n## Exit codes to branch on here\n\n| Code | Meaning | What to do |\n|---|---|---|\n| `1` | `INTERNAL` from the server itself: a genuine bug on the platform side. | Worth one retry; if it repeats it is a bug to report, not a state to work around. |\n| `2` | Usage or invalid input, often raised before any network call: a missing required flag, a description under 200 characters, a location passed as a name rather than an id. | Fix the invocation. Never retry unchanged. |\n| `4` | Not found: the posting does not exist, or is not yours. | Re-check the id and the acting account. |\n| `5` | Three causes, one code: read `error.code`. `NO_ACTIVE_SEAT`: the account is on no active seat. `LINKEDIN_FEATURE_NOT_SUBSCRIBED`: LinkedIn itself lacks the feature. `BETA_NOT_ENABLED`: the operation is beta-gated and this workspace has not opted in. | Branch on `error.code`: the three fixes have nothing in common, and none is fixed by retrying unchanged. |\n| `6` | `PLATFORM_RATE_LIMIT` and its siblings. Carries `retry_after` in whole seconds. A response naming `budgetRow` means only that row is paused; every other row on the account keeps working. | **Back off and retry** after that many seconds. On a named `budgetRow`, switch to other work on the account rather than backing off across the board. |\n| `7` | Transient platform fault: a request that got no response at all (network error, DNS failure, timeout) or one that came back as something other than a valid API answer. Carries `retryLikelyToSucceed: true`. | Retry with backoff. |\n| `11` | Billing: payment, a cancelled seat, or a subscription lock. `SUBSCRIPTION_BUSY` is retry-likely; check the envelope. | Resolve it in the dashboard. |\n| `13` | `BUDGET_EXHAUSTED`: a safety rule of your own refused the action, not LinkedIn. Read `error.safetyReason`: `ceiling` means the row named in `error.budgetRow` hit its configured limit; `activity_window` means the account is outside the hours it works in (no `budgetRow` on that one). **Nothing reached LinkedIn and nothing was spent.** `reset_at` can be weeks out, and may be `null` where no clock frees it. | **Do not back off and retry.** `error.safetyHint.parameter` names the exact setting to change. Read `quotas[]` via `curviate account get \u003Cacc_id> --json`, then wait for the named reset or change that setting. |\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-jobs","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-jobs",{"tool":48,"command":49},"bunx","bunx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill curviate-jobs",{"tool":51,"command":52},"pnpm","pnpm dlx skills add marnixGeerkens\u002Frocketlauncher-claude-code --skill curviate-jobs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FmarnixGeerkens\u002Frocketlauncher-claude-code\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fcurviate\u002Fcurviate-jobs\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",[],[]]