Skills

Skills are reusable capability bundles. Instead of attaching every possible tool and instruction directly to a step, you package a domain workflow once and let agents activate it when the conversation needs it.

Use skills when an agent has many possible jobs but only needs a few capabilities on any one turn: support troubleshooting, refund processing, sales research, onboarding, compliance review, data cleanup, and similar workflows.

What a skill contains

Part	Purpose
Name and ID	Stable handle for humans, APIs, and agent references.
Description	Short trigger condition the agent sees before activation.
Instructions	Markdown playbook injected when the skill activates.
Tools	Required tools, each bound to an integration config when attached.
Resources	Optional assets or knowledge sources available to the skill.

The description should say when to activate the skill, not just what it contains. For example: "Activate when the user asks to investigate a Salesforce opportunity or update CRM notes."

Progressive disclosure

Skills keep the model's context small. Before activation, the agent sees only skill names and descriptions. When it calls the activate_skill tool, Fruxon injects the selected skill's instructions, tool schemas, and resources into the session.

Activation is session-scoped. Once a skill is active in a conversation, it remains available on later turns in that same session.

Tools vs. skills

Use direct tools when...	Use a skill when...
The step needs 1-5 tools on every run.	The agent has many possible domains or workflows.
Every tool is relevant to every user request.	Only some tools are relevant after the user intent is known.
Tool descriptions are enough guidance.	The agent needs a procedural playbook or policy.
You want the simplest setup.	You want a reusable capability shared by multiple agents.

Most production agents use both: direct tools for always-on capabilities, skills for specialized workflows.

Attach a skill in Studio

Open the agent in Studio.
Select the step that should be able to activate the skill.
Add the skill from the Skills section.
Bind each required tool to the right integration config.
Preview the instructions and run a test conversation that should trigger activation.

If a required tool is missing credentials, the skill card shows an error until every binding is complete.

CLI and API

The CLI can inspect the skill catalog:

fruxon skills list
fruxon skills show fruxon-create-integration

The API reference includes the integration-scoped skills surface under API -> Integrations -> Skills.

Next steps

Tools & Skills — full runtime model and configuration details
Agent Studio — where skills are attached to steps
Integrations — credentials and tool configs used by skills