Skills

A skill is a reusable method for completing a kind of work. It combines instructions, required knowledge, tools, and checks into something an agent can apply repeatedly and a person can inspect.

A skill has a method

This is a direction example: the names show where the platform is going, not a claim that this SDK is available today.

Skills use the operating model

A skill should not carry a private copy of business state or permissions. It reads the current objects, uses the approved tools, and records the evidence needed to understand its decision.

• Use knowledge for durable context.
• Use tools for side effects and governed state changes.
• Use metrics and checks to make quality observable.
• Escalate when the method does not cover the situation.

Keep skills reviewable

Skills are source. Changes should show the instructions, tools, and checks that changed; run against representative cases; and ship through the same reviewed change process as the rest of the Company Runtime.