Back to browse

CherryHQ/cherry-studio

create-skill

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.

82CollectingWrites filesRuns scripts
See how to use itView GitHub source
npx skills add https://github.com/CherryHQ/cherry-studio --skill ".agents/skills/create-skill"
Automated source guideDocumentationStandard source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded documentation guide: create-skill

Create a new skill in .agents/skills// following the workflow defined in .agents/skills/README.md.

npx skills add https://github.com/CherryHQ/cherry-studio --skill ".agents/skills/create-skill"
Check the pinned source

The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.

414 source words · 14 usable sections

Best fit

  • Use when the user wants to create/add a new skill, or mentions creating a skill from scratch.

Documentation workflow

Read create-skill through these 4 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

Workflow

Before creating anything, ask the user:

SKILL.md · Workflow
Skill name: What should the skill be called? (lowercase, digits, hyphens only, e.g., gh-create-pr, prepare-release)Description: What should this skill do? Include specific trigger contexts (e.g., "Use when user asks to create PRs")Is this a public skill?: Should it be synced to .claude/skills/ for shared use? (default: no, private only)
02

Step 1: Gather Intent

Before creating anything, ask the user:

SKILL.md · Step 1: Gather Intent
Skill name: What should the skill be called? (lowercase, digits, hyphens only, e.g., gh-create-pr, prepare-release)Description: What should this skill do? Include specific trigger contexts (e.g., "Use when user asks to create PRs")Is this a public skill?: Should it be synced to .claude/skills/ for shared use? (default: no, private only)
03

Step 2: Read Guidelines

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

SKILL.md · Step 2: Read Guidelines
Always read .agents/skills/README.md before creating a new skill to ensure compliance with the current workflow.

Documentation checklist

Verify each item before delivery

The source section “Workflow” has been checked.

The source section “Step 1: Gather Intent” has been checked.

The source section “Step 2: Read Guidelines” has been checked.

The source section “Step 3: Create Skill Structure” has been checked.

Static permission evidence

Inspect the exact source lines that triggered a signal

These are source excerpts matched by deterministic rules, not findings of malicious behavior, safety, or actual execution.

medium · write-files

SKILL.md · L24

Create the following directory structure:

The documentation asks the agent to create, modify, or delete local files.

medium · exec-script

SKILL.md · L55

pnpm skills:sync

The documentation asks the agent to run terminal commands or scripts.

medium · exec-script

SKILL.md · L64

Run the validation command:

The documentation asks the agent to run terminal commands or scripts.

medium · write-files

SKILL.md · L88

| Private | `.agents/skills/` | No | Just create the folder |

The documentation asks the agent to create, modify, or delete local files.

Choose a different workflow

When another Skill is the better fit

create-skill

Create new marketing skills for the mktg playbook. Use when the agent needs to add a new capability, someone says 'create a skill', 'new skill', 'add a marketing skill', 'extend the playbook', 'I need a skill for X', 'build a skill', 'make a skill for Y', or 'add capability for Z'. Also use when someone wants to capture a marketing workflow they just did into a reusable skill, or when they say 'turn this into a skill'. Reads the skill contract, generates SKILL.md with correct frontmatter and str

A separate implementation from MoizIbnYousaf/marketing-cli; compare its source, maintenance signals, and permission requirements.

Open source detail

biopython

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

A separate implementation from K-Dense-AI/scientific-agent-skills; compare its source, maintenance signals, and permission requirements.

Open source detail

markdown-mermaid-writing

Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.

A separate implementation from K-Dense-AI/scientific-agent-skills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does the create-skill source document cover?

Create a new skill in .agents/skills// following the workflow defined in .agents/skills/README.md.

How do I install create-skill?

The source record exposes this install command: npx skills add https://github.com/CherryHQ/cherry-studio --skill ".agents/skills/create-skill". Inspect the command and pinned source before running it.

Which permission-related actions were detected?

Static rules flagged write-files, exec-script in the source; the page lists the matching lines and excerpts.

Repository stars
49,062
Repository forks
4,672
Quality
82/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

82/100
Documentation26/30
Specificity25/25
Maintenance18/20
Trust signals13/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

create-skill by MoizIbnYousaf

Create new marketing skills for the mktg playbook. Use when the agent needs to add a new capability, someone says 'create a skill', 'new skill', 'add a marketing skill', 'extend the playbook', 'I need a skill for X', 'build a skill', 'make a skill for Y', or 'add capability for Z'. Also use when someone wants to capture a marketing workflow they just did into a reusable skill, or when they say 'turn this into a skill'. Reads the skill contract, generates SKILL.md with correct frontmatter and str

biopython by k-dense-ai

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

markdown-mermaid-writing by k-dense-ai

Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.

fastapi-expert by jeffallan

Use when building high-performance async Python APIs with FastAPI and Pydantic V2. Invoke to create REST endpoints, define Pydantic models, implement authentication flows, set up async SQLAlchemy database operations, add JWT authentication, build WebSocket endpoints, or generate OpenAPI documentation. Trigger terms: FastAPI, Pydantic, async Python, Python API, REST API Python, SQLAlchemy async, JWT authentication, OpenAPI, Swagger Python.

brand-landingpage by wshobson

Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens —

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 2 min

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:

---
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: 
    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:

pnpm skills:check

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

Step 6: Summary

Present the user with:

  • Created files
  • Validation result
  • Next steps (how to use the skill)

Naming Rules

  • Use lowercase letters, digits, and hyphens only
  • Prefer short, action-oriented names (e.g., gh-create-pr)

Public vs Private Skills

TypeLocationSyncRequires
Private.agents/skills/NoJust create the folder
PublicBothYesAdd to public-skills.txt + run pnpm skills:sync

Commands Reference

# Validate skill structure
pnpm skills:check

# Sync public skills to Claude
pnpm skills:sync

Constraints

  • Never create skills outside .agents/skills/<skill-name>/
  • Always run pnpm skills:check before completing
  • Public skills require both adding to public-skills.txt AND running pnpm skills:sync
  • If the skill-creator skill is available, you may use it for advanced skill development (evals, iterations), but this skill handles the basic creation workflow.
Skill path
.agents/skills/create-skill/SKILL.md
Commit SHA
dda7cc99d730
Repository license
AGPL-3.0
Data collected