Skills
Expertise the agent loads only when it needs it.
A skill bundles instructions, tools, and knowledge into one reusable unit. Attach it to any agent and that agent gains a competence — without every prompt paying the context cost of every capability.
Progressive disclosure keeps context small
Before activation, the agent sees only skill names and descriptions. When it calls activate_skill, Fruxon injects that skill's instructions, tool schemas, and resources into the session. An agent can have many possible jobs and still carry only the few it needs on this turn.
Write the playbook once, share it everywhere
A skill holds a markdown playbook, the tools it requires — each bound to an integration config when attached — and optional assets or knowledge sources. Support troubleshooting, refund processing, sales research, compliance review: package the workflow once instead of copy-pasting it into every agent that needs it.
The description is the trigger
A skill's description tells the agent when to activate, not just what's inside. "Activate when the user asks to investigate a Salesforce opportunity or update CRM notes" is a routing instruction the model can act on — which is why skills stay reliable as you add more of them.
How it fits together
Skills are how capability scales past one agent.
Skills draw on the same tools and knowledge bases as everything else, so there's no second system to maintain. Update the playbook once and every agent that uses the skill picks it up on its next revision.
Bundle tools, instructions, and knowledge into one attachable unit
Reuse across agents and sub-agents without duplicating configuration
Skill activations show up in the trace, so you can see what fired and when
The rest of the build surface
Every capability is included on every plan — see pricing