Skills are prompt templates that extend mini-a’s behaviour. They live in ~/.openaf-mini-a/skills/ and can be invoked with /<name> or $<name>.

# Invoke a skill in interactive mode
/<skill-name> arg1 arg2

# Load extra skill directories
mini-a extraskills=/path/to/shared-skills

Skill layouts:

  • ~/.openaf-mini-a/skills/<name>/SKILL.md
  • ~/.openaf-mini-a/skills/<name>.md

You can also drop downloaded skill packs in ~/.openaf-mini-a/skills/ as folders as long as each one contains SKILL.md (or skill.md). Inside folder skills, relative @file.md attachments resolve against the skill folder, and relative markdown links to .md files are inlined as extra reference content.

skill

Code Review Checklist

A structured skill that guides the model through a rigorous code review checklist covering correctness, security, and performance.

codereviewquality
Target: {{arg1}}

Conduct a structured code review of {{arg1}} using the following checklist:

## Correctness
- [ ] Logic is accurate and matches the stated intent
- [ ] Edge cases and error conditions are handled
- [ ] No off-by-one errors or null pointer risks

## Security
- [ ] No hard-coded secrets or credentials
- [ ] Inputs are validated and sanitized
- [ ] Authentication and authorisation checks are present where needed
- [ ] No SQL/command injection risks

## Performance
- [ ] No unnecessary loops or N+1 queries
- [ ] Data structures are appropriate for the access pattern
- [ ] Expensive operations are cached where suitable

## Maintainability
- [ ] Code is readable and self-explanatory
- [ ] Functions are small and single-purpose
- [ ] Tests exist for critical paths

Report findings with file name, line number, severity, and suggested fix.
/code-review-checklist src/payments/
skill

Explain Code

Explains a piece of code, algorithm, or module in plain English. Suitable for onboarding or documentation generation.

docslearningonboarding
Target: {{arg1}}

Explain the code at {{arg1}} as if teaching a developer who is new to this
codebase but experienced with programming in general.

Structure your explanation as follows:
1. **One-line summary** — what this code does
2. **Context** — where it fits in the broader system
3. **Key concepts** — any algorithms, patterns, or domain terms
4. **Walk-through** — step-by-step explanation of the main logic
5. **Gotchas** — anything surprising or non-obvious
/explain-code src/algo/kd-tree.js
skill

Refactor Assistant

Suggests targeted refactoring improvements for a file or function. Preserves behaviour while improving readability and structure.

coderefactorquality
Target: {{arg1}}

Refactor {{arg1}} to improve readability, maintainability, and structure
without changing observable behaviour.

Apply these principles where applicable:
- Extract long functions into smaller, named helpers
- Replace magic numbers and strings with named constants
- Remove dead code and redundant comments
- Simplify complex conditionals
- Improve variable and function names

For each change, explain the motivation.
Present the refactored code followed by a diff summary.
/refactor src/legacy/parser.js
skill

README Generator

Generates a comprehensive README.md for a project from its source files and structure.

docsmarkdownonboarding
Inspect the project in the current directory and generate a comprehensive
README.md with the following sections:

1. **Project name and one-line description**
2. **Features** — bullet list of key capabilities
3. **Prerequisites** — required tools and versions
4. **Installation** — copy-paste install commands
5. **Usage** — the most common commands with examples
6. **Configuration** — key environment variables or config files
7. **Contributing** — brief contribution guide
8. **License**

Base all content on the actual code and existing documentation.
Do not invent features that are not present.
/generate-readme
skill

SQL Query Explainer

Explains and optimises a SQL query. Identifies potential performance issues and suggests improvements with an execution plan analysis.

sqldatabaseperformance
SQL query:
{{arg1}}

1. Explain what this query does in plain English.
2. Identify potential performance issues (missing indexes, full-table scans,
   N+1 subquery patterns, non-sargable predicates).
3. Suggest an optimised version with comments explaining each change.
4. List the indexes that would most improve this query's performance.
/sql-explain