agentleFS
Faaz17Faaz17/Agents-and-Skills/skills/outreach/followup/SKILL.md

followup

Skill1 starsChanged 2 months agoMITView on GitHub

Draft the single follow-up to an unanswered cold email, or draft the reply to a company that has responded. Use when a follow-up comes due, when a reply arrives, or to see across both trackers what is owed. Enforces the one-follow-up-only rule.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    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
  1. Very specific:

    Run send_qa on it

    line 22
  2. Distinctive:

    Follow-ups stay under 60 words and add no new argument.

    line 69
  3. Distinctive:

    Never chase a reply less than 24 hours old.

    line 70
  4. Distinctive:

    Avoid Friday afternoons and weekends.

    line 71
  5. Distinctive:

    Never send. Drafts go to the folder for a human.

    line 72
  6. Distinctive:

    Keep both trackers in step.

    line 73

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

/followup, the one nudge and the replies

Usage: /followup (everything due) · /followup "<Person Name>" Space42 · /followup --replies

Steps

  1. Read both trackers and both sent/ folders. The folders are ground truth; the tracker is the summary. When they disagree, fix the tracker.
  2. Spawn followup_planner to compute what is due against today.
  3. Handle replies before anything else. A reply is worth more than a week of cold outreach. If one is waiting, draft that answer first.
  4. For each follow-up due (day 6–7, no reply):
    • Confirm no follow-up has already gone. If one has, the answer is no-reply and the company is finished for this cycle. There is no second nudge
    • Draft it: under 60 words, Re: plus the exact original subject so it threads, the single strongest link restated, the referral fallback, no attachment, no new argument
    • Save to <person>/sent/YYYY-MM-DD-<company>-followup.md, status ready
    • Run send_qa on it
  5. For each reply:

    ReplyResponse
    Interested, wants a callConfirm within 24 hours. Offer concrete times. Attach the CV now
    Asks for the CV or portfolioSend it. At most two files. Never a company its own recommendation letter
    "Not this cycle"Short thanks, ask when to check back, park it with a diary date
    RejectionShort thanks, plus the one question: is there someone else worth talking to. This converts
    Forwarded internallyThank them, and treat the new person as a warm contact rather than a cold one
    Out of officeNo action. Push the follow-up date to after their return
  6. Close out anything past day 14 with no reply after a follow-up: status no-reply. Do not re-contact for three weeks, and then only a different person.
  7. Push outcomes to the vault. A replying contact becomes a 04 People/ note via /obsidian-person — name, company, role, context, and no contact details. An interview becomes a line in 09 Reference/Planned Events.md.
  8. Update both trackers.

Output format

## Follow-up run — <date>

### Drafted
| Person | Company | Type | Words | Status |
|---|---|---|---|---|

### Replies needing an answer
| Person | Company | What they said | Waiting | Drafted? |
|---|---|---|---|---|

### Closed out
| Person | Company | Reason | Status |
|---|---|---|---|

### Due later
| Person | Company | Due |
|---|---|---|

## Next action
<one thing>

Rules

  • One follow-up per company, ever. The single rule most likely to be broken with good intentions. A second nudge converts almost nothing and turns a neutral non-answer into a bad impression.
  • Follow-ups stay under 60 words and add no new argument. If the first email did not work, a longer second one will not either.
  • Never chase a reply less than 24 hours old.
  • Avoid Friday afternoons and weekends. Tuesday to Thursday morning gets opened. The UAE week runs Monday to Friday, so a Sunday send lands before anyone is reading.
  • Never send. Drafts go to the folder for a human.
  • Keep both trackers in step. Updating one and not the other leaves the next session with a wrong picture.

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.