claude-copilot: Command for Claude Code

Skills Manager

Browse, search, and manage reusable skills via the cc CLI.

Overview

Skills are SKILL.md files discovered from configured directories:

• Project skills: .claude/skills/ (project-local, highest priority)
• Global skills: ~/.claude/skills/ (machine-level)
• Knowledge repo: configured via cc config set paths.knowledge_repo

Step 1: List Available Skills

cc skill list

This shows all discovered skills with name, description, tags, and source (project/global).

---

Step 2: Search Skills

cc skill search "<keywords>"

Example:

cc skill search "testing patterns"
cc skill search "auth security"

---

Step 3: Inspect a Skill

cc skill get <name>

Example:

cc skill get testing-patterns

---

Step 4: Create a New Skill

To add a skill, create a SKILL.md file in the appropriate directory:

# Project skill (committed to git)
mkdir -p .claude/skills/<category>
# Then write .claude/skills/<category>/SKILL.md

# Global skill (machine-level, all projects)
mkdir -p ~/.claude/skills/<category>
# Then write ~/.claude/skills/<category>/SKILL.md

SKILL.md format:

---
name: skill-name
description: One-line description used for search and discovery
tags: [tag1, tag2]
triggers:
  filePatterns: ["**/*.test.ts"]
  keywords: ["testing", "jest"]
---

# Skill Name

[Skill content here — guidelines, patterns, examples]

---

Step 5: Find Relevant Skills by Keyword

Search for skills relevant to the current task:

cc skill search "auth security"
cc skill search "testing"

---

Step 6: Load a Skill in Claude

Use @include to inject a skill into the current session:

@include .claude/skills/<category>/SKILL.md

Skills are plain prose files — the model reads them directly via @include or by running cc skill get <name> and reading the output.

---

File Organization

.claude/skills/
├── testing/
│   └── SKILL.md
├── patterns/
│   └── SKILL.md
└── security/
    └── SKILL.md