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

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:

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`

Reaction vocabularies: write is not read

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`

• 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`

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

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.

Exit codes to branch on here