skill-catalog

Maintain a central registry of skills with dependencies and trigger phrases.

29|12|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/matteotitta/genesys-skills --skill skill-catalog-matteotitta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-catalog
Source: https://github.com/matteotitta/genesys-skills/tree/main/skills/meta/catalog/skill-catalog
Command: npx skills add https://github.com/matteotitta/genesys-skills --skill skill-catalog-matteotitta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of skill discovery and dependency management within a large library of 168+ GTM primitives, ensuring that users and the orchestrator can reliably locate and chain the correct tools.

Core Features & Use Cases

  • Central Registry: Maintains a comprehensive index of all skills, their trigger phrases, and review gates.
  • Dependency Resolution: Tracks chaining metadata to ensure workflows are executed in the correct order.
  • Use Case: When a user asks what skills are available for outbound prospecting, this catalog provides the exact list of relevant skills and their required inputs.

Quick Start

Invoke the skill catalog to display a list of all available skills and their current status.

Frequently Asked Questions about skill-catalog

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

FAQPage Schema
How do I manage skill dependencies and routing metadata in a GTM catalog?

A skill catalog resolves workflow dependencies by maintaining a central registry of trigger phrases, review gates, and chaining metadata to ensure workflows execute in the correct order.

What is the best way to locate outbound prospecting skills in a large registry?

Querying a central skill registry retrieves the exact list of relevant outbound prospecting skills, their trigger phrases, and their required inputs.

How does dependency resolution work for orchestrating chained workflows?

Dependency resolution for orchestrating chained workflows works by tracking metadata records in a central registry, allowing an orchestrator agent to validate routing decisions and ensure correct execution order.

Do I need a specific directory structure to generate and validate skill metadata?

Generating and validating skill metadata requires access to the skill directory structure to accurately index dependencies, trigger phrases, and chaining data.

Can I use a central registry to discover available skills across 168+ GTM primitives?

You can use a central registry to discover available skills across 168+ GTM primitives, ensuring reliable tool location and dependency chaining for users and the orchestrator.