From exec-recruiter
Walk through Phase 3 send for a single greenlit packet. Triggers on "send X", "Phase 3 X", "/send X", "fire X", "let's send X", or "ready to send X". Opens the right LinkedIn surface for each channel (Connect+Note dialog, DM thread, InMail compose), types the drafted message into the field, and stops with the cursor positioned for the user to click Send. Never sends autonomously. Walks the user through each channel in priority order; after each user-confirmed send, updates the dashboard from "drafted" to "pending" with sendDate today.
How this skill is triggered — by the user, by Claude, or both
Slash command
/exec-recruiter:phase-3-sendThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Walk the user through Phase 3 send for one role at a time. Position the browser, type the message, stop. The user clicks Send.
Walk the user through Phase 3 send for one role at a time. Position the browser, type the message, stop. The user clicks Send.
The user says: "send X", "Phase 3 X", "/send X", "fire X", "let's send X", "ready to send X". X is a slug or company name.
No skill in this plugin sends a LinkedIn message, an email, or an application autonomously. This skill ALWAYS:
If the user types send or next after seeing the typed message, the skill moves to the next channel. If the user wants to edit, the skill waits.
The user names a role. Look up:
outreach/{slug}/outreach.md for the draftsoutreach/{slug}/jd.md for the JD contextIf the packet's status is not "drafted", confirm with the user before proceeding. (E.g., already-sent packets shouldn't be re-fired.)
Echo back the drafts and the channel plan. Ask the user to confirm:
If there's an application URL, navigate to it FIRST. The application can submit while the user is reviewing/sending Connect+Notes - parallel work.
For Workable / Teamtailor / Greenhouse / Lever / Ashby / company-careers:
mcp__Claude_in_Chrome__file_upload with the file input ref)outreach.md cover-letter angle)For each contact in the channel plan, in order:
https://www.linkedin.com/in/{slug}/)More
b. Click Connect
c. In the dialog, click Add a note
d. Click into the textarea
e. Type the Connect+Note (Premium = 300 char, standard = 280 char)
f. Confirm char count is within limit
g. STOP. Tell user "Send is active. Click it when ready."InMail is the channel of last resort. Before any InMail send:
channels.inmail_credits)If approved:
After each user-confirmed send:
sent entry to outreach/{slug}/outreach.md under "Send log" with timestamp, channel, contact namestatus: "drafted" to status: "pending"sendDate: "{today_yyyy_mm_dd}"channels array with what was actually sentsendName to a short identifier like "alan-and-dev" or "kanav"note field with the send logAfter all channels for the role are sent, calculate the follow-up dates per ${CLAUDE_PLUGIN_ROOT}/config/follow-up.yaml:
Append these to the role's outreach.md as a "Follow-up watch" section.
Output a tight summary in chat:
Confirm with the user one last time:
The user's send X command is greenlight for the workflow but each individual click stays the user's. Type and stop.
npx claudepluginhub bgolubovski/exec-recruiter --plugin exec-recruiterProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.