outreach
Skill617 starsChanged 10 months agoMITView on GitHub
Send messages to people on chat platforms (Discord, Slack, Telegram, Signal) on the user's behalf or your own initiative
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Before sending, check you haven't already said substantially the same thing recently — repetition when nothing changed reads as nagging.
- Very specific: line 24
When in doubt about whether the user would want a message sent on their behalf, ask them first.
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Outreach
Reaching out is what separates a companion from a tool — and it spends the scarcest resource there is: someone's attention. Earn the interruption.
- A message must clear the bar: new, wanted, timely. When nothing clears it, choosing silence is a completed act, not a failure to act.
- Before sending, check you haven't already said substantially the same thing recently — repetition when nothing changed reads as nagging.
- Messages to platforms reach real people in real rooms. Match the room's register; keep it brief; personal matters belong in private channels, never groups.
- When in doubt about whether the user would want a message sent on their
behalf, ask them first. The always-available path for reaching the user
themselves is
queue_user_message(the outbox). Use it directly for an immediate note to the user; usemanage_scheduleonly when the user asks for a future time, delay, recurrence, or reminder. Do not invent a delay to make a note feel more independent.
Other versions18 projects use a version of this.
Word for word · 1
- QuixiAI/Hexis★ 617100% same
Edited · 0
None found.
Wrote their own version · 17
- andrew-shwetzer/career-ops-plugin★ 501same name
- andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-★ 500same name
- guaardvark/guaardvark★ 283same name
- ShawhinT/non-coding-skills★ 40same name
- saksham10arora-dotcom/everything-claude-codex★ 24same name
- alejopijuan/Claude-Code-Agency-Co-Founder★ 19same name
- Abhipaddy8/outreach-agent★ 17same name
- emelia-io/claude-outreach★ 17same name
- julienamorgan/signal-prospecting-kit★ 16same name
- FakharEAli/book-skills★ 3same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use apply, evaluate and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
proficientlyjobsSkillapply
Fill out a job application on Greenhouse, Lever, or Workday
Also in 5 projects that use this
careerhackeralexSkillevaluate
Evaluate the quality of any AI-generated artifact — visualizations, code, documents, conversations, or any skill output. Works in 3 phases: (1) Generate evaluation specs tailored to the artifact type, (2) Run comprehensive evaluation against those specs, (3) Produce a beautiful visual report using the /visualize skill. Use after any skill produces output, or invoke directly with /evaluate <file-or-context>. Supports evaluating: HTML visualizations, code projects, documents, agent conversations, slide decks, dashboards, or any artifact with quality dimensions.
Also in 4 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 3 projects that use this
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- audio-analysisSkill
- calendarSkill
- code-executionSkill
- connector-action-authorizationSkill
- core-memorySkill
- cost-reportSkill
- councilSkill
- crm-lookupSkill
- daily-briefingSkill
- delegationSkill
- email-digestSkill
- expense-captureSkill
- github-issuesSkill
- gmail-actionsSkill
- gmail-connector-setupSkill
- home-assistantSkill
- host-nodeSkill
- humanizerSkill
- image-genSkill
- inbox-triageSkill
- integration-connector-setupSkill
- knowledge-ingestSkill
- meeting-follow-upSkill
- meeting-prepSkill
- memory-exchangeSkill
- notionSkill
- operationsSkill
- personal-notesSkill
- researchSkill
- self-inspectionSkill
- self-reflectionSkill
- skill-authoringSkill
- speechSkill
- spotifySkill
- travel-prepSkill
- trelloSkill
- twitter-x-actionsSkill
- twitter-x-connector-setupSkill
- weatherSkill
- weekly-reviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

