AI & agents · Building & coding
skill
/skill
Skill management and creation. Use for "create skill", "manage skills", "skill info", and "skill help".
For whom
- Author
- r3dlex ↗
- Repository
- oh-my-auggie ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Licence
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Skill management and creation. Use for "create skill", "manage skills", "skill info", and "skill help".
Triggers from the description
create skillmanage skillsskill infoskill help
Original author description
Skill management and creation. Use for "create skill", "manage skills", "skill info", and "skill help".
How it works
- Skill: skill
- When to Use
- OMA Skill Paths
- Commands
- Skill Creation Process
- Skill Quality Checklist
- Skill Naming
- Output Format
- Skill Templates
- Constraints
Original SKILL.md headings · 304 lines, 690 words
SKILL.md preview
---
name: skill
description: Skill management and creation. Use for "create skill", "manage skills", "skill info", and "skill help".
trigger: /oma:skill
---
## Skill: skill
Create, manage, and organize OMA skills.
## When to Use
- Creating new skills
- Editing existing skills
- Finding skills
- Understanding skill structure
- Skill maintenance
## OMA Skill Paths
OMA distinguishes three skill scopes with precedence (highest to lowest):
| Scope | Path | Read-Only |
|-------|------|-----------|
| **Project** | `.oma/skills/` | No |
| **User** | `~/.augment/plugins/marketplaces/oh-my-auggie/plugins/oma/skills-learned/` | No |
| **Built-in (plugin)** | `plugins/oma/skills/` | Yes |
Project-level skills take precedence over user-level; user-level takes precedence over built-in.
### Directory Structure
```
{skill-name}/
└── SKILL.md
```
### SKILL.md Format
```markdown
---
name: {skill-name}
description: {one-line description}
trigger: /oma:{skill-name}
allowed-tools: [Read, Glob, Bash, Edit, Write]
model: sonnet4.6
---
## Skill: {skill-name}
{body content}
```
## Commands
### List All Skills
```
/oma:skill list
```
### Get Skill Info
```
/oma:skill info {skill-name}
```
### Add Skill
```
/oma:skill add {skill-name}
```
### Edit Skill
```
/oma:skill edit {skill-name}
```
### Remove Skill
```
/oma:skill remove {skill-name}
```
**Note:** Use `remove`. `delete` is not a supported subcommand alias.
### Search Skills
```
/oma:skill search {query}
```
### Setup Skills
```
/oma:skill setup user
/oma:skill setup project
/oma:skill setup plugin
```
Initializes the skills directory for the given scope.
### Sync Skills
```
/oma:skill sync
/oma:skill sync {url}
```
Syncs all skills from configured remote sources, or installs a specific skill from a GitHub URL.
## Skill Creation Process
### 1. Identify Need
- What gap exists?
- What should this do?
- Who will use it?
### 2. Design Skill
- Name and trigger
- Description
- Body content
- Examples
### 3. Create Structure
```bash
mkdir -p plugins/oma/skills/{skill-name}
```
### 4. Write SKILL.md
- YAML frontmatter
- Clear description
- Usage examples
- Constraints
### 5. Test
```bash
/oma:skill info {skill-name}
/oma:{skill-name}
```
## Skill Quality Checklist
- [ ] Name is descriptive
- [ ] Trigger is memorable
- [ ] Description is clear
- [ ] Usage examples included
- [ ] Constraints documented
- [ ] Error cases handled
- [ ] Tested with real use
## Skill Naming
- Use lowercase
- No spaces (use hyphens)
- Descriptive but concise
- Unique across catalog
Good names:
- `code-review`
- `debug`
- `deploy`
Poor names:
- `the-code-reviewing-skill`
- `help-me-with-my-code`
## Output Format
```
## Skill: {name}
**Trigger:** /oma:{name}
**Description:** {description}
**Created:** {date}
### Usage
{how to use}
### Examples
```
/oma:{name} {example}
/oma:{name} {example}
```
### Files
- `plugins/oma/skills/{name}/SKILL.md`
```
## Skill Templates
Use the template that best matches the skill type.
### Template 1: Error Solution
Captures how to diagnose and fix a specific error or class of errors.
```markdown
---
name: {skill-name}
description: Diagnose and fix {error class}
trigger: /oma:{skill-name}
---
## Skill: {skill-name}
{full explanation of the error and solution}
## When to Use
{when this skill applies}
## Diagnosis Steps
1. {step}
2. {step}
## Fix
{how to resolve}
## Prevention
{how to avoid this error in the future}
```
### Template 2: Workflow
Captures a multi-step process for accomplishing a goal.
```markdown
---
name: {skill-name}
description: {one-liner}
trigger: /oma:{skill-name}
---
## Skill: {skill-name}
{high-level description}
## When to Use
{context when to invoke this}
## Steps
1. {step}
2. {step}
## Examples
```
/oma:{skill-name} {example}
```
## Constraints
{limits and edge cases}
```
### Template 3: Code Pattern
Captures a reusable code structure or idiom.
```markdown
---
name: {skill-name}
description: Apply {pattern name}
trigger: /oma:{skill-name}
allowed-tools: [Read, Glob, Grep, Bash, Edit, Write]
---
## Skill: {skill-name}
{full description of the pattern}
## When to Use
{context}
## Pattern
```{language}
{canonical example}
```
## Anti-Patterns
{what to avoid}
## Constraints
{limitations}
```
### Template 4: Integration
Captures how to connect to an external service or tool.
```markdown
---
name: {skill-name}
description: Integrate with {service/tool name}
trigger: /oma:{skill-name}
allowed-tools: [Bash, Read]
---
## Skill: {skill-name}
{what this integration does}
## Prerequisites
- {requirement}
- {requirement}
## Setup
{configuration steps}
## Usage
{how to use}
## Examples
```
{example commands}
```
## Troubleshooting
{common issues and fixes}
```
## Constraints
- One skill per directory
- SKILL.md required
- Unique names
- Document thoroughly
- Test before publishing
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · r3dlex/oh-my-auggie | 100 | Apache-2.0 |
| szarkans/multi | 100 | MIT |
| TheAlejo160/orchestra | 100 | MIT |
| peterbamuhigire/chwezi-sdlc-documentation | 90 | MIT |
Database snapshot: 13.11.2026 · package version ee63c3c3d6ef (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100skill-management
Create, update, and manage Claude Code skills. Use when working with SKILL.md files, slash commands, or extending Claude's capabilities. - 100manage-skills
Use when the user wants to find, install, or manage agent skills from skills.sh. Triggers on requests like "find a skill for", "install a skill", "browse skills", "what skills are available", or any mention of skills.sh. - 100gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment. - 90skillme
Find, install, and manage Skill Me skills from inside a conversation through the Skill Me connector. Use when the user asks for a Skill Me skill, asks what skills they have, wants skills suggested for a task, or wants to install or remove a skill or pack. - 100managing-skills
Manage reusable agent skills with the installed skill-manager CLI. Invoke only when the user explicitly asks to "manage skills" or clearly asks for help managing their agent skills, or when the user invokes `$managing-skills`. Do not invoke for requests that merely mention a… - 100skills
Manage agent skills using the npx skills CLI. Use when the user asks to "install a skill", "add a skill", "remove a skill", "list skills", "update skills", "find skills", "search for skills", or mentions "npx skills", skill management, or agent skill installation. Also trigger…