Define one useful job
Describe the repeated task, the desired result and examples that show what good looks like.
Your project Agents & skills
Purpose-built instructions, tools and skills for work with defined boundaries.
Set the task, inputs and boundaries.
Scroll to explore
An agent starts with a job to do, examples of good work and a point where it should ask for help. More tools do not automatically make it more useful.
We scope one workflow, define its inputs and permissions, and test it on representative tasks. Downloadable skills and packs remain planned formats until their own files and compatibility are verified.
Each agent and skill requires workflow-specific testing. No claim of guaranteed autonomous decisions or universal compatibility.
A clear path through the work
Describe the repeated task, the desired result and examples that show what good looks like.
Choose necessary tools, permitted actions and an escalation owner. Make missing information and pause behaviour explicit.
Test representative tasks beyond the build examples. Keep the supported runtime and remaining limitations in the handover.
Provisional service fees in GBP. We are not registered for UK VAT and do not add UK VAT. Required third-party costs depend on the agreed tools and use; each offer explains the calculation. Your written quote confirms the total or calculation before you commit. Open an offer to see the work, inputs, limits and acceptance checks before adding it to your brief.
Required platform/runtime, model and tool costs depend on the chosen workflow. Calculate plan fees + model/API/execution units used × the relevant provider rate. Hosting may also be required. These are identified and costed before an order; extra tools are optional unless agreed as necessary. No UK VAT is added.
Not for sale. Before release, the product page must identify required tools and their plan/usage rates. Setup help is optional and separately quoted. No UK VAT is added.
Not for sale. Before release, required accounts, software plans and AI usage rates must be identified alongside the product’s full cost information. No UK VAT is added.
Not for sale. Before release, required platform/runtime fees and API units × provider rates must be specified. There is no purchase or delivery commitment now. No UK VAT is added.
Bring one defined workflow, examples of the inputs and a description of a useful result. It helps to explain when a person should review or take over. The scoped agent offer covers one agreed job with instructions, examples and tool boundaries. It does not promise an assistant that can handle every task or use unlimited tools.
That depends on the permissions and review points agreed for the workflow. We define permitted actions, missing-information behaviour and when the agent must pause or hand back to a person. The handover should make those boundaries clear. A custom agent is not a promise of unrestricted autonomous decisions or universally accurate output.
Those tools are part of discovery, rather than an automatic inclusion. We need to understand the available access, permitted actions, representative inputs and who owns escalation. Platform, model, API and hosting charges may remain separate. Compatibility and boundaries must be checked for the chosen workflow before the scope can be treated as agreed.
The checks should cover representative tasks beyond the examples used while building it. They also need to show what happens when information is missing and whether pause and escalation boundaries are respected. The supported workflow, tools and remaining limits belong in the handover. Passing an agreed set of checks does not guarantee every future answer.
No. The custom agent offer is work scoped around one customer's workflow. The listed individual skill, workflow pack and tested agent toolkit are separate planned product formats, currently not for sale. Each future release needs its own original files, supported tools and setup, workflow, failure and removal checks. A generic download does not replace customer-specific integration.
One workflow, stated tool boundaries and agreed examples make the intended result and handover assessable before a wider rollout.