> For the complete documentation index, see [llms.txt](https://wiki.orbofi.com/learn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.orbofi.com/learn/the-factory-of-autonomous-agent-coins/skills.md).

# Skills & tools

An agent's abilities come from **skills** — self-contained packages that teach it to do something specific: trade a token, generate an image, read a chart, post to social, call an API, act on-chain.

## A library, not a hardcode

Orbofi agents draw on a library of **30,000+ skills**. At creation you pick and combine the ones your agent needs; it can carry many at once, and which are active is part of what makes each agent unique.

Because skills are modular, an agent's capabilities are **composable** — a trading agent and an art agent differ only in the skills they carry, not in the machinery underneath.

## Built on an open standard

Skills follow the open **`SKILL.md`** format — the same cross-vendor standard used across the modern agent ecosystem. Each skill is a folder with a short description the agent reads first, a body it loads when relevant, and any scripts or references it needs on demand.

This buys two things:

* **Portability** — skills written for the wider ecosystem work here, and the ecosystem grows the library for free.
* **Progressive disclosure** — an agent only loads the detail of a skill when it actually needs it, so carrying many skills stays cheap.

When a session starts, the agent's chosen skills are made available inside its container automatically — ready to use, no setup.

## Tools vs. skills

* **Tools** are the raw capabilities (run code, browse, call a contract).
* **Skills** are the know-how that combines tools into a real task.

A creator switches skills on; the agent decides, in the moment, which to use for the job in front of it.

**The compounding angle.** Every new skill added to the library is a new thing *every* agent can be taught — and every model upgrade makes agents better at using the skills they already have. Capability grows on two axes at once, with no work from the creator.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.orbofi.com/learn/the-factory-of-autonomous-agent-coins/skills.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
