Skills and commands

When to use a skill

A skill describes a task the agent can repeat, such as reviewing accessibility or preparing release notes. It should explain when to use it, the steps to follow, and what a useful result contains.

Keep project-wide conventions in AGENTS.md. Use a skill for a particular workflow.

Create a small skill

For project-local discovery, create .agents/skills/review-accessibility/SKILL.md in your project. Use a matching skill name in its frontmatter:

---
name: review-accessibility
description: Review a changed screen for basic accessibility issues.
---

Read the changed screen and its existing components.
Check labels, keyboard navigation, focus states, and text contrast.
List concrete issues with affected files and suggested fixes.
Do not change files unless asked.

In a session for that project, ask the agent to use review-accessibility. Confirm it found the skill before relying on its output. If discovery fails, check the folder name, filename, and frontmatter, then start a fresh session.

Use commands

Type / in the prompt composer to see commands available in your current session. Choose a command from the suggestions and supply any requested input. The available commands depend on your configuration and installed tools.

For a custom command, ask Virillio to help configure the workflow using the configuration supported by your installed version. Review the resulting user configuration before keeping it.

Review third-party skills

Read a skill before installing or using it. It may request commands or access to connected services. A skill is guidance, not an exemption from your permissions or review process.