curviate-profile

Topics in the source

• Curviate: profiles, companies, and filter ids
• Before any command
• --profile and --account are different questions
• Retrieval mode: --mode and --max-age
• profile: members
• Traps
• company: company pages
• search parameters: turning words into filter ids

Profiles are the entry point for almost every LinkedIn workflow: you resolve a person or a company, then act. This skill covers that resolution, the company page surface, the parameter lookup every structured search depends on, and the account plumbing underneath all of it. Command surface established against CLI 0.33.0. Resolve the binary first. If curviate --version fails, install it. Do not substitute a raw HTTP call for a command you could not find; the command surface is the contract. Credentials resolve flag > environment > stored profile. CURVIATEAPIKEY, CURVIATEBASEURL and CURVIATEACCOUNT are the right path for a scripted run: the key stays out of argv, out of ps, and out of shell history. --json on anything you parse. It is already the default when stdout is not a terminal; ask for it explicitly when a human might also be watching. --preview before every write. It renders the resolved request without sending it. On a read command it is refused with exit 2. --fields a,b,c to project. Profile responses carry 18 or more fields; projecting cuts most of that away. --verbose when a slim response looks suspiciously empty. An empty slim field is not proof the data does not exist;

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