Skip to main content
Prompts teach the AI about your app one session at a time. A skill makes that knowledge permanent. QA Wolf loads SKILL.md files in every autonomous creation, guided creation, and outlining session, so the AI starts with your context instead of asking you to repeat it.
These are skills stored in your QA Wolf workspace for QA Wolf’s AI. To install QA Wolf skills in an external coding agent, use the coding-agent plugin guide.

​
What a skill looks like

A skill is a Markdown file with two parts: frontmatter that names and describes it, and a body with the knowledge itself.

​
What belongs in a skill

Good skill content is anything you would otherwise repeat across many prompts:
  • Domain vocabulary and what each term maps to in the UI
  • Environment quirks, such as which login method works and which test users are seeded
  • Team conventions, such as structuring flow headers around AAA
  • Links to deeper documentation the AI should fetch when it becomes relevant
Keep each skill focused on one topic. Knowledge that matters to a single flow belongs in that flow’s prompt or header, not in a skill.

​
Where skills live

A skill can live anywhere in your workspace. The best practice is to give each SKILL.md its own folder:

​
How each surface uses skills

Autonomous creation. The quality of an unattended run depends on the context you front-load. A skill carries the standing context, so your prompt only needs to describe the flow itself. Guided creation. You stop re-explaining the same background at every step. The AI already knows your domain terms and conventions, so short prompts land correctly. Outlining. The agent explores your app already knowing what the features are called and which areas matter, which produces more accurate flow stubs.
Last modified on September 16, 2026