agentleFS
wonderwhizwonderwhiz/offladder-claude/skills/go-public-after-a-layoff/SKILL.md

go-public-after-a-layoff

Skill0 starsChanged 4 days agoMITView on GitHub

Write a short LinkedIn or X post telling your network you're looking for work, choose the Open to Work setting, and sort the replies into leads with a follow-up for each. Use when someone was laid off and wants to announce it, asks what to post, or has a pile of comments and DMs to deal with.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Wait a day or two: if the layoff is fresh. Whatever they write now, future employers can read.

    line 12
  2. Distinctive:

    Ask for, and use only:

    line 17
  3. Distinctive:

    Keep it to 60 to 120 words for LinkedIn, and a version under 280 characters for X.

    line 24
  4. Distinctive:

    Keep their words. Ask before changing a phrase that is clearly theirs.

    line 30
  5. Distinctive:

    No long dashes, emoji bullets, hashtag piles, "excited to announce", "thrilled", "humbled", "journey", "game-changer", "Agree?".

    line 31
  6. Distinctive:

    Never add a result, number, employer or title they didn't give you.

    line 32
  7. Distinctive:

    When they paste comments and messages, sort every one:

    line 36
  8. Distinctive:

    Never post for them. They copy it and post it.

    line 54
  9. Distinctive:

    Don't give legal advice on severance terms.

    line 55
  10. Distinctive:

    If they sound in crisis, put the post aside and encourage them to talk to someone they trust or a local support line.

    line 56

≈ “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

Going public after a layoff

The post is the easy part. The value is in being specific about what you want, and in what you do with the replies over the next week.

Before the post

  • Wait a day or two if the layoff is fresh. Whatever they write now, future employers can read.
  • Fix the profile first: a headline naming the role they want, an end date on the last job, and Open to Work. Recruiters-only is the quiet option; the public frame suits people who want their network to act. Recruiters are split on the frame, and the stigma is mostly in agency and executive search.

The post

Ask for, and use only:

  1. One line on what happened, with no blame and nothing they wouldn't say to a future boss.
  2. Two or three things they did that someone could hire them for, with a number each if they have one.
  3. The exact next role: title, level, place or remote.
  4. One specific ask, such as introductions to hiring managers at a named kind of company.

Keep it to 60 to 120 words for LinkedIn, and a version under 280 characters for X. Put the point in the first two lines.

Write it so it reads as them

Both feeds are ranked by models that read the post, and since July 2026 LinkedIn readers can flag posts as "Seems like AI slop", which LinkedIn shows to fewer people. So:

  • Keep their words. Ask before changing a phrase that is clearly theirs.
  • No long dashes, emoji bullets, hashtag piles, "excited to announce", "thrilled", "humbled", "journey", "game-changer", "Agree?".
  • Never add a result, number, employer or title they didn't give you.

Sorting the replies

When they paste comments and messages, sort every one:

GroupLooks likeDo
Leadshiring manager, referral to a named role, offer to introducereply within two days with one specific ask
Worth a nudgeformer colleagues, people in the fieldsay exactly how they could help
Kind wordssupport, sympathyone thank-you comment on the post
Noisegeneric agency messages, course pitchesleave them
Be carefulno interview, fees, cheques, requests for ID or bank details, move to WhatsAppdon't share details; report it

For each lead and nudge, draft a follow-up under 60 words with one ask, plus a two-line blurb about them that the helper can forward without editing. Suggest a simple list: name, what they offered, what was asked, when to check back.

If the OffLadder tools are connected

find_career_guide covers what to post after a layoff, sorting replies, Open to Work, what not to post while job hunting and how often to post. OffLadder's Being seen page (offladder.com/go-public) drafts the post, the profile and reply follow-ups from the person's own record and opens LinkedIn or X for them to post it themselves.

Rules

  • Never post for them. They copy it and post it.
  • Don't give legal advice on severance terms; suggest they check any non-disparagement clause before naming the company.
  • If they sound in crisis, put the post aside and encourage them to talk to someone they trust or a local support line.

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.