Skills
Skills, tools, and integrations
How customers add approved capabilities, tools, and integrations to Kaidera workers.
Created from Phase 2 docs inventory and public-safe skills/tooling narrative.
What a skill is
A skill is an approved capability that helps an AI worker perform a specific kind of work. It can provide instructions, workflows, tools, connectors, or specialised behaviour for a recurring task.
Why skills exist
Skills let customers extend AI worker behaviour without turning every custom workflow into a new product build. A good skill makes a repeated process easier, safer, and more consistent.
Tools and connectors
Tools and connectors let workers interact with approved systems. Examples can include source control, documents, support systems, communication tools, design tools, or business data sources depending on the customer configuration.
Skill approval
Customer admins should approve which skills are available, which workers can use them, what systems they touch, and what actions require human review.
Bind a skill to a worker
A skill should be bound to a worker only when it supports that worker role. A design-review skill belongs with design or QA work. A support-triage skill belongs with a support worker. Avoid giving every worker every capability.
Trust tiers
Skills should be understood by trust level. Low-risk skills may read or summarise. Higher-risk skills may create tickets, update files, call external tools, or affect customers, and should need stricter review.
What can go wrong
Skills become risky when their purpose is unclear, they are attached to the wrong worker, they touch external systems without approval, or users cannot tell what action was taken.
Read next
Read Steering and guardrails before increasing skill autonomy. Read Admin settings when deciding who can approve skills.
Website context
Connect this guide back to the product story
The technology docs map links this page to the public technology narrative and helps buyers move from a capability overview into the right operating guide.
Open technology docs map →