A step-by-step process that gets to a defensible offer, not a guess. It checks what is missing before it gives any number, and shows its reasoning every time.
Pay recommendations tend to go wrong in three ways. Steps get skipped. The logic changes from one case to the next. And reward is brought in late, then asked to approve a number when an offer is already on the table.
This skill holds the line on process. It checks what is in hand before it says anything about money. If something essential is missing, it stops and lists the gaps. Then it works six steps in a fixed order and shows its reasoning at each one.
A skill is a written set of instructions, saved as a file, that an AI assistant follows every time it does a particular job. It turns “a good first draft, if you ask the right way” into “the same method, every time, whoever is asking”.
For your team, that means the same logic whoever handles the case, and something to point to when a manager pushes.
Three real exchanges with an AI assistant using this skill, on an invented case at Banksia Example Co (an invented organisation). Press Play to watch each one, or Show all to read it.
These are real responses, saved and replayed. Nothing you do here is sent to an AI.
Five steps from a manager's request to a reasoned position. Press Play, or step through at your own pace.
The gate. Before any recommendation, the skill checks what is in hand. In this example two items are missing, so it stops and says why they matter. Once they are supplied, the run continues.
Not “Technology” or “Data” in general. The market match is the specific role.
Size, family, market match. Steps a, b and c fill in one at a time. The skill uses your job sizing result. It does not size the job itself.
18 people in the sample, from 11 organisations.
Example thresholds. Replace them with your own.
Market median and how far to trust it. A median is only as good as the sample behind it. Here 18 people lands in the medium band, so confidence is medium.
Reference point and range. The skill matches the role to your reference point, then draws the range around it. Peers appear as positions, with no names and no salaries.
Position the person, show the reasons. This step is judgement, not a formula. The skill's job is to make the reasons explicit. A person decides.
All figures in this walkthrough are invented, for illustration only. The thresholds and the plus or minus 10 percent range are examples to replace with your own.
You can build your own version with any capable AI assistant your employer allows, for example Microsoft Copilot, Claude or ChatGPT. The aim is to write down how your team really makes a pay recommendation, then turn it into a skill.
The method on this page is generic. Your thresholds, ranges and rules will differ, so build with your own process and invented data, never real pay data. Expect a few rounds of “that's not quite right, change X”.
Most teams have never written the process down. Let the AI interview you, one question at a time.
The gate is the most valuable part. It stops the AI from guessing when information is missing.
These are the rules you want held every time, however much pressure the person asking is under.
Test with invented cases built to make the skill fail. If it holds up, then trust it a little.
A skill is only useful if people can reach it. Where you put it depends on the tool your employer has approved.
Microsoft's documentation says agent instructions can be up to 8,000 characters, and a skill file up to 20,000 characters (Microsoft Learn, checked November 2026). We have not yet tested this skill inside Copilot.
An individual's proposed pay, peers' pay positions, and market data that is usually licensed. Each one needs care, for different reasons.
Work with role and level, not names. Give peer pay as positions against the reference point, not as names and salaries. Do not paste licensed survey data into a tool your licence does not cover. Use tools your employer has approved.
Privacy rules for employee records differ between private employers and government agencies, so check with your privacy officer. Start with the OAIC's guidance on the Australian Privacy Principles and on employment and privacy. General information, not legal advice.
Add SKILL.md to your assistant as a skill or as instructions, then try the sample case before you use a real one. Replace the example thresholds and the plus or minus 10 percent range with your own first.
What next: Back to all use cases