agentleFS
alexratmanplalexratmanpl/business-agent-skills/skills/careers/pay-check/SKILL.md

pay-check

Skill1 starsChanged 2 months agoMITView on GitHub

Work out what someone should be paid and what to say about it — comparing a salary, day rate or offer against the local market, converting between employment and contracting, and reopening a number already given. Use when someone mentions a salary, day rate, offer, pay rise, what to ask for, or a recruiter asking their expectations. Includes a calculator so the arithmetic is right. Money only — see company-research, role-fit, interview-prep.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    If code can't run, do the arithmetic explicitly and show every step: working days assumed, whether holiday is paid, exchange rate used.

    line 17
  2. Distinctive:

    Look them up rather than recalling them.

    line 23
  3. Distinctive:

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

    line 38
  4. Distinctive:

    How urgent: No income and one live process is a weak position.

    line 49
  5. Distinctive:

    Search local rates for that role, level and contract type.

    line 53
  6. Distinctive:

    Only one or two live processes weakens a position more than any script repairs.

    line 85

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

Pay Check

Work out the number, and what to say about it.

Use the calculator

scripts/rate_calc.py in this skill's directory — ${CLAUDE_SKILL_DIR}/scripts/rate_calc.py in Claude Code. Run --help to see what it covers, and trust that over anything written here: the script is updated on its own and this file is not. Every subcommand repeats the inputs it used, so quote its numbers together with those assumptions.

It holds no market data and reaches no network. Rates, percentages and day counts all come from you, which is what makes a result reproducible and a wrong assumption visible rather than buried in the total.

If code can't run, do the arithmetic explicitly and show every step: working days assumed, whether holiday is paid, exchange rate used.

Tax, and where the numbers come from

The calculator holds no rates for any country. For after-tax figures, look the parameters up and pass them in a rate file. rates-example.json in this skill's directory is a filled example — copy it and replace every figure, including the sources. rate_calc.py rates-template prints the same shape empty, if that is easier to fill.

Look them up rather than recalling them. Thresholds and percentages change every year, and a remembered figure is the one most likely to be a year out of date.

  • The tax authority's own pages first. An accountancy firm's summary second, and mainly to find out what to go and look up.
  • Record the source URL and the tax year. The file has fields for both, and the calculator refuses to produce after-tax numbers without them, because a tax figure nobody can check is worse than none.
  • Reliefs for people arriving from abroad are conditional — on age, on prior residence, on how long they run. Put the conditions in the file, and say which were applied. Never apply one because the country happens to have it.
  • VAT is usually not part of take-home. A registered contractor charges it and passes it on. It changes the answer only under a flat-rate scheme, or where a client will not pay it on top.

If nothing can be looked up, say so and fall back to --employee-tax-pct and --contractor-tax-pct with their own estimate. The output labels that result as built on flat rates. A comparison somebody knowingly built on their own guess beats no comparison, as long as it says so.

Either way the result is an estimate. Give the tax year, name the sources, and say it wants checking with an accountant before anything is signed.

A day rate quoted without saying whether holiday is paid can be out by a tenth. A contract rate compared to an employed salary with no adjustment for holiday, sick pay, pension and employer taxes is not a comparison.

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 number and its unit — year, month, day, hour.
  • Employment or contracting, and whether holiday is paid. Not comparable without adjustment.
  • Where — the country, and where the employer is based if different.
  • What they earn now, and what they want.
  • What's already been said. A number given in screening is an anchor; the job is usually to reopen it, not set it.
  • How urgent. No income and one live process is a weak position. This changes the advice more than any market data.

Find the range

Search local rates for that role, level and contract type. Be specific about the city. Use several sources and give a range — published salary data is thin and skewed.

Note when an employer based somewhere expensive pays local rates somewhere cheaper. Common, not scandalous, worth asking about directly.

Say where they stand

Above, at, or below — plainly. If they're below their own market, and especially below what they already earn, say so. People undersell themselves between jobs and nobody tells them.

Name the cause if visible. The usual sequence: left a job, recruiter approached, gave a number under pressure before knowing the scope, now anchored. Recoverable, and naming it helps.

Reopening a number

The mechanism is scope, not regret:

"We discussed a rate on the basis of role X. If the scope is what the requirements describe, I'd want to revisit the number so it matches the actual job."

Nobody reasonable objects. Asking for more with no reason attached doesn't work.

If asked first

  • Give a range, bottom at a number they'd accept. Fast, but caps the outcome.
  • Ask their band first. Reasonable, sometimes refused.
  • Defer once, then answer. Buys information, can read as evasive.

Whichever — have a number ready. Improvising under pressure is how people anchor low.

Shares and options

At a private company, a lottery ticket, not pay. Never count it as salary. Ask about vesting, sale, and leaving — but the cash number is the number.

Say this if it applies

Only one or two live processes weakens a position more than any script repairs. Three conversations beats any negotiating tactic.

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.