skill-registry

Indexes project skills into a searchable registry for subagent delegation.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/arayaroma/ether --skill skill-registry-arayaroma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-registry
Source: https://github.com/arayaroma/ether/tree/main/.claude/skills/skill-registry
Command: npx skills add https://github.com/arayaroma/ether --skill skill-registry-arayaroma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Orchestrators delegating work to subagents often lack an accurate, up-to-date view of which skills exist in a project, leading to missed capabilities or stale summaries. This Skill maintains a local index of every available skill so tasks can be matched against real SKILL.md files instead of digested descriptions. ## Core Features & Use Cases - Skill Resolution: Scans project roots (skills/, .claude/skills/) first, then the global root (~/.claude/skills/), with project-scoped skills winning over global duplicates. - Registry Generation: ether skill-registry refresh writes .ether/skill-registry.md, a Markdown table of Skill, Trigger/description, Scope, and Path, plus a cache file. - Dry-Run Inspection: ether skill-registry list [--json] shows what would be resolved without writing files, with machine-readable output available. - Use Case: After adding a new go-testing skill to .claude/skills/, run the refresh command so an orchestrator can hand a subagent the exact SKILL.md path rather than a lossy summary. ## Quick Start Ask the agent to run ether skill-registry refresh and then list the available skills so it can match your task to the right SKILL.md file.

Frequently Asked Questions about skill-registry

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

FAQPage Schema
How do I discover which skills are available in a Claude Code project?▼

Run `ether skill-registry list` to print every resolved skill with its name, description, scope, and SKILL.md path. Use `ether skill-registry refresh` to write the same index to `.ether/skill-registry.md` for orchestrators to read.

How do I pass skills to a subagent without losing information?▼

Pass the exact SKILL.md file paths from the registry and instruct the subagent to read those files directly. This keeps the original skill as the source of truth instead of relying on compact summaries that lose author intent.

What happens when a skill exists in both project and global scopes?▼

The project version wins. Resolution scans project roots (`skills/`, `.claude/skills/`) before the global root (`~/.claude/skills/`), so a skill present in both scopes keeps the project copy.

Why is my skill missing from the registry output?▼

Skills named `_shared`, `skill-registry`, or matching `ether-*` are never indexed because they are internal plumbing or orchestrator-managed. Also run `ether skill-registry refresh` after adding, renaming, or moving skills to update the index.

Can I inspect the skill registry without writing files?▼

Yes, `ether skill-registry list` performs the same resolution as refresh but prints the result instead of writing `.ether/skill-registry.md`. Add `--json` for machine-readable output suitable for scripting.