Five skills make an agent builder: designing a role narrow enough to certify, choosing sources with the right provenance, setting guardrails and limits, writing scenario suites from the organisation's real cases, and taking the agent through certification and re-certification. None of them require training a model. They require knowing the work the agent will do.
What does an agent builder actually do?
An agent builder designs, trains and certifies agents for a specific organisation. The word "trains" can mislead: in a governed system, nobody updates model weights for a customer. The builder qualifies the agent by shaping its brief, sources, bounds and certification. That is closer to writing a job description, an induction pack and an assessment than to machine learning.
The best builders are often people who have done the job the agent will do, or who have worked closely with those who have. They know which cases are routine, which are tricky, and where the red lines sit. The role is described more fully in what an agent builder is.
Which skills matter, and why?
- Role design. A good agent role is narrow, clear and certifiable: what the agent does, for whom, with which capabilities, at which depth. Builders who try to make one agent do everything end up with an agent that cannot be certified for anything above drafting.
- Source selection. Every fact reaching the agent is stamped sealed, signed, declared or external. Builders choose which sources the agent may use for each decision, and make sure decisions that need strong evidence cannot rest on declared or external facts.
- Guardrails and limits. Builders write the organisation's own limits: value thresholds, topics that are always held, red lines that are refused. They also need to understand the platform guardrails and which actions are withheld for every agent.
- Scenario suites. Certification in Attest replays the agent against real cases from the organisation's operation and scores every answer against a floor across seven gates: grounded, refuses, depth, escalates, scope, adversarial and stable. Builders assemble those cases, including the hard ones and the ones where the right answer is to refuse.
- Certification and maintenance. Certificates last 90 days, and a run that clears no depth drops the agent to depth 1 the same day. Builders plan re-certification, investigate failures, and turn reviewers' corrections into changes in brief, sources or bounds.
What does the builder own, and what do others own?
| The builder | Others |
|---|---|
| Designs the role and brief | The process owner agrees the scope |
| Chooses and maintains sources | Knowledge owners keep sources current |
| Writes limits and scenario suites | The risk owner approves limits |
| Runs certification and reads results | Reviewers supply corrections from live work |
Builders need to understand the depth each capability will reach, because it changes what the scenario suite must test; see what skills people need at depth 3 and at depth 4.
What does good building look like?
Take a builder at a regional insurer creating a claims intake agent. She starts by sitting with claims handlers for two days, listing the 15 claim types they see most and the five that cause trouble. She writes the role: register claims, request missing documents, draft acknowledgement letters, at depth 2; no settlement. She sets sources: the policy library and claims system as sealed, claimant uploads as external.
Her scenario suite has 200 real past claims, including fraud indicators, complaints disguised as claims, and claimants in distress. The first Attest run fails on escalation: the agent drafted routine letters to two bereaved claimants. She adds a held rule for bereavement signals and reruns. The agent passes, and is certified at depth 2. When handlers later correct its drafts, she reads every reason and batches changes for the next run.
How should teams develop builders?
Pair new builders with experienced reviewers from the business. Give them real cases to build suites from. Make them read Attest results gate by gate, not just the overall outcome. And map their skills against the team's needs using a skills matrix template; what a skills matrix is explains the idea. The wider role map is in AI agent skills by role.
Where the Academy fits
The Builder track at Pryme Intelligence Academy is designed for this role: about 24 hours of study, with labs in a free Build workspace, and a capstone. Certified Pryme Builder requires a proctored exam and a capstone agent certified in Attest to depth 2 or higher. The certificate is valid for 12 months and checkable at source through VerifyDoc.ai.
Questions people ask
Do agent builders need to code?
Not for most of the work. Role design, sources, limits and scenario suites are written in plain language and configuration. Technical skills help when connecting new systems.
How many cases should a scenario suite have?
Enough to cover the routine cases, the known hard cases and every red line. Quality of cases matters more than quantity.
Who should builders report to?
Usually the process owner or an operations lead, with a dotted line to risk. Builders need to be close to the work and accountable for what they certify.