Skills
Skills package reusable behavior for TARX-compatible tools and clients.
Legacy docs described a large fixed tool catalog. Current TARX docs should not publish exact tool counts unless they come from the live MCP registry or capability registry.
Tool categories
| Category | Examples | Status |
|---|---|---|
| Status | Runtime health and availability. | Available now |
| Memory | Store and recall approved work context. | Pilot-ready |
| Spaces | List Spaces and load project context. | Pilot-ready |
| Delegation | Queue approved background work. | Pilot-ready |
What makes a skill publishable
| Requirement | Why it matters |
|---|---|
| Clear boundary | Users should know whether it runs on Computer, remote MCP, or an approved relay. |
| Evidence | A skill should record what it used, changed, or could not prove. |
| Approval | Actions that affect files, accounts, messages, spend, or hosted capacity need review first. |
| Fallback | If Bridge, local runtime, or Supercomputer is unavailable, the skill should say so. |