reach-check
Skill2 starsChanged 57 days agoMITView on GitHub
Gatekeeper — confirms each lead can actually be reached (resolvable LinkedIn profile, connection degree, email route through Lemlist) and completes missing fields from Pastel and public pages only. Use for "find their email", incomplete leads, or just before campaign-launch.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- buying-committeeSkill
- call-readySkill
- campaign-launchSkill
- command-centerSkill
- competitor-watchSkill
- fit-checkSkill
- human-voiceSkill
- intent-radarSkill
- market-mapSkill
- message-writerSkill
- morning-briefSkill
- nudgeSkill
- outbound-briefSkill
- post-studioSkill
- priority-rankSkill
- reply-deskSkill
- social-warmupSkill
- what-worksSkill
- why-nowSkill
The file
Files
Reach check — Gatekeeper
House rules: ../command-center/shared/house-rules.md · Pastel tools: ../command-center/shared/pastel-tools.md
LinkedIn is the main channel, so the question is less "do we have their email?" than "can Pastel reach this profile?".
Steps
- Profile:
pastel_get_detailsfor each lead. Without a resolvable LinkedIn profile Pastel can't visit, invite, or message them → routeno-route. - Degree: already connected → the sequence can skip the invitation and open with a message. Note it on the lead card.
- Missing fields: fill company domain and current title from the company website or LinkedIn company page, and cite the page.
- Email: Pastel doesn't look up email addresses. If
outbound-brief.mdallows email, route the leadlemlist—campaign-launchpushes it to Lemlist, which finds the address itself. Otherwise the field stays[missing: email]. - Someone caught twice (by two agents, say) keeps a single lead card that lists both events.
Output
# Reach check — [date]
Checked: N · LinkedIn: n (connected: n) · Lemlist: n · No route: n
| Person | Company | Profile | Connected | Domain | Email | Route | Source |Routes: linkedin · linkedin-connected · lemlist · no-route. Everyone with a route moves on to priority-rank.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

