demeter-skills

Map task context to the appropriate Claude skill in the Demeter registry.

Updated Dec 7, 2025
One-click install
npx skills add https://github.com/emilyantosch/demeter --skill demeter-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demeter-skills
Source: https://github.com/emilyantosch/demeter/tree/main/.claude/skills
Command: npx skills add https://github.com/emilyantosch/demeter --skill demeter-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as the central registry for Demeter, helping you discover available Claude skills, understand skill conventions, and quickly find the right skill for a task.

Core Features & Use Cases

  • Skill Discovery: Browse available skills and access their usage notes.
  • Conventions Overview: See naming, format, and activation guidelines.
  • Quick Reference: Jump to specific skill docs like architecture.md.

Quick Start

Use the registry to view all available skills in this project and open the architecture.md entry for details.

Frequently Asked Questions about demeter-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover and find the right Claude skill for my project?

Skill discovery maps your task context to available Claude skills in the Demeter registry. The registry centralizes all skills with their metadata, naming conventions, and activation rules, letting you quickly locate the right skill by matching your project structure and task requirements.

What skill naming and metadata conventions should I follow?

Demeter enforces standardized skill metadata and YAML frontmatter naming to enable automatic skill activation. Following these conventions—including consistent naming patterns, metadata format, and documentation structure—ensures your skills are discoverable and activate correctly based on task context.

How does automatic skill activation work based on project structure?

Automatic skill activation routes tasks to the appropriate skill by interpreting your project structure, design patterns, and CLI/TUI concerns. The registry analyzes these architectural signals to match incoming tasks with the right skill without manual selection.

Can I use the registry to understand architecture patterns and design conventions?

Yes. The registry documents conventions for naming, format, and activation guidelines alongside skill definitions. You can reference architecture.md and other skill documentation to understand design patterns and how to structure projects for optimal skill discovery.

What if I need to browse all available skills quickly?

The registry provides a centralized view of all available Claude skills in your project with usage notes and quick-reference links. You can jump directly to specific skill documentation like architecture.md to understand capabilities and activation conditions.