agentleFS
alexratmanplalexratmanpl/business-agent-skills/skills/careers/role-fit/SKILL.md

role-fit

Skill1 starsChanged 2 months agoMITView on GitHub

Compare someone's background against a specific job and give an honest verdict on fit — including a rough probability, the gaps, and the unusual strength other applicants lack. Use when someone shares a job description and asks whether to apply, whether they qualify, how they measure up, or why they keep getting rejected. Judges fit only — see company-research, interview-prep, pay-check.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. FynePool/job-hunter-template★ 3same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Use whatever interactive choice mechanism the environment offers — tappable options where they exist, plain questions otherwise.

    line 18
  2. Distinctive:

    Does the title match the requirements?: If the requirements are broader or more senior than the title, say so — bigger job than advertised, …

    line 31
  3. Distinctive:

    Is the advert the job?: Check for responsibilities but no outcomes, a very small team hiring senior, or a manager who still does hands-on …

    line 35
  4. Distinctive:

    Write the actual sentences: what they have done, where it stops, what they'd need to learn and why they'd learn it fast.

    line 56
  5. Distinctive:

    If something relevant is missing, draft the entry: what they owned, over what period, at what scale, with what result.

    line 60

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

Role Fit

Tell someone the truth about whether they fit, and what to do about the parts where they don't.

Stance

  • Honest, not encouraging. A stretch is a stretch. Say why, and what would change it.
  • Never help them overclaim. Say exactly what they did, mark where it stops, name what they'd need to learn. Precision reads as senior; bluffing collapses under questioning.
  • If they admit something isn't theirs, drop it entirely and say what that removes from their case.

Asking

Use whatever interactive choice mechanism the environment offers — tappable options where they exist, plain questions otherwise. One round, three questions at most.

If nobody is watching — a background job, a scheduled run, a delegated task in an agentic workspace — do not stall waiting for an answer. Take the most useful default, state the assumption plainly in the output, and carry on.

Ask first

  • The job description, full text. Ask them to paste it if a page won't load.
  • Their background — CV, profile, or description.
  • What isn't written down. Freelance work, side projects, earlier careers, anything left off for seeming irrelevant. People routinely omit the most relevant thing they've done because it doesn't match their current title. This question matters more than any other here.
  • What they actually want. Sometimes they fit a job they'd hate.

Read the job description properly

  • Does the title match the requirements? If the requirements are broader or more senior than the title, say so — bigger job than advertised, or a trap.
  • Find the real filters: bold text, anything marked essential, anything appearing twice, and the "this probably isn't for you if" list. That last is the most honest part of any advert.
  • Separate must-have from wish-list. The person hired usually misses one or two. The question is which.
  • Tools listed: be honest about which take a weekend and which take years.
  • Is the advert the job? Check for responsibilities but no outcomes, a very small team hiring senior, or a manager who still does hands-on work full-time. Two or more make the advert unreliable.

Compare

Four buckets:

  • Meets — specific evidence against specific requirements, in the employer's words. Name the project, scale, year. Claims of transferable skills are worthless here.
  • Doesn't — plainly, especially anything essential. Say where it surfaces and who asks.
  • Unclear — and how to find out. If the advert is unreliable, have them ask the employer: what would this hire do in the first six months that the team can't do now? A vague answer means the job is underdefined.
  • The unusual advantage — what almost nobody else applying has. Usually mention it early; it reframes everything else.

Size their numbers first

If the job involves scale of any kind, estimate what they've handled against what the company handles. Show the arithmetic. Use real figures, not flattering ones. Saying "I've worked at this size, not that one" beats being caught out — sizing a problem accurately is usually part of the job.

Verdict

Strong fit, plausible, or stretch. If the advert is unreliable, say the verdict is on the advert as written, which may differ from the job. Give a probability if asked and explain what drives it. If it's a long shot, say so, then say whether to apply anyway and what else should be running alongside.

Gap script

Write the actual sentences: what they have done, where it stops, what they'd need to learn and why they'd learn it fast. Nothing vague, no apology.

CV

If something relevant is missing, draft the entry: what they owned, over what period, at what scale, with what result. Invisible in a thirty-second screen means it doesn't exist.

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.