Agent skill · AI & Agents

creating-skills

Use when creating new Claude Code skills or improving existing ones - ensures skills are discoverable, scannable, and effective through proper structure, CSO optimization, and real examples

AgentWorkforcegithub.com/AgentWorkforceGitHub ↗
claude-codeApache-2.0
Install
npx skills add AgentWorkforce/relay --skill creating-skills-skill --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 15 KB
Bundled scripts: none
Path: .claude/skills/creating-skills-skill/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 784
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Creating Skills ## Overview **Skills are reference guides for proven techniques, patterns, or tools.** Write them to help future Claude instances quickly find and apply effective approaches. Skills must be **discoverable** (Claude can find them), **scannable** (quick to evaluate), and **actionable** (clear examples). **Core principle**: Default assumption is Claude is already very smart. Only add context Claude doesn't already have. ## When to Use **Create a skill when:** - Technique wasn't intuitively obvious - Pattern applies broadly across projects - You'd reference this again - Others would benefit **Don't create for:** - One-off solutions specific to single project - Standard practices well-documented elsewhere - Project conventions (put those in `.claude/CLAUDE.md`) ## Required Structure ### Frontmatter (YAML) ```yaml --- name: skill-name-with-hyphens description: Use when [triggers/symptoms] - [what it does and how it helps] tags: relevant-tags --- ``` **Rules:** - Only `name` and `description` fields supported (max 1024 chars total) - Name: letters, numbers, hyphens only (max 64 chars). Use gerund form (verb + -ing) - Avoid reserved words: "anthropic", "claude" in names -

What's inside
Steps it walks through
  1. Overview
  2. When to Use
  3. Required Structure
  4. Frontmatter (YAML)
  5. Document Structure
  6. Degrees of Freedom
  7. Claude Search Optimization (CSO)
  8. Description Best Practices
  9. Keyword Coverage
  10. Naming Conventions
  11. Code Examples
  12. Choose Language by Use Case
  13. Good Example Checklist
  14. Example Template
Commands it runs
set -e  # Exit on error
if [ ! -f "config.json" ]; then
echo "Error: config.json not found" >&2
exit 1
fi
Script logic here
echo "Success"
exit 0
More from relay
All skills →
About this skill
What does the creating-skills skill do?

Use when creating new Claude Code skills or improving existing ones - ensures skills are discoverable, scannable, and effective through proper structure, CSO optimization, and real examples

How do I install it?

Run `npx skills add AgentWorkforce/relay --skill creating-skills-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From AgentWorkforce/relay, a repository with 784 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going