SKILLS & JOB AGENTS
Purpose-built agents.
Governed skills.
Each AI worker is assembled for a defined job from approved skills, bounded connections and a workflow with a human owner.
- 400Governed Skills in the catalogue
- 2,800IF-THEN rules those Skills carry
- 24Industries with a pack of their own
Skill intelligence
UBOSS does not send
every task to a generic AI.
It selects a governed Skill — an approved, published, versioned definition of how one kind of work is done — and refuses the step when nothing in the catalogue fits.
Read from the UBOSS Skill Catalog as it is persisted — 208 UBOSS Verified and 192 Industry Pack Skills, and the rules their published versions carry.
UBOSS Verified
208Skills that apply to any company, whatever it makes. Authored and governed at platform level.
Industry Packs
192Skills that carry one industry's way of working, across 24 industries. Entitled per company.
Company Custom
Per companySkills a company authors for itself. They stay inside that company and never reach another.
A Skill is selected against
Analysis
252Read a situation and say what it means, with the evidence it was read from.
Operations
49Carry a repeatable operational step, inside the policy that governs it.
Review
44Check work against a standard and report what does not meet it.
Drafting
21Produce a first version for a person to decide on. Never the last word.
DataEntry
17Move structured information between systems without retyping it.
Compliance
7Test an action against the rule that constrains it before it happens.
Communication
6Prepare what goes to somebody else, in the form they expect it.
Research
4Gather what is known about a question and cite where it came from.
From the catalogue
Access Review
ReviewIT, Cybersecurity & Service Management
Accounts Payable Control
OperationsFinance & Accounting
Accounts Receivable Collections
AnalysisFinance & Accounting
Anti Bribery Due Diligence
AnalysisRegulatory, Legal & Compliance
Asset Lifecycle Planner
AnalysisMaintenance, Assets & Utilities
AI Use Case Classification
OperationsData, Analytics & AI
Job Agents
AI workers built for the job,
not generic prompts.
An Agent is assembled from an approved Skill, a governed connection and the objective it serves — then tested, and only then activated. It is built for the person whose work it is, by somebody authorised to build; being the operator grants nobody the right to configure.
- 1Objective contextInherited, read-only
- 2Relevant SkillsApproved and published only
- 3ConnectionChosen by identity, never a key
- 4TriggerSchedule or upstream step
- 5OutputWhat it produces, and to whom
- 6ApprovalWhere a person must decide
- 7TestBefore it can go live
- 8ActivateA separate decision
Product illustration of Agent Builder. An Agent cannot be activated until its tests have passed.
Your workflow.
Inside Chief Agent.
Bring a recurring report, a review process or an operational task. We’ll walk through its people, agents, skills and approvals.
Book a Workflow Demo