agentleFS
wonderwhizwonderwhiz/offladder-claude/skills/follow-up-on-applications/SKILL.md

follow-up-on-applications

Skill0 starsChanged 4 days agoMITView on GitHub

Track job applications and write short follow-up, thank-you and feedback-request emails after applying or interviewing. Use for "should I follow up on my application", "I haven't heard back", "thank-you email after interview" or "how do I ask for interview feedback".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    If many applications get no reply, look at the pattern, not one silence: are the roles a stretch on must-haves, is the CV tailored to each …

    line 23
  2. Distinctive:

    Never send an email on their behalf.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Follow up on job applications

One follow-up after applying and one after a missed decision date is enough. After that, energy goes to the next application.

Timing

  • After applying: about one to two weeks after the closing date, or two weeks after applying if there's no closing date.
  • After an interview: a thank-you within 24 hours, ideally to each interviewer.
  • After a missed decision date: one polite note a few working days later.
  • After a rejection: a short request for feedback, then move on.

How to write each note

Under 100 words: the role, the date they applied or interviewed, one specific reason they match (or one thing from the conversation), and one polite question about timing. Subject line names the role.

Not hearing back at all

If many applications get no reply, look at the pattern, not one silence: are the roles a stretch on must-haves, is the CV tailored to each post (see tailor-cv-to-job), and are applications going in early?

Tracking

Suggest a simple tracker: company, role, link, date applied, contact, next step and date, outcome. Patterns show up after ten or so applications.

If the OffLadder tools are connected

find_career_guide covers following up, not hearing back, what happens after you apply, how long hiring takes, asking for interview feedback and tracking applications.

Rules

  • Never send an email on their behalf; draft it for them to send.

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.