registry.query

Search Betty registries for skills, agents, and commands with filtering.

2|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/epieczko/betty --skill registry-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: registry.query
Source: https://github.com/epieczko/betty/tree/main/skills/registry.query
Command: npx skills add https://github.com/epieczko/betty --skill registry-query

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

As the number of skills, agents, and commands grows, finding the right tool for a specific task becomes challenging. This Skill provides a powerful, programmatic way to search and filter Betty registries, enabling dynamic discovery and automation.

Core Features & Use Cases

  • Multi-Registry Search: Query skills, agents, commands, and hooks registries for comprehensive discovery.
  • Advanced Filtering: Filter by name, version, status, tags, capabilities, and domain with optional fuzzy matching for flexible searches.
  • Flexible Output: Get results in JSON for programmatic use, human-readable table for CLI, or compact list formats.
  • Use Case: A developer needs to find all active skills related to "API validation". They can use registry.query with --tag api --status active to quickly get a list of relevant skills, their descriptions, and commands, streamlining their workflow.

Quick Start

Find all active skills tagged 'api' and display as a table

python3 skills/registry.query/registry_query.py skills --tag api --status active --format table

Frequently Asked Questions about registry.query

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

FAQPage Schema
How do I search across multiple registries for skills and commands?

Registry.query searches Betty registries for skills, agents, commands, and hooks in a single operation. Query by name, version, status, tags, domain, and capability across multiple registries simultaneously, returning results in JSON, table, or compact formats for programmatic use or CLI display.

Can I filter registry search results by tags and status?

Yes, registry.query applies advanced filtering by name, version, status, tags, capabilities, and domain with optional fuzzy matching. Filter active skills tagged with specific domains (e.g., `--tag api --status active`) to quickly identify relevant tools matching your workflow requirements.

What output formats does registry search support?

Registry.query returns results in three flexible formats: JSON for programmatic integration and automation, human-readable table for CLI inspection, and compact list format for quick scanning. Choose the format that fits your downstream use case—integration, display, or processing.

How can I automate discovery of skills in my CLI workflows?

Registry.query enables dynamic discovery and CLI autocompletion by querying registries programmatically. Use JSON output to integrate search results into automation scripts, enabling your tools to dynamically locate and reference skills, agents, and commands without manual catalog maintenance.

Does registry search support fuzzy matching for flexible queries?

Yes, registry.query includes optional fuzzy matching for flexible searches beyond exact name matches. This allows you to find skills and commands even when you don't know the exact name, returning close pattern matches across all registries.