Contribute

Add a skill

Every skill is a Markdown file with frontmatter. The directory rebuilds itself from the files in this repo. Add yours and open a pull request.

Step 1

Fork the repo

Fork nimaaksoy/skills and clone it locally.

git clone https://github.com/<you>/skills.git
cd skills
npm install

Step 2

Scaffold a skill

Use the interactive scaffolder. It picks the right folder and frontmatter for you.

npm run new-skill

Or copy skills/_TEMPLATE/ into skills/<category>/<subcategory>/<slug>/ by hand.

Step 3

Write the SKILL.md

The body has six sections: Overview, When to use, Instructions, Examples, Resources, Notes & limitations, Changelog.

Keep the description under 200 characters and trigger-focused — the model uses it to decide whether to load the skill.

Step 4

Validate locally

npm run validate

name ≤ 64 chars; description ≤ 200 chars
category and subcategory exist in categories.yml
Folder path matches skills/<cat>/<sub>/<slug>/, slug is kebab-case
1–8 kebab-case tags
Body has at least one ## heading
No file over 5 MB; no nested SKILL.md

Step 5

Open a pull request

Push your branch and open a PR. CI runs the same validator. Read CONTRIBUTING.md for the full checklist.

SKILL.md template

---
name: Skill Name Here
description: One-sentence trigger description. Be specific about when this skill should be used. Max 200 characters. This field determines whether the model loads the skill.
dependencies: []

# Directory metadata (skills.nimaaksoy.com only — ignored by Claude)
category: business
subcategory: sales
tags: [outreach, b2b, cold-email]
author:
  name: Your Name
  url: https://yourlink.com
  github: yourhandle
license: CC-BY-4.0
version: 0.1.0
created: 2026-05-14
updated: 2026-05-14
---

# Skill Name Here

## Overview

One short paragraph: what this skill does and the situation it's built for. Write it so a contributor reading the directory understands the point in under 10 seconds.

## When to use this skill

- Trigger condition 1
- Trigger condition 2
- Trigger condition 3

## Instructions

Step-by-step guidance for the model. Be concrete. Reference any files in `resources/` by relative path.

1. First step.
2. Second step.
3. Third step.

## Examples

### Example 1 — short label

**Input:**
> User asks: "..."

**Expected behaviour:**
The skill should...

### Example 2 — short label

(another worked example)

## Resources

- `resources/<file>` — what it is and when to read it.

## Notes & limitations

- Known limitation 1
- Known limitation 2

## Changelog

- `0.1.0` — initial version.

Need a new category?

Open an issue using the Category proposal template before adding skills under it.

New issue