agentleFS
sree-datasree-data/job-search-agent/.claude/skills/send-email/SKILL.md

send-email

Skill0 starsChanged 2 months agoMITView on GitHub

Send cold emails that Alex has approved in pipeline/outreach.csv, via Gmail, and log the sends

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aeon-update, auto-workflow and 10 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.
  • aaronjmarsSkill

    aeon-update

    Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.

    Also in 4 projects that use this

  • aaronjmarsSkill

    auto-workflow

    Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.

    Also in 4 projects that use this

  • +10 more from aaronjmars

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read pipeline/outreach.csv.

    line 8
  2. Very specific:

    After each successful send, update the row: status sent, sent_date today, followup_due = today + 5 days.

    line 12
  3. Very specific:

    Create a Google Calendar reminder on the followup_due date titled "Follow up: <name> at <company>", if the calendar connector is available.

    line 13
  4. Very specific:

    Never send LinkedIn messages.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 23 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Send approved emails

  1. Read pipeline/outreach.csv. Select rows where channel is email and status is approved. If there are none, say so and stop.
  2. For each row, open the draft file, show Alex the recipient, subject, and body, and ask for a single confirmation for the batch. Do not send anything before he confirms in this session.
  3. Respect the daily cap of 10 emails. If the batch is larger, send the 10 with the highest job score and tell him what's left.
  4. Send via the Gmail connector, one at a time, from Alex's account. Plain text. No attachments unless the row's notes say to attach the resume.
  5. After each successful send, update the row: status sent, sent_date today, followup_due = today + 5 days. If a send fails, leave the row as approved and note the error.
  6. Create a Google Calendar reminder on the followup_due date titled "Follow up: <name> at <company>", if the calendar connector is available.
  7. Print a summary: sent, failed, remaining.

Never send LinkedIn messages. Never send an email whose status is draft. Never change draft to approved yourself.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.