skills-discovery

Skills Discovery

You can extend your capabilities by discovering and installing portable AI skills from a registry or repository. Skills provide specialized knowledge, tools, and techniques for specific technologies, frameworks, and domains.

When to Use

First, check if an installed skill matches the task. If not, search the registry—specialized skills may exist that you haven't installed yet.

Before starting any non-trivial task, ask yourself:

1. Do I have a skill for this? → Use it
2. Might one exist that I don't have? → Search the registry

Search proactively when:

• The task involves specific technologies, frameworks, or file formats
• You're about to do something where best practices matter (testing, deployment, APIs, documentation)
• The domain is specialized (PDF processing, data pipelines, ML workflows)
• You notice yourself about to give generic advice where expert patterns would help

Also search when users explicitly ask to find, install, or manage skills.

Discovery Workflow

Use the registry API for search when one is available:

curl "<registry-url>/api/skills?q=QUERY&limit=20&offset=0"

Parameters:

• q: Search query (e.g., "frontend", "python", "pdf")
• limit: Results per page (max 100)
• offset: Pagination offset

Response structure:

{
  "skills": [
    {
      "id": "...",
      "name": "skill-name",
      "namespace": "@owner/repo/skill-name",
      "sourceUrl": "https://github.com/...",
      "description": "...",
      "author": "...",
      "installs": 123,
      "stars": 45
    }
  ],
  "total": 100,
  "limit": 10,
  "offset": 0
}

Search Strategies

The registry indexes skill names, descriptions, and tags. Construct queries that match how skill authors describe their work.

Query construction:

• Use 1-3 specific terms (too broad = noise, too narrow = misses)
• Prefer widely-used terminology over project-specific jargon
• Technology + task often outperforms either alone
• If results are poor, broaden or try synonyms