Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage 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).
Manage 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).
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Manage ongoing LinkedIn conversations from a central Google Sheet CRM. Read threads, draft context-aware replies, send messages, and keep the sheet updated — all from one skill.
Before doing anything: Sheet ID — Confirm the CRM sheet ID (from linkedin-dm setup). Default: 1eEZDGcr1dIbSC782mNkxvD7pVrF8rOFySWCVZ1RXkhM, tab: Sheet1 (or Outreach if renamed). gog auth — Run gog auth list. If no tokens: see gog auth setup below. Browser — Open the openclaw browser profile and confirm LinkedIn is logged in. Navigate to /feed/ first. Mode — Identify which mode the user wants (see Modes).
The CRM sheet uses these columns (A–P): ColFieldNotesADate SentISO dateBPerson NameFull nameCRole / TitleDCompanyELinkedIn URLProfile URLFRelationship HookHook used in openerGOpener SentMessage 1 textHPitch SentMessage 2 textICampaignBatch labelJStatusCurrent pipeline stageKNotesContext and historyLLast UpdatedISO timestampMLast Reply DateWhen they last repliedNLast Reply (preview)First 200 chars of their last replyOConversation LogFull thread (see format below)PNext ActionWhat to do next (agent or human) Status values: Sent → Replied → Call Scheduled → Demo Done → Follow Up Sent → No Response → Closed Won → Closed Lost Conversation Log format (column O): [2026-02-13 17:05 SENT] Hey Rishabh, we both had stints at CRED... [2026-02-13 17:05 SENT] I'm building an AI calling agent... [2026-02-15 09:30 RECEIVED] Hey! Sounds interesting, tell me more. [2026-02-15 09:45 SENT] Happy to show you a live demo — are you free Thursday? If columns M–P don't exist yet, add them first: gog sheets update <SHEET_ID> "Sheet1!M1:P1" \ --values-json '[["Last Reply Date","Last Reply (preview)","Conversation Log","Next Action"]]' \ --input USER_ENTERED
User says: "Mark Rishabh as Replied" or "Rishabh got back to me, he's interested" Find the row — Search the sheet for the person: gog sheets get <SHEET_ID> "Sheet1!A:P" --json Match by name (col B) or LinkedIn URL (col E). Get the row number. Update status (col J) and last updated (col L): gog sheets update <SHEET_ID> "Sheet1!J<ROW>:L<ROW>" \ --values-json '[["Replied","","<ISO_TIMESTAMP>"]]' \ --input USER_ENTERED If the user provides reply content, also update: Col M: Last Reply Date Col N: Last Reply preview (first 200 chars) Col O: Append to Conversation Log Col P: Next Action (what should happen next) Confirm update to user.
User says: "Follow up with Rishabh" or "Send a follow-up to everyone who replied" Step 1 — Load the person's data from sheet gog sheets get <SHEET_ID> "Sheet1!A:P" --json Find their row. Load: Name, Company, Role, LinkedIn URL, Opener Sent, Pitch Sent, Status, Notes, Conversation Log, Next Action. Step 2 — Navigate to their LinkedIn profile Always go to feed first (anti-detection): https://www.linkedin.com/feed/ Wait 2–4 seconds. Then navigate to their profile URL (col E). Step 3 — Open message thread and read conversation Click the Message button on their profile. Wait for the conversation bubble to load. Scrape the full thread with JavaScript: const events = Array.from(document.querySelectorAll('.msg-s-message-list__event')); const messages = []; events.forEach(el => { const groups = el.querySelectorAll('.msg-s-event-listitem'); groups.forEach(g => { const nameEl = g.closest('.msg-s-message-group')?.querySelector('.msg-s-message-group__profile-link'); const bodyEl = g.querySelector('.msg-s-event-listitem__body'); const timeEl = g.closest('.msg-s-message-group')?.querySelector('.msg-s-message-group__timestamp'); if (bodyEl?.textContent?.trim()) { messages.push({ sender: nameEl?.textContent?.trim() || 'unknown', time: timeEl?.textContent?.trim() || '', text: bodyEl.textContent.trim() }); } }); }); return JSON.stringify(messages); If the thread is empty or not loading, scroll up in the conversation bubble to load older messages. Step 4 — Analyse the conversation With the full thread loaded + their profile data, determine: What did they say last? — Identify the most recent message from them. What's the intent? — Interested / wants more info / asked a question / cold / objection / not interested. What's the right next message? — See Response Playbook below. Tone — Mirror their tone (casual vs formal, brief vs detailed). Step 5 — Draft the follow-up Write a response that: Directly addresses what they said last Doesn't re-pitch unless they asked for it Moves toward a specific action (demo, call, intro, forward to team) Is brief — 2–4 sentences max Feels human, not templated Show the draft to the user and ask for approval before sending: Draft reply to [Name]: [message] Send this? (y / edit / skip) Step 6 — Send the message Same JS evaluate method as linkedin-dm: const active = document.querySelector('.msg-overlay-conversation-bubble--is-active .msg-form__contenteditable'); if (active) { active.focus(); document.execCommand('insertText', false, '<message>'); } Then find and click Send. Step 7 — Update the sheet After sending: gog sheets update <SHEET_ID> "Sheet1!J<ROW>:P<ROW>" \ --values-json '[["<new_status>","<last_reply_date>","<last_reply_preview>","<updated_conversation_log>","<next_action>","<ISO_TIMESTAMP>"]]' \ --input USER_ENTERED
User says: "Who needs a follow-up?" or "Check my outreach" Load all rows from the sheet. Filter by status and time: Sent older than 3 days → candidate for "No Response" or gentle follow-up Replied → needs a response Follow Up Sent older than 5 days → consider "No Response" Call Scheduled → check if call happened, update status Present a table of candidates: Name Status Last Updated Suggested Action Rishabh Nayan Replied 2026-02-14 Reply to their message Shorya Saini Sent 2026-02-10 Follow-up nudge (4 days) Shantam Mohata Sent 2026-02-13 Too soon (today) User picks who to action, then enter Mode 2 for each.
Use these as a guide — always adapt to the actual conversation: They saidIntentYour move"Sounds interesting, tell me more"CuriousShort explanation + offer a specific demo slot"How does it work?"Exploring2-line description + invite to a 15-min call"We already use [X]"ObjectionAcknowledge, explain differentiation, offer demo"Send me more details"Soft interestShare a Loom/deck/link + follow up in 2 days"Not relevant right now"Soft noRespect it, leave door open: "No worries, I'll ping you in a few months""Who else is using it?"Trust-buildingShare a relevant use case, offer intro to a user[No reply in 4 days]SilenceLight nudge: "Hey [Name], just checking — any thoughts?"[No reply in 8 days]ColdOne final message, then mark No Response
Same rules as linkedin-dm: Always go to /feed/ before navigating to a profile Wait 2–4 seconds after loading feed Max 15–20 messages per session (combined sends across follow-ups) Space out follow-ups: don't ping multiple people in rapid succession Natural delays between typing and sending (1–2 seconds)
If gog auth list returns empty, the user needs to set up Google OAuth credentials: Go to console.cloud.google.com Create a project (or select existing) Enable Google Sheets API (APIs & Services → Library) Create OAuth credentials: APIs & Services → Credentials → Create → OAuth client ID → Desktop App Download client_secret_<id>.json Run: gog auth credentials set /path/to/client_secret.json gog auth add your@gmail.com --services sheets A browser window will open — log in and grant access Verify: gog auth list Fallback (no gog): All sheet reads/writes can be done manually via browser — open the sheet in the openclaw browser and update cells directly. Less automated but functional.
Max 15–20 follow-up messages per session Log every send immediately to sheet (don't batch) If gog is unavailable, log to local linkedin_followup_log.json and sync to sheet next session
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.