VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

/ak:find-skills

Discover and install skills

Discover and install Agent Skills when users ask for a capability that may already exist in the skills ecosystem.

01

Recognize Need

02

Route Installed Skills

03

Clarify Domain

04

Search CLI

Rule 01

Use local AgentKit routing before external discovery when the choice is among installed skills.

Rule 02

Specific search terms beat broad category words.

Rule 03

Present installable options with exact package names and links.

Rule 04

No result is not a dead end: help directly or suggest creating a custom skill.

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Recognize Need Trigger when the user asks how to do a specialized task, whether a skill exists, or how to extend capabilities.
  2. 2 Route Installed Skills If choosing between installed AgentKit skills, load domain-routing before using the external Skills CLI.
02

Work

Agent / skill execution

  1. 3 Clarify Domain Identify domain, concrete task, and whether the task is common enough that an installable skill likely exists.
  2. 4 Search CLI Run npx skills find with specific keywords, trying alternative terms such as deploy/deployment or PR/review when needed.
03

Verify

Gate, review, validation

  1. 5 Evaluate Results Prefer relevant packages from known sources, inspect the package name, capability fit, install command, and skills.sh link.
  2. 6 Present Options Show skill name, what it does, install command, and learn-more link in a concise user-facing recommendation.
04

Close

Report, handoff, artifact

  1. 7 Offer Install If the user wants it, install with npx skills add package -g -y, using the exact package found.
  2. 8 Fallback Gracefully When no match exists, say so, offer to help directly, and suggest creating a custom skill with npx skills init.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:find-skills [capability or task description]

Arguments

[capability or task description] Required

Capability to find

Describe the domain, task, framework, language, platform, and whether you want local routing, recommendations only, or installation after review. Do not include credentials, private source, or unrelated workspace details.

/ak:find-skills "Audit a Next.js checkout for accessibility and keyboard navigation"

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Find React help Recommended 
/ak:find-skills react performance
Use when:
The user asks how to make a React app faster and a reusable skill may already exist.
Expected:
Identifies React performance as the domain and task, runs a targeted Skills CLI search, then presents relevant matches with exact install commands and skills.sh links.
PR review skill 
/ak:find-skills pr review
Use when:
The user wants help with a specialized workflow such as pull request review.
Expected:
Searches with the PR review query, checks whether the result fits the requested workflow, and summarizes the skill name, purpose, install command, and learn-more link.
Changelog discovery 
/ak:find-skills changelog
Use when:
The user asks for tooling or a reusable workflow around creating changelogs.
Expected:
Treats changelog generation as a documentation or release-workflow capability, searches by the specific keyword, and recommends any relevant installable skill with package evidence.
No matching skill 
/ak:find-skills custom release ritual for our internal approval board
Use when:
The requested capability is niche or organization-specific and may not have a public skill.
Expected:
If targeted and alternative searches do not find a relevant skill, says no match was found, offers direct help, and suggests creating a custom skill with npx skills init for repeated work.

Handled Scope

  • Agent Skills ecosystem discovery
  • npx skills find/add/check/update command flow
  • Installed AgentKit domain routing
  • Capability-to-keyword translation
  • User-facing skill recommendation and installation handoff

Next