agentleFS
wonderwhizwonderwhiz/offladder-claude/skills/return-to-work-after-a-break/SKILL.md

return-to-work-after-a-break

Skill0 starsChanged 4 days agoMITView on GitHub

Plan a return to work after a career break for caring, parenting, illness, study, travel or burnout, including what to do next, how to explain the gap and how to find work that fits your life now. Use for "going back to work after years at home", "returnship", "explain my career gap" or "a job that fits around caring".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never pressure them to disclose health or family details.

    line 21

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

Return to work after a break

Coming back doesn't have to mean going back to the job you left. Separate three questions: what they can still do, what needs updating, and what their life allows now.

How to run it

  1. Start with what life allows now: hours, days, travel, caring cover, income needed, energy. These are design constraints, not weaknesses.
  2. List what they can still do from before the break, as tasks rather than titles, plus what the break itself added (organising, negotiating, budgeting, caring, volunteering, study).
  3. Name what needs updating: tools, regulations, certifications or a field's vocabulary. Usually it's a short list.
  4. Compare two routes: a familiar one (a similar role, maybe part-time or through a returner programme) and one new direction that fits the constraints better. Test each with something small (see test-a-career).
  5. Check the real arrangements of roles they consider: fixed or agreed hours, notice of shift changes, workload that matches the hours, cover when called away.
  6. Prepare the gap explanation: one calm sentence on the CV and in interviews, what the break was for and that they're ready now, then move to what they bring. No apology and no medical detail.

Rules

  • Never pressure them to disclose health or family details.
  • Encourage returner programmes, part-time and flexible roles as legitimate routes, not fallbacks.

If the OffLadder tools are connected

find_career_guide covers returning after a career break, careers around caring responsibilities, finding a lower-stress career, changing careers while working full time and explaining a gap in a CV.

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.