# Create Skill

Create a new skill in the current repository.

- Repository: https://github.com/CherryHQ/cherry-studio (53164 stars)
- Category: AI and agents
- License: AGPL-3.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add CherryHQ/cherry-studio --skill create-skill -g -a claude-code -y`
Codex: `npx skills add CherryHQ/cherry-studio --skill create-skill -g -a codex -y`
Cursor: `npx skills add CherryHQ/cherry-studio --skill create-skill -g -a cursor -y`
Gemini CLI: `npx skills add CherryHQ/cherry-studio --skill create-skill -g -a gemini-cli -y`

## Description

Create a new skill in the current repository. Use when the user wants to create/add a new skill, or mentions creating a skill from scratch. This skill follows the workflow defined in .agents/skills/README.md and helps scaffold, validate, and sync new skills.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Create Skill

Create a new skill in `.agents/skills/<skill-name>/` following the workflow defined in `.agents/skills/README.md`.

## Workflow

### Step 1: Gather Intent

Before creating anything, ask the user:

1. **Skill name**: What should the skill be called? (lowercase, digits, hyphens only, e.g., `gh-create-pr`, `prepare-release`)
2. **Description**: What should this skill do? Include specific trigger contexts (e.g., "Use when user asks to create PRs")
3. **Is this a public skill?**: Should it be synced to `.claude/skills/` for shared use? (default: no, private only)
4. **Test cases** (optional): Does the user want to set up evals for this skill?

If the user provides partial info (e.g., just a name), proceed with reasonable defaults and ask to confirm.

### Step 2: Read Guidelines

Always read `.agents/skills/README.md` before creating a new skill to ensure compliance with the current workflow.

### Step 3: Create Skill Structure

Create the following directory structure:

```
.agents/skills/<skill-name>/
└── SKILL.md
```

**SKILL.md template:**

```markdown
---
name: <skill-name>
description: <description>
---

# <Skill Name>

[Instructions for the skill]
```

**Frontmatter fields:**
- `name`: Skill identifier (lowercase, digits, hyphens)
- `description`: When to trigger (what the skill does + specific contexts)

### Step 4: Sync (if public)

If the user wants a **public skill**, before validation:

1. Add the skill name to `.agents/skills/public-skills.txt` (one per line, no inline comments)
2. Run sync:
   ```bash
   pnpm skills:sync
   ```

This creates a symlink at `.claude/skills/<skill-name>/` pointing to `.agents/skills/<skill-name>/`.

**Note**: `pnpm skills:check` primarily validates public skills (those in `public-skills.txt`) and also verifies related governance files, so you must sync first before validating.

### Step 5: Validate

Run the validation command:

```bash
pnpm skills:check
```

If there are issues, fix them and re-run.

The rest: https://github.com/CherryHQ/cherry-studio/blob/HEAD/.agents/skills/create-skill/SKILL.md