Skip to content
Back to skills

Create Skill

ASecurity

Create a new agent skill for Shannon. Every new skill must follow the Agent Skills specification and match the conventions established by existing skills.

  • 11 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 7, 2026
documentation

Security analysis

A100/100

Scanned September 7, 2026

npx -y skills add shannonshell/shannon --skill create-skill --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Create Skill?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Create Skill
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/shannonshell-create-skill/badge)](https://www.skillsdirectory.com/skills/shannonshell-create-skill)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: create-skill
description:
  "Create a new agent skill. Use when creating a new skill for the project."
---

# Create Skill

Create a new agent skill for Shannon. Every new skill must follow the Agent
Skills specification and match the conventions established by existing skills.

## When This Skill Applies

Any time a new skill needs to be created.

## Process

1. **Read the specification.** Fetch `https://agentskills.io/specification` to
   review the current Agent Skills format.

2. **Read every existing skill.** Read all `SKILL.md` files in
   `skills/*/SKILL.md` to understand the project's conventions, tone, and level
   of detail.

3. **Create the skill directory and file.** The skill is a directory in
   `skills/<name>/` containing a `SKILL.md` file. `.claude/skills` and
   `.codex/skills` are symlinks to that root directory. The directory name must
   match the `name` field in the frontmatter.

4. **Follow the spec.** The `SKILL.md` must have:
   - YAML frontmatter with `name` (lowercase, hyphens, max 64 chars) and
     `description` (what it does and when to use it)
   - Markdown body with instructions

5. **Match existing conventions.** Based on the current skills:
   - Keep it to a single `SKILL.md` (no `scripts/`, `references/`, `assets/`
     unless truly needed)
   - Include a "When This Skill Applies" section
   - Include a "Process" or "Steps" section with numbered steps
   - Reference specific paths in the Shannon repo where relevant
   - Keep under 500 lines

## Naming Rules

From the spec:

- Lowercase letters, numbers, and hyphens only
- Must not start or end with a hyphen
- No consecutive hyphens
- Max 64 characters
- Directory name must match the `name` field

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…