Repository navigation
Creating Custom Skills
Josemalyson Oliveira edited this page Jun 27, 2026
·
1 revision
Learn how to create your own skills for the Custom Skills collection.
Every skill follows this structure:
skill-name/
├── SKILL.md # Main definition
├── references/ # Supporting documents
│ ├── reference-1.md
│ └── reference-2.md
└── templates/ # Ready-to-use starting points (optional)
└── template.html
---
name: skill-name
description: >
Trigger phrases that activate this skill.
Be specific about when it should activate.
Use multiple phrases separated by commas.
---
# Skill Name
## Overview
What this skill does and why it exists.
## When to Use
- Use case 1
- Use case 2
- Use case 3
## Trigger Phrases
- "Phrase 1"
- "Phrase 2"
- "Phrase 3"
## Workflow
### Phase 1: Name
**Objective:** What this phase achieves
**Steps:**
1. Step 1
2. Step 2
3. Step 3
### Phase 2: Name
**Objective:** What this phase achieves
**Steps:**
1. Step 1
2. Step 2
3. Step 3
## Output
What the skill produces.
## References
- `references/file.md` — DescriptionThe frontmatter defines how the skill is discovered and activated:
---
name: my-skill
description: >
This is the trigger text.
The agent reads this to know when to activate.
---- Be specific — "Compare X approaches" is better than "help me"
- Use natural language — Match how users actually ask
- Include multiple phrases — Cover variations
- Avoid ambiguity — Don't overlap with other skills
Reference documents provide on-demand knowledge for the skill:
# Reference Title
## Section 1
Content...
## Section 2
Content...
## Examples
```code
example code
### Best Practices
- **Clear titles** — Know what you're looking at
- **Structured content** — Use headings, lists, tables
- **Code examples** — Show, don't just tell
- **Cross-references** — Link to other documents
---
## Templates
Templates provide ready-to-use starting points:
### HTML Templates
```html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Template</title>
<style>
/* CSS here */
</style>
</head>
<body>
<!-- Content here -->
<script>
// JS here
</script>
</body>
</html>
#!/usr/bin/env bash
set -euo pipefail
# Configuration
CONFIG_VAR="${CONFIG_VAR:-default}"
# Functions
function main() {
echo "Starting..."
# Main logic
}
function cleanup() {
echo "Cleaning up..."
}
# Trap
trap cleanup EXIT
# Run
main "$@"Before submitting:
- Test trigger phrases — Verify the skill activates
- Test workflow — Follow all phases
- Test output — Verify the output is correct
- Test edge cases — What happens with invalid input?
git clone https://github.com/josemalyson/custom-skills.git
cd custom-skillsmkdir my-skill
# Create SKILL.md, references/, templates/Add your skill to:
- Skills Overview table
- Project Structure tree
- Use the PR template
- Include checklist
- Reference related issues
- Use clear headings (H1 for title, H2 for sections)
- Include code blocks with language tags
- Use tables for structured data
- Keep lines under 100 characters
- Follow existing code style
- Add comments for complex logic
- Use meaningful names
- Structure with clear sections
- Include examples and anti-patterns
- Cross-reference other documents
See existing skills for reference:
- Agent-Code-Detective — Complex multi-phase workflow
- HTML-First — Template-heavy skill
- K8s-Investigation — Script-based skill
- Learning-Trail — Validation-focused skill
- Pre-Commit-Quality-Gate — Configuration-heavy skill
Last updated: June 2026