Claude-skill-registry demeter-skills
Central skill registry for demeter project. Use to discover available skills, understand skill conventions, and find the right skill for a task.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/demeter-skills" ~/.claude/skills/majiayu000-claude-skill-registry-demeter-skills && rm -rf "$T"
manifest:
skills/data/demeter-skills/SKILL.mdsource content
Demeter Skills
This directory contains skills that Claude auto-activates based on task context.
Available Skills
| Skill | File | Purpose |
|---|---|---|
| Architecture | architecture.md | Project structure and design patterns |
Skill Conventions
File Format
Each skill file uses YAML frontmatter:
--- name: skill-name description: What this skill does. When to use it. allowed-tools: Tool1, Tool2 # Optional --- # Skill Content
Naming
- Use lowercase with hyphens:
my-skill-name - Max 64 characters
- Be specific:
notrust-error-handlingerrors
Description Guidelines
The
description field drives auto-activation. Include:
- What the skill does
- When Claude should use it
- Trigger keywords users would mention
# Good description: Debug Rust compile errors and borrow checker issues. Use when encountering lifetime errors, ownership problems, or type mismatches. # Bad description: Helps with Rust
Adding New Skills
- Create
in this directoryskill-name.md - Add YAML frontmatter with
andnamedescription - Write skill content in markdown
- Update the table in this file
Skill Discovery
Claude automatically discovers skills based on:
- Task relevance
- Description keywords
- Request context
No explicit invocation needed—write good descriptions and Claude will find them.