113 lines
3.5 KiB
Markdown
113 lines
3.5 KiB
Markdown
---
|
||
name: ck-find-skills
|
||
description: >
|
||
Discovers and recommends relevant skills from the skills catalog.
|
||
Activate when user says 'what skills are available', 'find a skill for', 'which skill should I use',
|
||
'list all skills', 'search skills', or 'what can you do'. Accepts task descriptions
|
||
and domain keywords to match against the skills index.
|
||
---
|
||
|
||
## Overview
|
||
Queries the skills catalog (skills_index.json) to surface relevant skills for a given task. Returns skill names, descriptions, and activation triggers to help users discover the right tool.
|
||
|
||
## When to Use
|
||
- User is unsure which skill applies to their task
|
||
- Exploring what capabilities are available in the current installation
|
||
- Building a workflow and need to identify which skills to chain
|
||
- Verifying a skill exists before referencing it in a plan
|
||
|
||
## Don't Use When
|
||
- User already knows which skill they want (just activate it directly)
|
||
- Creating a new skill (use ck-skill-creator instead)
|
||
- Searching for non-skill files in the codebase (use file search tools)
|
||
|
||
## Steps / Instructions
|
||
|
||
### 1. Locate the Skills Index
|
||
|
||
The skills catalog is stored at:
|
||
```
|
||
# Antigravity global install:
|
||
~/.gemini/antigravity/skills/skills_index.json
|
||
|
||
# Workspace install:
|
||
.agent/skills/skills_index.json
|
||
```
|
||
|
||
### 2. Parse the Index
|
||
|
||
The `skills_index.json` structure:
|
||
```json
|
||
{
|
||
"skills": [
|
||
{
|
||
"name": "ck-scout",
|
||
"description": "Explores codebase structure...",
|
||
"category": "core-workflow",
|
||
"triggers": ["explore codebase", "understand project", "map the code"]
|
||
}
|
||
]
|
||
}
|
||
```
|
||
|
||
### 3. Search Strategy
|
||
|
||
**By keyword match:**
|
||
- Extract keywords from user's task description
|
||
- Match against `name`, `description`, and `triggers` fields
|
||
- Return top 3–5 matches with relevance reasoning
|
||
|
||
**By category:**
|
||
```
|
||
core-workflow: brainstorm, planning, code-review, debug, fix, git, scout, research
|
||
development: frontend-*, backend-*, web-*, databases, devops
|
||
specialized: ai-artist, ai-multimodal, agent-browser, media-processing, shader
|
||
orchestration: ccs-delegation, skill-creator, find-skills
|
||
```
|
||
|
||
**By task type:**
|
||
| User goal | Recommended skill |
|
||
|-----------|------------------|
|
||
| Start a new feature | ck-brainstorm → ck-planning |
|
||
| Fix a bug | ck-debug → ck-fix |
|
||
| Review code | ck-code-review |
|
||
| Build UI | ck-frontend-design → ck-frontend-development |
|
||
| Set up auth | ck-better-auth |
|
||
| Generate images | ck-ai-artist |
|
||
| Analyze images/docs | ck-ai-multimodal |
|
||
| Automate browser | ck-agent-browser |
|
||
| Build MCP server | ck-mcp-builder |
|
||
| Process video/audio | ck-media-processing |
|
||
| Deploy infrastructure | ck-devops |
|
||
|
||
### 4. Format the Response
|
||
|
||
```markdown
|
||
## Skills Found for: "[user query]"
|
||
|
||
### Best Match
|
||
**ck-[name]** — [one-line description]
|
||
Activate with: "[trigger phrase]"
|
||
|
||
### Also Relevant
|
||
- **ck-[name2]** — [description]
|
||
- **ck-[name3]** — [description]
|
||
|
||
### Suggested Workflow
|
||
[If task needs multiple skills, show the chain]
|
||
ck-scout → ck-planning → ck-frontend-development → ck-web-testing
|
||
```
|
||
|
||
### 5. Handle No Match
|
||
|
||
If no close match:
|
||
1. Suggest the closest partial match
|
||
2. Recommend ck-skill-creator to build a new skill
|
||
3. Suggest using ck-research to investigate the topic first
|
||
|
||
## Notes
|
||
- skills_index.json is the authoritative catalog; do not modify it here
|
||
- Skill discovery queries should be fast — read index once, match in memory
|
||
- When multiple skills apply, recommend a workflow chain rather than a single skill
|
||
- New skills added via ck-skill-creator are automatically added to the index
|