curviate-engage

# Curviate: posts, comments, reactions, feed Engagement is the cheapest way to be visible, and every write here is public and attributable. Two vocabularies and three identifier forms cause most failures; both are below. Command surface established against CLI `0.33.0`. ## Before any command ```bash npm install -g @curviate/cli && curviate --version # needs Node 18 or newer curviate login --api-key <key> # or export CURVIATE_API_KEY curviate account list --json # the acc_id for --account ``` - **Credentials resolve flag > environment > stored profile** (`CURVIATE_API_KEY`, `CURVIATE_BASE_URL`, `CURVIATE_ACCOUNT`). - **`--profile <name>` picks the stored credential set; `--account <acc_id>` picks which connected LinkedIn account posts, comments or reacts.** Name it explicitly on every write: a comment from the wrong account is public and permanent. - **`--preview` before every write.** It renders the resolved request without sending. On a read command it is refused with exit `2`. - **`--json` on anything you parse**; **`--fields a,b,c`** to project; **`--verbose`** when a slim response looks suspiciously empty. - **Put global flags at the end of the command.** - **Branch on the exit code, never on prose.** See the table at the end. - These are not retrieval-mode commands: `--mode`/`--max-age` are refused here with `unknown flag`, exit `2` (see `curviate-profile` for the four commands that do accept them). ### Text input Post and comment text is a positional argument, and `-` reads stdin. **Use a quoted heredoc**: the quoted delimiter disables every shell expansion, so apostrophes, accents, `$` and backticks survive intact: ```bash cat <<'EOF' | curviate post create - --preview Line one. Line two. EOF ``` ## Identifiers A post id comes in three forms and the commands are not uniformly forgiving: - The **numeric activity id** (`7459869580333576193`) is the canonical form. - `urn:li:activity:<N>` works. - A **full share URL** is accepted and the id extracted from it. If a command ever rejects one, extract it yourself: `POST_ID=$(echo "<share_url>" | grep -oP 'activity[-/]\K\d+')`. - Some builds have rejected the bare numeric id at write time on `post react`, `comment add` and `comment list` while `--preview` on the same command rendered fine. If you hit that, pass the base64 `id` from whatever `post get`, `post create` or list response you already hold: no extra fetch needed. **In every `comment` command, `<post_id>` is the original post's id, never the comment's.** `<comment_id>` comes from `comment list <post_id>` as `items[].id`. **`post get` answers with `social_id` (a URN); the numeric id you passed is not echoed back.** ## `post` | Command | What it does | Confidence | |---|---|---| | `curviate post get <post_id>` | One post. Adds `is_repost`, `reposted_by`, `user_reacted` and a richer `author` (headline, slug) over what a list carries. | proven | | `curviate post create "<text>"` | Publish a post. `--attach` is repeatable for images and takes jpg, png, gif, mp4 or pdf; a single PDF produces a document post. | proven | | `curviate post react <post_id> <reaction>` | React to a post. `--as-organization <id>` reacts as a company page you administer. Duplicate reactions succeed silently. | proven | | `curviate post unreact <post_id> <reaction>` | Remove your reaction. | proven | | `curviate post reactions <post_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 | | `curviate post delete <post_id>` | Delete a post you own. | proven | | `curviate post save <post_id>` | Save to your private bookmark list. Never notifies the author, never visible to anyone else. Idempotent. | proven | | `curviate post unsave <post_id>` | Remove from the bookmark list. Idempotent. | proven | | `curviate post saved` | Your saved posts, newest first. Each item is a preview with the snippet capped at 140 characters. | proven | | `curviate post user-posts <id\|me>` | A member's own posts. Same data as `profile <id> --posts`. | proven | | `curviate post user-reactions <id\|me>` | A member's own reactions. Same data as `profile <id> --reactions`. | proven | ### Reaction vocabularies: write is not read | Write (`post react`, `comment react`, lowercase) | Read (`value`, `user_reacted`) | |---|---| | `like` | `LIKE` (confirmed pairing) | | `celebrate` | `PRAISE` (confirmed pairing) | | `insightful` | `INTEREST` (confirmed pairing) | | `support` | `APPRECIATION` (pairing unconfirmed) | | `love` | `EMPATHY` (pairing unconfirmed) | | `funny` | `ENTERTAINMENT` (pairing unconfirmed) | **Sending an uppercase read value as a write returns `INVALID_REQUEST`, exit `2`.** Always write lowercase. Read-side casing has been observed to vary, so **compare reaction values case-insensitively** when parsing `post reactions`, `comment reactions`, or `user_reacted`. ### Traps - **`post reactions` returns `cursor: null` while more reactions remain.** A single page is not the reaction list. Use `--all`, and check the final line for `{"object": "stream_truncated", …, "has_more": true}`. - **Check `user_reacted` on `post get` before reacting**: a duplicate reaction succeeds silently and tells you nothing. - **A very recent create or delete can take minutes to appear in `post user-posts`** (LinkedIn-side indexing). `post get <post_id>` reflects it immediately. - **The post list carries no `is_repost` field.** Detect a repost by comparing the item's author name against the member you queried, or call `post get <post_id> --fields is_repost,reposted_by`. On a repost, `author` is the original creator and `reposted_by` is the sharer. - **A company reactor carries no `network_distance`**: the key is absent, not null. Treat `author.type == "COMPANY"` as its own signal rather than as missing data. - A list item already carries `id`, `parsed_datetime`, full `text`, `reaction_counter`, `comment_counter`, `repost_counter`, `impressions_counter`, `author` and `attachments`, so most "read a post" questions need no `post get` at all. ## `comment` | Command | What it does | Confidence | |---|---|---| | `curviate comment list <post_id>` | Top-level comments. Returns `id` and `social_id` (chain into `comment react`/`reply`), `reply_counter` (above 0 means nested replies exist) and `author.profile_url`. | proven | | `curviate comment add <post_id> "<text>"` | Comment on a post. Returns the new comment's id. `--attach` takes at most one image. | proven | | `curviate comment reply <post_id> <comment_id> "<text>"` | Reply to a specific comment. | proven | | `curviate comment edit <post_id> <comment_id> "<text>"` | Edit your own comment. | proven | | `curviate comment delete <post_id> <comment_id>` | Delete your own comment. | proven | | `curviate comment replies <post_id> <comment_id>` | Replies to one comment. | proven | | `curviate comment react <post_id> <comment_id> <reaction>` | React to a specific comment (not the post). Same lowercase write vocabulary. | proven | | `curviate comment unreact <post_id> <comment_id> <reaction>` | Remove that reaction. | proven | | `curviate comment reactions <post_id> <comment_id>` | Reactions on one comment. | proven | | `curviate comment user <id\|me>` | Comments a member authored. Same data as `profile <id> --comments`; each carries `post_id` for context. | proven | - **`comment list` returns only what is visible to you.** The post's own `comment_counter` is always greater than or equal to the items returned, so a mismatch is not a bug. - **`parsed_datetime` is always null on a comment**: use `date` for the ISO timestamp. - **To check whether you already commented on a post, match on `parent_post.share_url`, never on ids.** `parent_post.id` is base64 of a *two*-element array (`[comment_activity, post_activity]`) while a post's own `id` is a one-element array, so an id comparison is always false. If you need the id, decode and take element `[1]`. - **A very recent add or delete can take minutes to appear in `comment list`.** ## `feed` and `notification` | Command | What it does | Confidence | |---|---|---| | `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 | | `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 | | `curviate notification delete <card_urn>` | Delete one of your own notification cards. Idempotent, cannot be undone. | proven | | `curviate notification show-less <card_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 | The feed and the notification stream are the two cheapest sources of a genuinely current thing to engage with: reach for them before searching for something to react to. ## Full command surface <!-- generated: command surface, CLI 0.33.0 --> Read from the CLI's own `--help` at version 0.33.0. Descriptions, traps and confidence tags elsewhere in this skill are hand-written and carry the version they were established against. Every command below that takes flags at all also accepts `--account`, `--api-key`, `--base-url`, `--beta`, `--json`, `--preview`, `--profile`, `--timeout`, `--verbose`. | Command | Arguments | Flags | |---|---|---| | `curviate post get` | `POSTID` | `--fields`, `--limit`, `--cursor` | | `curviate post create` | `TEXT` | `--attach` | | `curviate post react` | `POSTID` `REACTION` | `-reaction, --reactionAlias`, `--as-organization` | | `curviate post reactions` | `POSTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` | | `curviate post delete` | `POSTID` | `--fields` | | `curviate post unreact` | `POSTID` `REACTION` | `--fields` | | `curviate post saved` | *(none)* | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` | | `curviate post save` | `POSTID` | `--fields` | | `curviate post unsave` | `POSTID` | `--fields` | | `curviate post user-posts` | `USERID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` | | `curviate post user-reactions` | `USERID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` | | `curviate comment list` | `POSTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` | | `curviate comment add` | `POSTID` `TEXT` | `--fields`, `--attach` | | `curviate comment reply` | `POSTID` `COMMENTID` `TEXT` | `--fields`, `--attach` | | `curviate comment edit` | `POSTID` `COMMENTID` `TEXT` | `--fields` | | `curviate comment delete` | `POSTID` `COMMENTID` | `--fields` | | `curviate comment replies` | `POSTID` `COMMENTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` | | `curviate comment react` | `POSTID` `COMMENTID` `REACTION` | `--fields` | | `curviate comment reactions` | `POSTID` `COMMENTID` | `--fields`, `--limit`, `--cursor`, `--all`, `--max-pages`, `--page-delay` | | `curviate comment unreact` | `POSTID` `COMMENTID` `REACTION` | `--fields` |