curviate-engage

Topics in the source

• Curviate: posts, comments, reactions, feed
• Before any command
• Text input
• Identifiers
• post
• Reaction vocabularies: write is not read
• Traps
• comment

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. Credentials resolve flag > environment > stored profile (CURVIATEAPIKEY, CURVIATEBASEURL, CURVIATEACCOUNT). --profile picks the stored credential set; --account 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). Post and comment text is a positional argument, and - reads stdin. Use a quoted heredoc: the quoted delimiter disables every shell expansion,

This is an excerpt. Refer to the complete source and its current requirements.