VyreVYRE

Skills

Skills are reusable, domain-specific instruction sets that activate when you or the agent mentions a matching keyword or task type. They're the difference between a generic AI assistant and one that knows your domain deeply.

What are skills?

A skill is a folder containing:

  • SKILL.md — The main instruction file that tells Agent exactly how to handle a specific type of task.
  • examples/ — Reference implementations Agent can use for consistency.
  • resources/ — Templates, snippets, or documentation the skill references.

When Agent detects that a task matches a skill's trigger keywords (defined in the SKILL.md frontmatter), it automatically loads and follows that skill's instructions.

Skills vs Rules

Rules define what to do always. Skills define how to do specific things exceptionally well. A rule might say "write tests." A skill teaches the agent exactly how to write tests for your testing framework, with your conventions, using your existing test patterns as examples.

Creating skills

1

Create the skills directory

Create a .agents/skills/ directory inside your project or in your global Vyre config:

code
.agents/
  skills/
    react-component/
      SKILL.md
      examples/
      resources/
2

Write the SKILL.md file

The SKILL.md file has a YAML frontmatter section and a body section:

markdown
---
name: react-component
description: >
  Use this skill when asked to create a new React component.
  Triggers on: "create component", "new component", "build a component"
---

# React Component Skill

When creating a React component, always:
1. Use TypeScript with proper prop types
2. Co-locate the test file
3. Export from the component index
4. Follow the naming conventions in our design system
3

Add examples

Drop reference implementations in the examples/ folder. Agent will read these to understand your patterns:

code
examples/
  UserCard.tsx          ← example component
  UserCard.test.tsx     ← example test

Skill structure

SKILL.md frontmatter

The frontmatter defines when the skill activates:

yaml
---
name: api-endpoint          # unique identifier
description: >              # natural language description + trigger words
  When the user wants to create, modify, or debug API routes.
  Also triggers on: "REST endpoint", "API route", "server action"
---
Skill body

The body is a full markdown document with detailed instructions for Agent. Be explicit and specific:

markdown
# API Endpoint Skill

## Always
- Use Zod for request validation
- Return consistent error shapes
- Add JSDoc with the request/response types

## File locations
- Route handlers live in `src/app/api/`
- Shared types live in `src/types/api.ts`
- Middleware lives in `src/middleware/`

## Pattern to follow
See `examples/users-route.ts` for the canonical pattern.
Scripts directory

Add scripts/ to your skill for helper scripts that Agent can run as part of the skill:

code
skills/
  database/
    SKILL.md
    scripts/
      generate-migration.sh    ← Agent can run this
      seed-database.sh

Sharing skills

Skills are just folders — share them the same way you share code:

  • Commit to your repo — all team members automatically benefit.
  • Publish to the Skills Registry — share skills with the Vyre community (coming soon).
  • Import from URL — in Settings, add a GitHub URL to a skills folder to import it.

The most valuable skills are project-specific ones that encode your team's institutional knowledge. Think: "how we write tests here", "how we structure API routes here", "how we design database schemas here."

Previous
Rules
Customize
Next
Subagents
Customize