Skip to main content
Skills are reusable, self-contained packages of instructions that extend what DinoAI knows how to do. DinoAI auto-discovers the skills in your repository and loads them on demand — only pulling a skill’s full instructions into context when it’s relevant to the task, so your context stays lean. DinoAI is compatible with the standard agent skills format, so skills you already maintain (alongside CLAUDE.md / AGENT.md) work without changes.

How skills are structured

A skill is a folder containing a SKILL.md file. DinoAI discovers skills from any of these locations in your repository (checked in this order):
  • .claude/skills/<name>/SKILL.md
  • .dino/skills/<name>/SKILL.md
  • skills/<name>/SKILL.md
  • SKILL.md (repository root)
Each SKILL.md has YAML frontmatter with a required name and description, followed by the instructions the skill provides:
.claude/skills/incident-healer/SKILL.md
The description is how DinoAI decides when a skill is relevant, so keep it specific. Skill names must be unique — if two skills share a name, the first one discovered wins. Any additional files in the skill folder (runbooks, templates, scripts) become available to DinoAI once the skill is loaded.

How skills load per surface

In Copilot

Skills are discovered and loaded automatically. There’s nothing to configure — relevant skills are surfaced as you work.

In the agents

Skills are discovered automatically, but a Programmable / Slack / Bolt agent can only load them if its allowlist includes the load_skill_instructions tool.
Enabling skills for a Programmable Agent. Add load_skill_instructions to the agent’s tools.list. See the Tools Reference for the id and YAML Configuration for allowlist syntax.