Development firms & engineering teams
Build reusable agent capabilities.
Import the configuration you already maintain. Separate instructions, tools and context into reviewable capabilities, then test their behavior before handing a bundle to an operator.
Launch specification. Application source, downloads and versioned compatibility evidence publish with releases.
Operating workflow
Agent development, from input to evidence.
A documented capability bundle with source lineage, declared dependencies, test evidence and an accountable owner.
- 01
Import and inspect
Start with agent files and project configuration. Review detected instructions, tool references and source provenance before creating reusable modules.
Review the specification - 02
Compose and test
Give each skill a defined input, output and dependency boundary. Exercise workflow branches, failure cases and required approvals in the Test Lab.
Review the specification - 03
Package and hand off
Record a version, runtime target and known limitations. Keep client-specific configuration separate from reusable capabilities and credential material.
Review the specification
Operator experience
Inspect the configuration behind the action.
Use the interface preview to orient the evaluation. Review the linked specifications for boundaries, responsibilities and evidence.
Evaluation checklist
Define a bounded first workload.
Work through these questions, then continue to the technical material for your operating role.
What enters the bundle?
Record source files, their provenance, configuration versions, required tools and declared inputs. Keep secrets outside the shared capability package. A source file describes behavior; it does not authorize its execution.
How is behavior evaluated?
Choose a small representative workflow and explicit success criteria. Include missing context, invalid outputs, policy denials and connector failure. Test results describe the evaluated configuration, not every possible future run.
What does a client receive?
Hand over the bundle revision, configuration responsibilities, adapter requirements, evaluation results and rollback procedure. Keep operator approval and customer acceptance separate from a successful test.
