LinkedIn Follow-up
v1.0.0Manage LinkedIn outreach leads from Google Sheets — search by name, read live conversation threads, update status, and send contextual follow-up messages. Use after linkedin-dm to move leads through the pipeline (Sent → Replied → Call Scheduled → Demo Done → Closed).
⭐ 0· 637·2 current·2 all-time
by@10madh
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (LinkedIn follow-ups via Google Sheets) aligns with the actions described: using the 'gog' CLI to read/write Sheets and automating an 'openclaw' browser to read/send LinkedIn messages. Requiring the 'gog' binary and a browser profile is coherent. However, the skill ships a default hard-coded Sheet ID and assumes a specific logged-in user name ('Madhur'/'Madhur' matching) which is not justified by the description and is inappropriate for a generic skill.
Instruction Scope
Instructions explicitly scrape full LinkedIn conversation threads, take screenshots, and send messages from the logged-in LinkedIn session — these are legitimate for this purpose but involve sensitive personal data and active actions. Concerningly, the instructions include an 'anti-detection' step (always go to the feed first) that suggests stealthy behavior, and a hard-coded sender name ('Madhur') to classify SENT vs RECEIVED messages, which will misclassify other users and indicates the instructions were tailored to a single person rather than generalized. The skill also instructs appending full conversation logs into a sheet cell (potentially storing private content).
Install Mechanism
This is an instruction-only skill with no install spec or remote downloads, so it does not write code to disk or fetch arbitrary archives. That is the lower-risk option for installation mechanics.
Credentials
The skill declares no required environment variables or credentials and instead uses the 'gog' CLI and the agent's browser profile for auth — reasonable for Sheets and browser automation. It does instruct using 'gog auth add your@gmail.com --services sheets --force-consent', which implies adding Google auth tokens interactively; this is expected but users should be aware that their Google Sheets content and LinkedIn session will be accessed. No unrelated credentials are requested.
Persistence & Privilege
The skill does not request always:true or other elevated installation privileges. It relies on the agent's browser profile and the gog CLI at invocation time. There is no evidence it modifies other skills or system-wide settings.
What to consider before installing
This skill broadly does what it claims (reads LinkedIn messages, drafts replies, and updates a Google Sheet), but several red flags mean you should be cautious before installing:
- Hard-coded values: The SKILL.md assumes a specific Sheet ID and that the logged-in LinkedIn user is named 'Madhur' when classifying sent vs received messages — if your account/name differs the skill will misclassify messages and could behave incorrectly. Ask the author to make sender detection dynamic (use the logged-in user's display name or profile id).
- Stealthy behavior: The instructions include an 'anti-detection' step (navigate to /feed first). That suggests the author intended to make automated actions less obvious. Decide whether you are comfortable with automation that actively tries to be stealthy and confirm this complies with LinkedIn's terms and your organizational policy.
- Sensitive data handling: The skill scrapes full message threads and writes them into Google Sheets. If those sheets are shared or accessible, private conversations will be stored there. Limit sheet sharing, review access controls, and consider storing only summaries or redacted snippets.
- Sending messages: While the skill shows a draft and asks for 'y / edit / skip', verify in a safe test that it truly requires explicit user approval before sending. If you want more safety, require manual approval for every send or disable automatic sends.
- Authentication: The skill expects you to authenticate gog to access Sheets. Only grant the minimum scopes required and revoke tokens after testing if you don't intend long-term usage.
What would reduce my concern: removing hard-coded IDs/names, making sender detection dynamic, removing 'anti-detection' guidance, storing minimal data in Sheets, and having a stricter manual approval step before any message is sent. If you don't trust the unknown publisher, test this in a throwaway account and sheet first, or ask the author for source attribution and an updated SKILL.md that addresses the issues above.Like a lobster shell, security has layers — review code before you run it.
latestvk97c330wzzzeedcedkf1ebb0s581240f
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔁 Clawdis
Binsgog