Linkedin Buying Signal

Before installing or running this skill, consider the following: - Ask the author to clearly declare required credentials and how to supply them (Apify token, and any CRM/Notion/Slack/email credentials) as environment variables or documented inputs — do not paste secrets into free-text prompts. - Confirm how the Apify actors obtain LinkedIn/profile data: do they require a LinkedIn session cookie or authenticated access? If so, supplying such credentials grants broad access to your LinkedIn account; avoid sharing account cookies unless you fully trust and audit the actor. - Verify legal and privacy implications: the skill scrapes personal profiles and emails. Ensure compliance with LinkedIn's Terms of Service and local privacy laws (e.g., GDPR) before collecting/transmitting PII. - Request details on the exact Apify actors used (versions, code or run logs) and test with a very small, controlled dataset first (sandbox run, dummy inputs) to confirm behavior and outputs. - If you plan to push data to CRMs or email prospects, require that the skill explicitly list what credentials it needs and how it will store/transmit them; prefer short-lived tokens or user-controlled webhooks. - If you cannot obtain satisfactory answers about credential handling, data sources, or legal compliance, do not run the skill with real credentials or real personal data. Confidence note: assessment is medium because many issues could be innocuous documentation omissions (e.g., author expects apify_token as an input rather than an env var). However, the combination of unexplained credential needs, personal-data scraping, and unspecified integrations is enough to warrant caution.