Skip to main content
Version: 0.8.5

Skills and tools

A Skill is a maintained set of instructions and supporting resources for a kind of work. A Tool is an executable capability such as reading files, searching the web or calling an external MCP service.

An Agent can use local skills and skills from the Skill Store. When a configured store skill is not present, Clawuno downloads the latest copy before the Agent reads it. Default system skills are visible and cannot be removed.

Choose Agent capabilities​

Administrators and Advanced Users select tools and Skills in the Agent editor and save. A short built-in tool list needs only selection; longer lists support search and, when items are selected, a selected-only filter. Default system Skills differ from optional selections: a non-removable default does not indicate a failed save.

Forge helps browse and manage capabilities. Administrators configure instance services such as MCP in system settings; Advanced Users choose already-provided capabilities for Agents. Users operate prepared Agents without Forge or configuration pages.

In Forge, Tools has the Tool Store, with Installed beneath it, and Custom tools for MCP services you added yourself. Skills has the Skill Store, with Downloaded beneath it, and Custom skills for skills created in your company. A section shows how many items it holds once it has any; a red badge on Installed counts tools that need attention.

A Skill teaches a method; it does not grant Workspace, account or external-service permissions. Test a small task after installing or changing one. Review its source, license, scripts and external calls instead of judging only its name or popularity.

Before enabling an external tool:

  • confirm who operates it and where data is sent;
  • provide only the credentials and environment variables it needs;
  • understand whether it can modify external data;
  • test it with non-sensitive data first.

MCP services from the Tool Store​

Forge › Tools › Tool Store offers MCP services that Forge has reviewed. Installing one downloads it once, together with its exact dependencies; after that it runs on this deployment without downloading anything when it starts. Backups do not include these files: after restoring a backup or moving to a new machine, they are downloaded again automatically, and the card shows Needs re-download until npm can be reached.

  • Configure on a service's card is the only place to set it up. Fields have types: plain values are shown and can be edited, sensitive values show Saved encrypted and can only be replaced, and numbers, switches and choices are checked when you save and when the service starts.
  • Forge descriptions are written in English. In the Chinese interface they are shown in Chinese with a link to the English original; in other languages they are shown in English, marked Original. Tool names and descriptions that come from the service itself are shown as the service provides them.
  • Forge offers only the latest version of each service. Update available shows what changes before you update: fields, tools, security and installation. If the new version adds required fields, update first and then fill them in; until then, the affected configurations are incomplete and are not loaded. Sessions already running keep the old version; new sessions use the new one.
  • Forge can stop an installed service: Withdrawn for security, or Update required when the installed version is below the minimum Forge requires. A stopped service ends its running processes, and Agents and Uno run without its tools. The card explains why and offers Uninstall, Update (when an update is required) and Resume. Resuming requires confirming the risk and giving a reason, which is recorded; it applies only to the installed version and that stop. A security withdrawal is final: the service stays stopped even if Forge later removes or lists the entry again, until you uninstall it; after that you can install it again if Forge offers it.
  • If Forge cannot be reached, nothing is stopped or removed: installed services keep their last known state and keep running, and the toolbar shows when Forge was last checked. Use Check for updates to check now. A service that Forge no longer lists keeps working but cannot be updated or reinstalled.
  • Services installed from Forge with an earlier version of Clawuno are shown as Legacy install, no longer supported and do not run. Uninstall them on their card, then install the current version and set up its configurations and Agent or Uno choices again.

If installing, updating, uninstalling or saving fails, the card or dialog says so; open Error details to see the service message. Forge › Tools › Custom tools only manages MCP services you added yourself.

Credentials saved for an MCP service are available only to that service in the same organization. MCP settings do not expand server environment variables: a value containing a reference such as ${NAME} is rejected when the service is tested or started.

Use several accounts with one MCP service​

An MCP service can have several configurations, for example one per mailbox. A configuration holds the values the service needs, such as an address and a password; sensitive values are stored encrypted and can only be replaced, never viewed.

  • System configurations are managed with Configure on the service's card for services from the Tool Store, and in Forge › Tools › Custom tools for services you added yourself. One of them is the default: Agents and Unos that have not chosen configurations use it. Use Show who uses it to see which Agents and Unos chose a configuration.
  • In the Agent editor's Tools step, or in your own Uno panel settings, select an MCP service and choose Use the system default or choose its configurations: pick system configurations by name, create configurations of its own, or both. Once you choose configurations, the system default is no longer used for that service.
  • An Agent's own configurations are used by everyone who can use that Agent. Your Uno's own configurations belong only to you; other members and administrators cannot see or use them.
  • With two or more configurations, the model chooses one by name each time it calls the service. Names can be in any language. The names and their descriptions are sent to the model provider, so do not put passwords or keys in them; Preview what the model sees shows exactly what is sent.

Edits to an Agent's or Uno's own configurations take effect when you save the Agent or Uno settings. Existing services keep working unchanged: their current values become the default system configuration.

Ask Uno:

Which skills and tools does this Agent have, and which one would send data outside this deployment?