Skills

Skills are modular capability packages that teach AIRA specialized knowledge. Each skill is a small archive containing instructions and reference documents that AIRA reads on demand. Instead of repeating detailed context every time, upload a skill once and mention it by name whenever you need it.

What is a Skill?

A skill is a .zip or .skill archive that contains:

• SKILL.md — The main instructions file with a name and description in YAML frontmatter. This is what AIRA reads first when you activate the skill.
• Reference files — Supporting documents (markdown, JSON, YAML, text) that AIRA can read when the instructions reference them.

Think of a skill as a portable knowledge pack. For example, you could create a skill that teaches AIRA your brand voice guidelines, your internal data dictionary, or a specific analysis methodology.

Uploading a Skill

1. Navigate to the Skills page from the AIRA section in the sidebar.
2. Click Upload Skill in the top right corner.
3. Select a .zip or .skill file from your computer.
4. The system validates the archive automatically, checking that it contains a SKILL.md at the root with valid name and description fields in the YAML frontmatter.
5. Once validated, click Upload to add the skill to your workspace.

SKILL.md Format

Your SKILL.md file should follow this structure:

---
name: Brand Voice
description: Guidelines for writing in our brand tone and style
---

# Brand Voice Guidelines

Always use active voice and short sentences.
Refer to references/tone-examples.md for sample copy.

Using Skills in Chat

To activate a skill in a conversation, type @ followed by the skill name. AIRA's mention menu will show matching skills. Select one to insert it as a mention chip in your message.

When you send a message with a skill mention, AIRA reads the skill's instructions first and then follows any references to supplementary files within the package. You can mention multiple skills in a single message.

Browsing and Managing Skills

The Skills page provides a searchable, filterable grid of all available skills.

• Search — Filter skills by name or description using the search bar.
• Filter by type — Use the tabs to switch between All, Official, and Custom skills.
• Enable or disable — Toggle individual skills on or off for your workspace.
• Delete — Remove custom skills you no longer need.

Click any skill card to open the skill detail view, which includes a file browser with a tree of all files in the archive. Select any file to preview its content. Markdown files render with a formatted preview.

Skills in Playbooks

You can attach a skill to any playbook so it loads automatically whenever that playbook is invoked. This means you do not need to manually mention the skill each time you use the playbook — AIRA activates it behind the scenes.

To attach a skill to a playbook, edit the playbook and select a skill from the playbook settings.

Official vs Custom Skills

Skills come in two types, shown as badges on each skill card:

Official Skills

Official skills are created and maintained by the AccessFuel team. They are available in every workspace on the platform automatically.

• Read-only — You cannot edit, rename, or delete Official skills.
• Always available — Official skills appear in every workspace. You cannot disable them.
• Duplicate to customize — If you want to modify an Official skill, click Duplicate to create your own Custom copy. Your copy is fully editable and lives only in your workspace.
• Updated by AccessFuel — Official skills may be improved or expanded over time. Updates apply to all workspaces automatically.

Custom Skills

Custom skills are uploaded by you or your team members. They are only available in your workspace.

• Fully editable — You can update, rename, or delete Custom skills at any time.
• Workspace-scoped — Only members of your workspace can see and use Custom skills.
• Can be toggled — Enable or disable Custom skills as needed.

Comparison

Tips for Good Skills

• Keep instructions focused — Each skill should cover one domain or capability. Create separate skills for separate topics.
• Reference supplementary files — Put detailed reference material in separate files and point to them from SKILL.md (e.g., "see references/api-docs.md").
• Use clear frontmatter — A descriptive name and description help team members find the right skill quickly.
• Organize with folders — Group related reference files in subdirectories within the archive for clarity.

Next Step