Custom Agent Skills

Firetiger’s agents ship with a built-in library of skills — focused, reusable instructions an agent reads on demand (how to query a table, how to write up an issue). With a Skills Bundle you add your own: point Firetiger at a directory of agentskills.io-format skills in one of your GitHub repositories, and every agent in your organization can use them.

Use this when you have org-specific runbooks, conventions, or procedures you want your agents to follow — your deploy process, your escalation policy, the quirks of a particular service — authored as version-controlled Markdown rather than pasted into prompts.

How skills are structured

A skill is a directory containing a SKILL.md: YAML frontmatter (a name and a one-line description) followed by the instructions. Your repository holds one directory of these, with each immediate subdirectory being a single skill:

skills/
  deploy-production/
    SKILL.md
  rotate-credentials/
    SKILL.md
    scripts/
      rotate.sh

---
name: deploy-production
description: Run a production deployment and verify the rollout
---

# Deploy to production

1. Confirm the release PR has merged to `main`.
2. Trigger the deploy workflow…

The directory defaults to skills/, but you can point at any directory in the repo. Files under a skill’s scripts/, references/, and assets/ subdirectories are mounted alongside it; other files are ignored.

Skills are agent-agnostic instructions — they describe how to do a thing, not which agent should run. Keep Firetiger-specific routing out of SKILL.md.

Prerequisites

• A GitHub Connection whose installation can read the repository holding your skills.

Connect a repository

In the Firetiger UI, open Integrations → Skills and click Add Skills:

1. Display Name — a label for this provider (e.g. “Platform Runbooks”).
2. GitHub Connection — the connection that grants repository access. Only GitHub connections are eligible.
3. Repository — owner/repo.
4. Directory — the directory of skills within the repo. Defaults to skills.
5. Branch — the git ref to read from. Leave blank to use the repository’s default branch.

Save, and Firetiger resolves the repository’s skills immediately.

Review what was discovered

Open the provider from the Skills list to see every skill Firetiger found in the directory — its slug, its description, and the full SKILL.md. This is the same set your agents see, fetched live from GitHub, so it’s the quickest way to confirm a repository is laid out correctly. If a skill is missing, check that it lives in an immediate subdirectory of the configured directory and contains a SKILL.md.

How agents use them

Resolved skills are mounted read-only at /n (/run/skills) inside every agent’s environment, alongside the built-in library. Agents discover them by listing the mount and read a skill’s body when it’s relevant to the task at hand.

• Org-wide. Every agent in your organization sees the org’s custom skills. Per-agent targeting is reserved for a future release.
• Built-ins win. If a custom skill has the same name as a built-in library skill, the built-in takes precedence.
• Always current. Bodies are fetched at agent runtime from the configured branch, so merging a change to a SKILL.md updates what agents read — no re-import step.

Disable or remove a provider

Editing a provider exposes an Enabled toggle. Turn it off to stop serving its skills while keeping the configuration, or delete the provider to remove it entirely. Either change takes effect for new agent work within a short cache window. Credentials live on the GitHub connection, not on the provider, so deleting a provider never touches your connection.

API

Everything above is available over the API — register providers and list the skills a provider exposes. See the Skills Bundles API reference.