Skills
The 29 skills SoreQen comes with, how they load, and how to add your own as a SKILL.md file.
A skill is a set of instructions for one kind of work. Some are always on; the rest load when a task needs them, so a task about a database never carries the instructions for designing a web page.
Always on
These twelve apply to every task.
| Skill | What it covers |
|---|---|
orient-repository | Understand the existing project before changing it. |
clarify-task | Turn the request into outcomes and acceptance criteria. |
plan-proportionally | A short plan for small changes, a detailed one for risky changes. |
follow-conventions | Use the repository's patterns before its own defaults. |
minimal-changes | Change only what the request needs, and keep it consistent. |
debug-from-evidence | Reproduce, form a hypothesis, confirm it, fix the root cause. |
validate-behavior | Run the narrowest useful checks first, then widen. |
edge-cases | Examine how the changed path can fail. |
security-active | Every change is also a security review of what it touches. |
dependency-hygiene | Use what the project already uses; add dependencies deliberately. |
git-safety | Never lose your work. |
communicate-result | Report what happened, from evidence. |
Loaded when a task needs them
| Skill | Loads for |
|---|---|
product-intent | Vague or user-facing requests: a new feature, app, flow or product. |
frontend-design | Any UI work: a website, an app screen, a dashboard, a component, a redesign. |
accessibility | Forms, navigation, dialogs, tables and other interface work. |
state-async | Fetching data, changing server state, uploads, streaming, anything on the network. |
data-schema | Database changes, stored formats, migrations, event schemas, API contracts. |
api-contracts | Adding or changing APIs, webhooks, SDKs or service boundaries. |
performance | Requested speed-ups, or changes to rendering, queries, bundles, caching or large data. |
observability | Background jobs, production services, integrations, payments, notifications. |
test-strategy | High-risk behaviour, regressions, critical workflows, weakly tested code. |
release-safety | Production configuration, feature flags, rollouts, upgrades. |
dependency-review | Adding, upgrading or removing a dependency. |
documentation | Changes to behaviour, setup, public interfaces, commands or configuration. |
deep-research | A question researched on the web, delivered as a report. |
motion-graphics-videos | Motion graphics videos: promos, launch videos, explainers. |
writing-and-planning | Anything people will read: emails, posts, announcements, proposals. |
documents | PDF, Word, PowerPoint and Excel files. |
skill-creator | Writing, installing or improving a skill. |
Turning skills on and off
soreqen skills
soreqen skills disable motion-graphics-videos
soreqen skills enable motion-graphics-videos
/skills shows the same list in a session. In the desktop app, Settings → Skills lists them all.
Your own skills
A skill is a folder with a SKILL.md file in it: front matter, then the instructions.
---
name: release-notes
description: Write release notes from the commits since the last tag.
---
Read the commits since the last tag with git log. Group them into
Added, Changed and Fixed, in plain language for the people who use
the product. Leave out internal refactors.Put yours in ~/.soreqen/skills/<name>/SKILL.md. Your own skills may also set always: true to apply to every task, or triggers and paths to load themselves for matching work.
A project can ship skills in .soreqen/skills/<name>/SKILL.md. Because whoever wrote the repository wrote them, a project's skills load only when SoreQen asks for them; they are never always on, and never load themselves.
The format is the same SKILL.md other coding agents use, so a skill written for one of them works here. You can also ask SoreQen to write one: the skill-creator skill handles it.