본문으로 건너뛰기
cccskills
무료GitHub에 공개

create-skill

Creates a new skill within the current repository, gathering its name and purpose before building the SKILL.md structure. It follows repository guidelines, runs validation, and optionally syncs skills for shared use through Claude.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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.

설치 방법 보기

이럴 때 유용합니다

  • Creating a new skill from scratch
  • Defining when an agent should use a skill
  • Syncing a skill for shared use through Claude
  • Validating a newly created skill structure

포함된 파일(1)

  • SKILL.md3.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Deciding whether a change needs a lasting decision record
  • Documenting bug fixes with significant tradeoffs
  • Preparing specifications for approval before implementation
CherryHQ/cherry-studio5.3만2026년 10월 19일 업데이트

Get answers about Cherry Studio from the installed version’s product information. The skill explains features, settings locations, and shortcuts, provides clickable navigation entries, and helps diagnose connection failures, configuration problems, and runtime errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Finding a feature or settings page
  • Checking supported providers and default shortcuts
  • Diagnosing connection failures and runtime errors
CherryHQ/cherry-studio5.3만2026년 10월 19일 업데이트

Operate the visible browser pane in a Cherry Studio conversation to navigate pages, click controls, fill forms, capture screenshots, and investigate browser issues. It can work with authenticated websites while checking page state and action outcomes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Navigate and operate an authenticated website
  • Fill forms and verify the resulting page state
  • Capture screenshots of a page or specific section
CherryHQ/cherry-studio5.3만2026년 10월 19일 업데이트

Operates native desktop apps through Cherry Studio Computer Use. It reads interface information, types, clicks, and captures windows, using fresh observations to choose actions and verify results within the permissions and capabilities available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Open a desktop app and inspect its interface
  • Enter text and click controls in an app
  • Capture a window when interface details are unclear
CherryHQ/cherry-studio5.3만2026년 10월 19일 업데이트

Develop and verify changes in a tracked Cherry Studio Electron instance, a running desktop app. Use real UI behavior, logs, and performance measurements to investigate problems, compare fixes, or test a pull request and report the results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Implement UI changes and verify them in the app
  • Reproduce bugs and inspect runtime logs
  • Compare performance before and after a fix
CherryHQ/cherry-studio5.3만2026년 10월 19일 업데이트

Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking key workflows before a release
  • Validating application behavior on a development branch
  • Running regression tests for a specific task
CherryHQ/cherry-studio5.3만2026년 10월 19일 업데이트

CherryHQ의 스킬 모두 보기

이 스킬의 문제 신고