outbound-agent-skills
Solid29 Claude Skills for an AI agent that runs B2B outbound on LinkedIn and email. Each rule carries the number from a live engine.
Bundles
Everything this plugin ships — skills, agents, commands, hooks, and MCP servers it bundles.
Skills (26)
first-touch-booking-link-once
Limits the calendar booking link to one appearance per thread, repeated only when the person returns to scheduling. Use when writing replies or follow-ups that invite to a call, and when reviewing a thread before sending.
first-touch-message-after-accept
Writes the first LinkedIn message after an invite is accepted, choosing between two families based on whether the invite note was actually delivered, and makes the second message add something new. Use when drafting post-accept messages or follow-ups in a connection sequence.
first-touch-no-negation
Rewrites outward-facing text (messages, emails, offer pages, posts) as statements, removing negations, named objections and comparisons with the reader's current tool. Use as a pass on any outbound copy or proposal before it goes out.
learning-ab-split-key
Assigns outreach A/B test arms by lead with a key whose period is smaller than a batch, locks the arm for the whole thread, and sizes the test before starting. Use when designing, auditing or reading an A/B test on outreach copy or sequences.
learning-check-what-the-human-received
Designs monitoring checks for an outreach engine that measure what the recipient actually got, after the last step between you and them, and gives every check a class, a way to go green and a quarantine. Use when adding, reviewing or trusting any automated check, alert or dashboard metric.
learning-decision-needs-why
Records every outreach change (copy, signal, segment, limit, offer, process) with three required fields, why, expected and rejected, and logs rejected lead candidates at the moment of selection. Use whenever you change a campaign, build a batch, or retire a message variant.
learning-weekly-readout
Runs the weekly outbound review, computing reply rate by signal, segment and message variant, refusing to decide on noise, and applying at most one change per week. Use once a week or when asked "how did the week go" or "what should we change" about an outreach campaign.
meetings-pre-call-brief
Build a one-screen brief before an external meeting from every calendar, inbox, call recorder and CRM record. Use the evening before, shortly before a call, or when asked "who is this" or "prep me for the call with X".
meetings-reminder-hour-before
One hour before a meeting with a prospect, confirm the meeting is live, find the channel the conversation already uses, and send one short reminder there. Use from a calendar watcher or when asked to remind a prospect about a call.
replies-48h-sla
Keep every thread where the ball is on our side answered within 48 hours. Use at the start of every reply-handling run and every daily summary, to build and clear the overdue list.
replies-discovery-not-pitch
Run a live conversation with a prospect as questions about their numbers, not as a pitch. Use when replying inside an active thread (LinkedIn, messenger, email) after the prospect has answered.
replies-follow-up-after-silence
Write the touch that goes out after a prospect stays silent on two messages. Use when planning or writing follow-ups 3 and 4 of an outbound sequence, and whenever a draft contains a breakup line.
Show all 26 bundled skills Showing all 26 bundled skills
replies-triage
Classify an inbound reply to outbound and decide who answers it. Use when a lead replies on LinkedIn, email or any channel and an agent is about to answer without a human.
sending-limits-from-vendor-docs
Sets limits, pauses, caps and thresholds for outreach sending from provider documentation, market tools' methodology and your own measurement, instead of from intuition. Use before writing any number into sending logic, such as a daily cap, a cooldown after an error, or a warm-up ramp.
sending-protect-real-profiles
Keeps sending-mechanics experiments (invite notes, likes before invites, volume, new action types, new channels) off real people's LinkedIn profiles and runs them on disposable profiles first. Use when planning any outreach experiment or choosing which profiles a new sending behavior rolls out to.
sending-refusal-costs-an-attempt
Handles LinkedIn invitation refusals (temporary limit errors) as a cost of one attempt instead of a lost day, and counts the weekly invite cap yourself. Use when designing retry, backoff, strike or cooldown logic for any sending profile.
sending-spread-the-day
Paces cold LinkedIn and email touches evenly across the sender's working window instead of firing them in a burst. Use when building or reviewing a sending queue, a scheduler, or daily limits for any outreach profile.
targeting-exclude-existing-customers
Builds the exclusion list from the full export of current accounts before any campaign sends, and refreshes it for every batch. Use when starting outreach on behalf of a company, or before queueing a new batch in a market where the company already has customers.
targeting-fact-with-source
Enforces one verifiable, sourced fact per first touch and drops leads without one. Use when personalizing a first message, invite note or email, or when reviewing a batch before it is queued.
targeting-named-person-not-inbox
Treats role mailboxes (hr@, info@, sales@, careers@) as dead ends and finds named decision owners with work emails and phones. Use when a lead or referral points to a shared inbox, or when building a contact list for an account.
targeting-reason-can-be-context
Chooses between an event (funding, hiring, headcount growth, new role) and company context as the reason to write, and accepts "no event" as a valid result. Use when picking the reason for each lead in a batch, especially for small companies and solo buyers.
targeting-sales-hiring-signal
Decides whether a job post is a valid reason to write to a company. Use when sourcing leads from hiring signals or when a draft opens with "saw you're hiring".
writing-claim-needs-ground
Makes every claim in a message travel with the fact it rests on, and removes guesses, unchecked causes and invented decisions. Use before sending any message to a prospect, client or teammate that states a fact, a cause, a status or someone's decision.
writing-paragraphs-not-walls
Formats a LinkedIn message, InMail, invite note or email into short paragraphs separated by blank lines, without changing a word. Use as the last formatting step before any outreach text is queued or sent.
writing-stamp-is-frequency
Judges a batch of outreach messages by how often phrases repeat, not by a ban list of words. Use before queueing or sending any batch of cold messages, follow-ups or invite notes written in one pass.
writing-weekday-matches-date
Verifies that a weekday written next to a date matches the calendar before a message is sent. Use on any outgoing message, email or invite that proposes, confirms or moves a meeting with both a weekday and a date.
Quality Score: 69/100
Details
- Author
- dostrovcev
- Repository
- dostrovcev/outbound-agent-skills
- Created
- 1 weeks ago
- Last Updated
- 1 weeks ago
- Language
- Python
- License
- MIT