[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ENRVGDXJKRCC48BVNAWDHZ":3,"skill-same:01M7ENRVGDXJKRCC48BVNAWDHZ":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":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M7ENRVGDXJKRCC48BVNAWDHZ","curviate-engage",null,"Create and engage with LinkedIn content using the Curviate CLI. Covers `post` (get, create, react, unreact, reactions, delete, save, saved, unsave, user-posts, user-reactions), `comment` (list, add, reply, edit, delete, replies, react, unreact, reactions, user), `feed home` and `notification`. Carries the write-versus-read reaction vocabularies, post-identifier forms, and the pagination trap on reaction lists. Use when posting, commenting, reacting, reading the home feed, or working through notifications.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-curviate-engage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: curviate-engage\ndescription: \"Create and engage with LinkedIn content using the Curviate CLI. Covers `post` (get, create, react, unreact, reactions, delete, save, saved, unsave, user-posts, user-reactions), `comment` (list, add, reply, edit, delete, replies, react, unreact, reactions, user), `feed home` and `notification`. Carries the write-versus-read reaction vocabularies, post-identifier forms, and the pagination trap on reaction lists. Use when posting, commenting, reacting, reading the home feed, or working through notifications.\"\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: posts, comments, reactions, feed\n\nEngagement is the cheapest way to be visible, and every write here is public and attributable. Two\nvocabularies and three identifier forms cause most failures; both are below.\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 posts, comments or reacts.** Name it explicitly on every write: a comment from\n  the wrong account is public and permanent.\n- **`--preview` before every write.** It renders the resolved request without sending. On a read\n  command it is 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` (see `curviate-profile` for the four commands that do accept them).\n\n### Text input\n\nPost and comment text is a positional argument, and `-` reads stdin. **Use a quoted heredoc**: the\nquoted delimiter disables every shell expansion, so apostrophes, accents, `$` and backticks survive\nintact:\n\n```bash\ncat \u003C\u003C'EOF' | curviate post create - --preview\nLine one.\n\nLine two.\nEOF\n```\n\n## Identifiers\n\nA post id comes in three forms and the commands are not uniformly forgiving:\n\n- The **numeric activity id** (`7459869580333576193`) is the canonical form.\n- `urn:li:activity:\u003CN>` works.\n- A **full share URL** is accepted and the id extracted from it. If a command ever rejects one,\n  extract it yourself: `POST_ID=$(echo \"\u003Cshare_url>\" | grep -oP 'activity[-\u002F]\\K\\d+')`.\n- Some builds have rejected the bare numeric id at write time on `post react`, `comment add` and\n  `comment list` while `--preview` on the same command rendered fine. If you hit that, pass the\n  base64 `id` from whatever `post get`, `post create` or list response you already hold: no extra\n  fetch needed.\n\n**In every `comment` command, `\u003Cpost_id>` is the original post's id, never the comment's.**\n`\u003Ccomment_id>` comes from `comment list \u003Cpost_id>` as `items[].id`.\n\n**`post get` answers with `social_id` (a URN); the numeric id you passed is not echoed back.**\n\n## `post`\n\n| Command | What it does | Confidence |\n|---|---|---|\n| `curviate post get \u003Cpost_id>` | One post. Adds `is_repost`, `reposted_by`, `user_reacted` and a richer `author` (headline, slug) over what a list carries. | proven |\n| `curviate post create \"\u003Ctext>\"` | Publish a post. `--attach` is repeatable for images and takes jpg, png, gif, mp4 or pdf; a single PDF produces a document post. | proven |\n| `curviate post react \u003Cpost_id> \u003Creaction>` | React to a post. `--as-organization \u003Cid>` reacts as a company page you administer. Duplicate reactions succeed silently. | proven |\n| `curviate post unreact \u003Cpost_id> \u003Creaction>` | Remove your reaction. | proven |\n| `curviate post reactions \u003Cpost_id>` | Reactions on a post: `{value, author: {id, type, name, headline, profile_url, profile_picture_url, network_distance?}}`. Page default 20, maximum 50. No timestamp exists. | proven |\n| `curviate post delete \u003Cpost_id>` | Delete a post you own. | proven |\n| `curviate post save \u003Cpost_id>` | Save to your private bookmark list. Never notifies the author, never visible to anyone else. Idempotent. | proven |\n| `curviate post unsave \u003Cpost_id>` | Remove from the bookmark list. Idempotent. | proven |\n| `curviate post saved` | Your saved posts, newest first. Each item is a preview with the snippet capped at 140 characters. | proven |\n| `curviate post user-posts \u003Cid\\|me>` | A member's own posts. Same data as `profile \u003Cid> --posts`. | proven |\n| `curviate post user-reactions \u003Cid\\|me>` | A member's own reactions. Same data as `profile \u003Cid> --reactions`. | proven |\n\n### Reaction vocabularies: write is not read\n\n| Write (`post react`, `comment react`, lowercase) | Read (`value`, `user_reacted`) |\n|---|---|\n| `like` | `LIKE` (confirmed pairing) |\n| `celebrate` | `PRAISE` (confirmed pairing) |\n| `insightful` | `INTEREST` (confirmed pairing) |\n| `support` | `APPRECIATION` (pairing unconfirmed) |\n| `love` | `EMPATHY` (pairing unconfirmed) |\n| `funny` | `ENTERTAINMENT` (pairing unconfirmed) |\n\n**Sending an uppercase read value as a write returns `INVALID_REQUEST`, exit `2`.** Always write\nlowercase. Read-side casing has been observed to vary, so **compare reaction values\ncase-insensitively** when parsing `post reactions`, `comment reactions`, or `user_reacted`.\n\n### Traps\n\n- **`post reactions` returns `cursor: null` while more reactions remain.** A single page is not the\n  reaction list. Use `--all`, and check the final line for\n  `{\"object\": \"stream_truncated\", …, \"has_more\": true}`.\n- **Check `user_reacted` on `post get` before reacting**: a duplicate reaction succeeds silently and\n  tells you nothing.\n- **A very recent create or delete can take minutes to appear in `post user-posts`** (LinkedIn-side\n  indexing). `post get \u003Cpost_id>` reflects it immediately.\n- **The post list carries no `is_repost` field.** Detect a repost by comparing the item's author name\n  against the member you queried, or call `post get \u003Cpost_id> --fields is_repost,reposted_by`. On a\n  repost, `author` is the original creator and `reposted_by` is the sharer.\n- **A company reactor carries no `network_distance`**: the key is absent, not null. Treat\n  `author.type == \"COMPANY\"` as its own signal rather than as missing data.\n- A list item already carries `id`, `parsed_datetime`, full `text`, `reaction_counter`,\n  `comment_counter`, `repost_counter`, `impressions_counter`, `author` and `attachments`, so most\n  \"read a post\" questions need no `post get` at all.\n\n## `comment`\n\n| Command | What it does | Confidence |\n|---|---|---|\n| `curviate comment list \u003Cpost_id>` | Top-level comments. Returns `id` and `social_id` (chain into `comment react`\u002F`reply`), `reply_counter` (above 0 means nested replies exist) and `author.profile_url`. | proven |\n| `curviate comment add \u003Cpost_id> \"\u003Ctext>\"` | Comment on a post. Returns the new comment's id. `--attach` takes at most one image. | proven |\n| `curviate comment reply \u003Cpost_id> \u003Ccomment_id> \"\u003Ctext>\"` | Reply to a specific comment. | proven |\n| `curviate comment edit \u003Cpost_id> \u003Ccomment_id> \"\u003Ctext>\"` | Edit your own comment. | proven |\n| `curviate comment delete \u003Cpost_id> \u003Ccomment_id>` | Delete your own comment. | proven |\n| `curviate comment replies \u003Cpost_id> \u003Ccomment_id>` | Replies to one comment. | proven |\n| `curviate comment react \u003Cpost_id> \u003Ccomment_id> \u003Creaction>` | React to a specific comment (not the post). Same lowercase write vocabulary. | proven |\n| `curviate comment unreact \u003Cpost_id> \u003Ccomment_id> \u003Creaction>` | Remove that reaction. | proven |\n| `curviate comment reactions \u003Cpost_id> \u003Ccomment_id>` | Reactions on one comment. | proven |\n| `curviate comment user \u003Cid\\|me>` | Comments a member authored. Same data as `profile \u003Cid> --comments`; each carries `post_id` for context. | proven |\n\n- **`comment list` returns only what is visible to you.** The post's own `comment_counter` is always\n  greater than or equal to the items returned, so a mismatch is not a bug.\n- **`parsed_datetime` is always null on a comment**: use `date` for the ISO timestamp.\n- **To check whether you already commented on a post, match on `parent_post.share_url`, never on\n  ids.** `parent_post.id` is base64 of a *two*-element array (`[comment_activity, post_activity]`)\n  while a post's own `id` is a one-element array, so an id comparison is always false. If you need\n  the id, decode and take element `[1]`.\n- **A very recent add or delete can take minutes to appear in `comment list`.**\n\n## `feed` and `notification`\n\n| Command | What it does | Confidence |\n|---|---|---|\n| `curviate feed home` | The connected account's home feed as agent-actionable posts. `--sort recent` (default, reverse-chronological, always available) or `--sort relevant` (LinkedIn's ranked feed, which draws on a shared throttled budget). `--sort` is ignored when `--cursor` is supplied. | proven |\n| `curviate notification list` | Notification cards, newest first, with the unread badge and a poll watermark. `--filter` selects the stream: `all` (default), `jobs`, `mentions`, `my_posts`, `my_posts_comments`, `my_posts_reactions`, `my_posts_reposts`. | proven |\n| `curviate notification delete \u003Ccard_urn>` | Delete one of your own notification cards. Idempotent, cannot be undone. | proven |\n| `curviate notification show-less \u003Ccard_urn>` | Apply \"show less like this\" to a card's source. For network-activity cards this removes the card, the same as delete. Idempotent, cannot be undone. | proven |\n\nThe feed and the notification stream are the two cheapest sources of a genuinely current thing to\nengage with: reach for them before searching for something to react to.\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`, `--json`, `--preview`, `--profile`, `--timeout`, `--verbose`.\n\n| Command | Arguments | Flags |\n|---|---|---|\n| `curviate post get` | `POSTID` | `--fields`, `--limit`, `--cursor` |\n| `curviate post create` | `TEXT` | `--attach` |\n| `curviate post react` | `POSTID` `REACTION` | `-reaction, --reactionAlias`, `--as-organization` |\n| `curviate post reactions` | `POSTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate post delete` | `POSTID` | `--fields` |\n| `curviate post unreact` | `POSTID` `REACTION` | `--fields` |\n| `curviate post saved` | *(none)* | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate post save` | `POSTID` | `--fields` |\n| `curviate post unsave` | `POSTID` | `--fields` |\n| `curviate post user-posts` | `USERID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate post user-reactions` | `USERID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate comment list` | `POSTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate comment add` | `POSTID` `TEXT` | `--fields`, `--attach` |\n| `curviate comment reply` | `POSTID` `COMMENTID` `TEXT` | `--fields`, `--attach` |\n| `curviate comment edit` | `POSTID` `COMMENTID` `TEXT` | `--fields` |\n| `curviate comment delete` | `POSTID` `COMMENTID` | `--fields` |\n| `curviate comment replies` | `POSTID` `COMMENTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate comment react` | `POSTID` `COMMENTID` `REACTION` | `--fields` |\n| `curviate comment reactions` | `POSTID` `COMMENTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate comment unreact` | `POSTID` `COMMENTID` `REACTION` | `--fields` |\n| `curviate comment user` | `USERID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate feed home` | *(none)* | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay`, `--sort` |\n| `curviate notification list` | *(none)* | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay`, `--filter` |\n| `curviate notification delete` | `CARDURN` | `--fields` |\n| `curviate notification show-less` | `CARDURN` | `--fields` |\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: an uppercase reaction value, a malformed post id, more than one attachment on a comment. | Fix the invocation. Never retry unchanged. |\n| `4` | Not found, usually a wrong identifier *form* rather than a missing post. | Re-derive the id before concluding the post is gone. |\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 (pass `--beta` for one call, or a human enables it in Settings). | 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 hiccup, or 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| `8` | Account or connection state. Read `error.code`. | `LINKEDIN_OPERATION_NOT_SUPPORTED` is permanent and never retryable; a session error needs a reconnect. |\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; nothing was posted.** `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: posts, comments, reactions, feed\n\nEngagement is the cheapest way to be visible, and every write here is public and attributable. Two\nvocabularies and three identifier forms cause most failures; both are below.\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 posts, comments or reacts.** Name it explicitly on every write: a comment from\n  the wrong account is public and permanent.\n- **`--preview` before every write.** It renders the resolved request without sending. On a read\n  command it is 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` (see `curviate-profile` for the four commands that do accept them).\n\n### Text input\n\nPost and comment text is a positional argument, and `-` reads stdin. **Use a quoted heredoc**: the\nquoted delimiter disables every shell expansion, so apostrophes, accents, `$` and backticks survive\nintact:\n\n```bash\ncat \u003C\u003C'EOF' | curviate post create - --preview\nLine one.\n\nLine two.\nEOF\n```\n\n## Identifiers\n\nA post id comes in three forms and the commands are not uniformly forgiving:\n\n- The **numeric activity id** (`7459869580333576193`) is the canonical form.\n- `urn:li:activity:\u003CN>` works.\n- A **full share URL** is accepted and the id extracted from it. If a command ever rejects one,\n  extract it yourself: `POST_ID=$(echo \"\u003Cshare_url>\" | grep -oP 'activity[-\u002F]\\K\\d+')`.\n- Some builds have rejected the bare numeric id at write time on `post react`, `comment add` and\n  `comment list` while `--preview` on the same command rendered fine. If you hit that, pass the\n  base64 `id` from whatever `post get`, `post create` or list response you already hold: no extra\n  fetch needed.\n\n**In every `comment` command, `\u003Cpost_id>` is the original post's id, never the comment's.**\n`\u003Ccomment_id>` comes from `comment list \u003Cpost_id>` as `items[].id`.\n\n**`post get` answers with `social_id` (a URN); the numeric id you passed is not echoed back.**\n\n## `post`\n\n| Command | What it does | Confidence |\n|---|---|---|\n| `curviate post get \u003Cpost_id>` | One post. Adds `is_repost`, `reposted_by`, `user_reacted` and a richer `author` (headline, slug) over what a list carries. | proven |\n| `curviate post create \"\u003Ctext>\"` | Publish a post. `--attach` is repeatable for images and takes jpg, png, gif, mp4 or pdf; a single PDF produces a document post. | proven |\n| `curviate post react \u003Cpost_id> \u003Creaction>` | React to a post. `--as-organization \u003Cid>` reacts as a company page you administer. Duplicate reactions succeed silently. | proven |\n| `curviate post unreact \u003Cpost_id> \u003Creaction>` | Remove your reaction. | proven |\n| `curviate post reactions \u003Cpost_id>` | Reactions on a post: `{value, author: {id, type, name, headline, profile_url, profile_picture_url, network_distance?}}`. Page default 20, maximum 50. No timestamp exists. | proven |\n| `curviate post delete \u003Cpost_id>` | Delete a post you own. | proven |\n| `curviate post save \u003Cpost_id>` | Save to your private bookmark list. Never notifies the author, never visible to anyone else. Idempotent. | proven |\n| `curviate post unsave \u003Cpost_id>` | Remove from the bookmark list. Idempotent. | proven |\n| `curviate post saved` | Your saved posts, newest first. Each item is a preview with the snippet capped at 140 characters. | proven |\n| `curviate post user-posts \u003Cid\\|me>` | A member's own posts. Same data as `profile \u003Cid> --posts`. | proven |\n| `curviate post user-reactions \u003Cid\\|me>` | A member's own reactions. Same data as `profile \u003Cid> --reactions`. | proven |\n\n### Reaction vocabularies: write is not read\n\n| Write (`post react`, `comment react`, lowercase) | Read (`value`, `user_reacted`) |\n|---|---|\n| `like` | `LIKE` (confirmed pairing) |\n| `celebrate` | `PRAISE` (confirmed pairing) |\n| `insightful` | `INTEREST` (confirmed pairing) |\n| `support` | `APPRECIATION` (pairing unconfirmed) |\n| `love` | `EMPATHY` (pairing unconfirmed) |\n| `funny` | `ENTERTAINMENT` (pairing unconfirmed) |\n\n**Sending an uppercase read value as a write returns `INVALID_REQUEST`, exit `2`.** Always write\nlowercase. Read-side casing has been observed to vary, so **compare reaction values\ncase-insensitively** when parsing `post reactions`, `comment reactions`, or `user_reacted`.\n\n### Traps\n\n- **`post reactions` returns `cursor: null` while more reactions remain.** A single page is not the\n  reaction list. Use `--all`, and check the final line for\n  `{\"object\": \"stream_truncated\", …, \"has_more\": true}`.\n- **Check `user_reacted` on `post get` before reacting**: a duplicate reaction succeeds silently and\n  tells you nothing.\n- **A very recent create or delete can take minutes to appear in `post user-posts`** (LinkedIn-side\n  indexing). `post get \u003Cpost_id>` reflects it immediately.\n- **The post list carries no `is_repost` field.** Detect a repost by comparing the item's author name\n  against the member you queried, or call `post get \u003Cpost_id> --fields is_repost,reposted_by`. On a\n  repost, `author` is the original creator and `reposted_by` is the sharer.\n- **A company reactor carries no `network_distance`**: the key is absent, not null. Treat\n  `author.type == \"COMPANY\"` as its own signal rather than as missing data.\n- A list item already carries `id`, `parsed_datetime`, full `text`, `reaction_counter`,\n  `comment_counter`, `repost_counter`, `impressions_counter`, `author` and `attachments`, so most\n  \"read a post\" questions need no `post get` at all.\n\n## `comment`\n\n| Command | What it does | Confidence |\n|---|---|---|\n| `curviate comment list \u003Cpost_id>` | Top-level comments. Returns `id` and `social_id` (chain into `comment react`\u002F`reply`), `reply_counter` (above 0 means nested replies exist) and `author.profile_url`. | proven |\n| `curviate comment add \u003Cpost_id> \"\u003Ctext>\"` | Comment on a post. Returns the new comment's id. `--attach` takes at most one image. | proven |\n| `curviate comment reply \u003Cpost_id> \u003Ccomment_id> \"\u003Ctext>\"` | Reply to a specific comment. | proven |\n| `curviate comment edit \u003Cpost_id> \u003Ccomment_id> \"\u003Ctext>\"` | Edit your own comment. | proven |\n| `curviate comment delete \u003Cpost_id> \u003Ccomment_id>` | Delete your own comment. | proven |\n| `curviate comment replies \u003Cpost_id> \u003Ccomment_id>` | Replies to one comment. | proven |\n| `curviate comment react \u003Cpost_id> \u003Ccomment_id> \u003Creaction>` | React to a specific comment (not the post). Same lowercase write vocabulary. | proven |\n| `curviate comment unreact \u003Cpost_id> \u003Ccomment_id> \u003Creaction>` | Remove that reaction. | proven |\n| `curviate comment reactions \u003Cpost_id> \u003Ccomment_id>` | Reactions on one comment. | proven |\n| `curviate comment user \u003Cid\\|me>` | Comments a member authored. Same data as `profile \u003Cid> --comments`; each carries `post_id` for context. | proven |\n\n- **`comment list` returns only what is visible to you.** The post's own `comment_counter` is always\n  greater than or equal to the items returned, so a mismatch is not a bug.\n- **`parsed_datetime` is always null on a comment**: use `date` for the ISO timestamp.\n- **To check whether you already commented on a post, match on `parent_post.share_url`, never on\n  ids.** `parent_post.id` is base64 of a *two*-element array (`[comment_activity, post_activity]`)\n  while a post's own `id` is a one-element array, so an id comparison is always false. If you need\n  the id, decode and take element `[1]`.\n- **A very recent add or delete can take minutes to appear in `comment list`.**\n\n## `feed` and `notification`\n\n| Command | What it does | Confidence |\n|---|---|---|\n| `curviate feed home` | The connected account's home feed as agent-actionable posts. `--sort recent` (default, reverse-chronological, always available) or `--sort relevant` (LinkedIn's ranked feed, which draws on a shared throttled budget). `--sort` is ignored when `--cursor` is supplied. | proven |\n| `curviate notification list` | Notification cards, newest first, with the unread badge and a poll watermark. `--filter` selects the stream: `all` (default), `jobs`, `mentions`, `my_posts`, `my_posts_comments`, `my_posts_reactions`, `my_posts_reposts`. | proven |\n| `curviate notification delete \u003Ccard_urn>` | Delete one of your own notification cards. Idempotent, cannot be undone. | proven |\n| `curviate notification show-less \u003Ccard_urn>` | Apply \"show less like this\" to a card's source. For network-activity cards this removes the card, the same as delete. Idempotent, cannot be undone. | proven |\n\nThe feed and the notification stream are the two cheapest sources of a genuinely current thing to\nengage with: reach for them before searching for something to react to.\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`, `--json`, `--preview`, `--profile`, `--timeout`, `--verbose`.\n\n| Command | Arguments | Flags |\n|---|---|---|\n| `curviate post get` | `POSTID` | `--fields`, `--limit`, `--cursor` |\n| `curviate post create` | `TEXT` | `--attach` |\n| `curviate post react` | `POSTID` `REACTION` | `-reaction, --reactionAlias`, `--as-organization` |\n| `curviate post reactions` | `POSTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate post delete` | `POSTID` | `--fields` |\n| `curviate post unreact` | `POSTID` `REACTION` | `--fields` |\n| `curviate post saved` | *(none)* | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate post save` | `POSTID` | `--fields` |\n| `curviate post unsave` | `POSTID` | `--fields` |\n| `curviate post user-posts` | `USERID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate post user-reactions` | `USERID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate comment list` | `POSTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate comment add` | `POSTID` `TEXT` | `--fields`, `--attach` |\n| `curviate comment reply` | `POSTID` `COMMENTID` `TEXT` | `--fields`, `--attach` |\n| `curviate comment edit` | `POSTID` `COMMENTID` `TEXT` | `--fields` |\n| `curviate comment delete` | `POSTID` `COMMENTID` | `--fields` |\n| `curviate comment replies` | `POSTID` `COMMENTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate comment react` | `POSTID` `COMMENTID` `REACTION` | `--fields` |\n| `curviate comment reactions` | `POSTID` `COMMENTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate comment unreact` | `POSTID` `COMMENTID` `REACTION` | `--fields` |\n| `curviate comment user` | `USERID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` |\n| `curviate feed home` | *(none)* | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay`, `--sort` |\n| `curviate notification list` | *(none)* | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay`, `--filter` |\n| `curviate notification delete` | `CARDURN` | `--fields` |\n| `curviate notification show-less` | `CARDURN` | `--fields` |\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: an uppercase reaction value, a malformed post id, more than one attachment on a comment. | Fix the invocation. Never retry unchanged. |\n| `4` | Not found, usually a wrong identifier *form* rather than a missing post. | Re-derive the id before concluding the post is gone. |\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 (pass `--beta` for one call, or a human enables it in Settings). | 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 hiccup, or 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| `8` | Account or connection state. Read `error.code`. | `LINKEDIN_OPERATION_NOT_SUPPORTED` is permanent and never retryable; a session error needs a reconnect. |\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; nothing was posted.** `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","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-imp-curviate-engage",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill curviate-engage",{"tool":48,"command":49},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill curviate-engage",{"tool":51,"command":52},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill curviate-engage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-curviate-engage\u002FSKILL.md",true,[],[57,64,72,79,86,93],{"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},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\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":15,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]