---
title: "Skills Reference"
description: "A Tajo skill is a folder with a SKILL.md file: instructions the agent reads before it builds or runs a sync. What a skill contains, how it loads, and which ones ship today."
url: https://tajo.io/docs/skills/
markdown: https://tajo.io/docs/skills.md
lang: en-US
---

# Skills Reference

A Tajo skill is a folder with one required file, `SKILL.md`. The file has a short header that says when the skill applies, then the instructions the agent follows. The agent that builds your sync reads the skill for the tool in front of it before it acts.

A skill is text, not code. It changes what the agent knows, not what the agent is allowed to do.

## Use a skill

There is nothing to install. Skills ship with Tajo, and the agent picks them from what you ask for.

1. **Connect two tools** - Pick a source and a destination from the [integration guides](https://tajo.io/docs/integrations/). Shopify, Webflow and Brevo run syncs today.
2. **Describe the sync** - For example: “Send new Shopify customers and their orders to Brevo every hour.” The agent matches your words against each skill’s triggers and reads the skills that apply.
3. **Approve the result** - The agent proposes a field map. You approve it before anything runs.

Info

Tajo is in early access. [Ask for access](https://tajo.io/contact/) to run a first sync.

## What a skill looks like

This is the skill the agent reads for Shopify work. The header and two of its sections, as they ship today:

```markdown
---
name: Shopify Solution Builder
description: Build and review Shopify integrations using official specs docs SDKs CLIs and Integration Builder confidence gates
triggers: [shopify, connector, integration, solution pack, openapi, swagger, sdk, cli, events, ingestion, emission]
supportedAgentKinds: [sync_worker, qa_engineer, support]
requiredTools: [discover, read_ref, request_approval]
requiredConnectors: [shopify]
---
# Shopify Solution Builder

Use this skill when building, reviewing, or debugging Shopify connector work. Prefer official vendor surfaces and block production generation when evidence is synthesized or below confidence threshold.

<!-- Official Surfaces, Build Rules and Common Recipes omitted -->

## Guardrails

- Do not use deprecated Admin REST endpoints for new builds.
- Require shop domain, API version, scopes, and token class in every generated adapter.
```

| Field | What it does |
| --- | --- |
| `name`, `description` | The agent always sees these two for every skill it may use. They are how it decides which skill to read. |
| `triggers` | Words to look for in your message. On a match, the whole skill is loaded before the agent’s first reply. |
| `requiredConnectors` | The tools the skill is about. One connected tool from the list is enough. |
| `supportedAgentKinds` | The kinds of agent that may use the skill. An empty list means all of them. |
| `requiredTools` | The tools the instructions refer to. |

Below the header, a skill is plain Markdown. A skill folder can also carry reference pages. The Shopify skill has eight, covering install and auth, resources and endpoints, webhooks, and rate limits.

## How a skill loads

1. **The list** - Every agent starts with the name and one-line description of each skill assigned to it. The full text stays on disk.
2. **The match** - If your message contains one of a skill’s triggers, and one of its connectors is connected, the full skill is loaded before the first model call.
3. **The pull** - For everything else, the agent calls `read_skill` with the skill’s slug and gets the full text. “Our storefront orders aren’t syncing” contains no trigger word. The list is how the agent still finds the Shopify skill.
4. **The memory** - After a run, Tajo stores the outcome with the skill: how many times it ran, the last status and the last five run summaries. They come back the next time the skill loads.

## Skills that ship today

These are the skills that cover building, running and checking a sync. The names are in English because the files are.

### Connector builders

Build and review an integration from the vendor's official API spec, SDK and CLI, not from guesses.

- Shopify
- WooCommerce
- BigCommerce
- Stripe
- HubSpot
- Mailchimp
- WordPress
- Zapier
- Make
- n8n
- Connector Solution Builder

Build 11 skills

### Sync operators

Move the data: upserts keyed on the source's own ID, Shopify GraphQL writes, Brevo API calls and contact enrichment.

- Reverse ETL Operator
- Shopify GraphQL Operator
- Brevo Deep API Operator
- Enrichment Operator

Run 4 skills

### Sending

Draft, preview and schedule email and SMS through Brevo, and wire transactional sends that fire once per trigger.

- Brevo Engagement Designer
- Email Craft
- Transactional Email Patterns
- Campaign Planner

Send 4 skills

### Compliance and deliverability

Review a send against GDPR, CAN-SPAM and TCPA before it goes, set up SPF, DKIM and DMARC, and handle bounces and complaints.

- Compliance Reviewer
- Email Compliance
- Email Authentication
- Email Deliverability

Check 4 skills

Caution

A skill is not a connector. A builder skill for Stripe or HubSpot tells the agent how to build that integration from the vendor’s official sources. It does not mean the connector is live. Shopify, Webflow and Brevo run syncs today.

## What a skill is not

- **Not an MCP tool.** A tool is something the agent calls. A skill is what the agent reads before it calls one. [MCP and agents](https://tajo.io/docs/mcp/) covers the tools.
- **Not a permission.** Approvals, budgets and consent checks are enforced by Tajo, not by the skill’s text.
- **Not shared by every agent.** An agent sees only the skills assigned to it.
- **Not yours to upload.** Every skill is written by Tajo and ships with the product. You cannot add your own today.

## For agents

The map of this site for machines is one request:

```bash
curl -s https://tajo.io/llms.txt
```

The full text of the documentation is at [tajo.io/llms-full.txt](https://tajo.io/llms-full.txt).

## Next steps

- [Getting started](https://tajo.io/docs/getting-started/) - What Tajo builds and how a first sync works
- [Integration layer](https://tajo.io/docs/integrations/) - How a source tool is connected to a destination tool
- [MCP and agents](https://tajo.io/docs/mcp/) - How integrations are exposed as MCP tools