agentleFS
wonderwhizwonderwhiz/offladder-claude/skills/future-proof-against-ai/SKILL.md

future-proof-against-ai

Skill0 starsChanged 4 days agoMITView on GitHub

Look at how AI is likely to change someone's job, task by task, and which directions to test next. Use for "will AI take my job", "careers safe from AI", "is my job at risk from automation" or "what should I learn because of AI".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    No career is guaranteed safe from AI, and confident lists are guesses.

    line 8
  2. Distinctive:

    List the tasks, not the title: Ask them to name what they actually spend a normal week doing, roughly by share of time.

    line 12
  3. Distinctive:

    Don't predict timelines or claim certainty.

    line 24

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

Check how AI changes a job, and what to move towards

No career is guaranteed safe from AI, and confident lists are guesses. A more useful question is which tasks in their work are changing, and which ones are moving slowly.

How to run it

  1. List the tasks, not the title. Ask them to name what they actually spend a normal week doing, roughly by share of time.
  2. Sort each task:
    • Mostly predictable text, code, images or data entry: changing fastest.
    • Physical presence, accountability for decisions, trust with people, judgement in messy situations: changing more slowly.
    • Checking, correcting and taking responsibility for AI output: often growing.
  3. Show them the picture as a short table: task, how exposed it looks, and why.
  4. Point to the moves: grow the slower-changing tasks inside their current job, or test two or three directions that are built from them. Emerging roles are often built on old skills plus AI (for example, checking AI output in a regulated field).
  5. Turn it into a test they can do this week (see test-a-career), rather than a course they pay for on a guess.

Rules

  • Say "exposed" or "changing", not "replaced". Exposure means some tasks could change; transformation is more likely than outright replacement.
  • Don't predict timelines or claim certainty.

If the OffLadder tools are connected

  • check_career_change_facts with an AI question returns exact quotes from the World Economic Forum on how fast skills are changing, with links.
  • find_career_guide covers AI and specific jobs (copywriters, translators, customer service, designers, junior developers, recruiters, admin, accountants, paralegals and more), careers safe from AI, and jobs of the future.
  • explore_career_directions with "new jobs AI is creating" returns emerging directions with a test for each.

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.