skills/assistant/agent-skills-manager/SKILL.md
Manage AI skills from the Ravn AI Toolkit via corvus CLI — install, update, remove, search, and configure skills for any project. Use when: (1) Installing AI skills into a project, (2) Updating installed skills to latest versions, (3) Browsing or searching available skills, (4) Configuring global or per-project skill sets, (5) Troubleshooting corvus setup. Triggers on: "install skills", "add skills", "update skills", "corvus", "skill manager", "browse skills", "set up AI rules".
npx skillsauth add ravnhq/ai-toolkit agent-skills-managerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manage Ravn AI Toolkit skills using the corvus CLI. Install, update, remove, and configure skills for any project without needing Bash knowledge.
Check if corvus is installed:
corvus --version
If not installed, run the bootstrap installer:
curl -fsSL https://raw.githubusercontent.com/ravnhq/ai-toolkit/main/install.sh | bash
After installation, restart the shell or source ~/.zshrc.
List all skills grouped by category:
corvus list
Search by keyword:
corvus search <keyword>
Preview a specific skill's details, rules, and dependencies:
corvus info <skill-name>
Interactive mode (recommended for first-time users) — launches a picker UI:
corvus
Direct install to the current project:
corvus install <skill-name> [<skill-name> ...]
Target flags — install Agent Skills under each product’s skills/ directory (Claude Code, Cursor), or under rules/ where that product only supports rules (OpenCode, Codex):
| Flag | Target |
|------|--------|
| --claude | .claude/skills (project — Claude Code Agent Skills) |
| --cursor | .cursor/skills (project — Cursor Agent Skills) |
| --opencode | .opencode/rules (project) |
| --codex | .codex/rules (project) |
| --global-claude | ~/.claude/skills (global) |
| --global-cursor | ~/.cursor/skills (global) |
| --global-opencode | ~/.config/opencode/rules (global) |
| --global-codex | ~/.codex/rules (global) |
corvus install --claude tech-react
corvus install --codex lang-typescript
corvus install --global-claude core-coding-standards
Recipe install — predefined skill sets for common stacks:
corvus install --recipe fullstack-ts
corvus install --recipe ios-swift
corvus install --recipe backend-api
Dependencies are resolved automatically. Use --no-deps to skip.
Pull latest toolkit and update all installed skills:
corvus update
corvus auto-checks for updates every 7 days and prompts when new versions are available.
Check installed versions vs latest:
corvus status
Remove a skill:
corvus remove <skill-name>
corvus remove --global <skill-name>
The .corvusrc file in the project root tracks installed skills and can be committed to git. Teammates can sync all project skills with:
corvus sync
Run diagnostics to verify installation, dependencies, and configuration:
corvus doctor
Print setup instructions for your shell:
corvus completions # auto-detect shell
corvus completions --shell zsh
corvus completions --shell bash
corvus completions --shell fish
Follow the printed instructions to add completions to your shell config. For fish, the output will guide you to create a completions file at ~/.config/fish/completions/corvus.fish.
~/.corvus/config)| Key | Default | Description |
|-----|---------|-------------|
| update_check | 7 | Days between auto-update checks (0 = disabled) |
| auto_deps | true | Automatically install dependency skills |
| global_skills | (empty) | Comma-separated list of global skills with versions |
.corvusrc)| Key | Description |
|-----|-------------|
| install_dir | Where skills are copied (e.g., .claude/skills, .cursor/skills) |
| skills | Comma-separated list of installed skills with versions |
Global skills apply to every project. Set personal defaults:
corvus install --global core-coding-standards lang-typescript
Project skills are project-specific additions. Stored in .corvusrc:
corvus install tech-react tech-drizzle
Both layers merge at runtime. Project versions take priority on conflicts.
| Recipe | Skills |
|--------|--------|
| fullstack-ts | lang-typescript, tech-react, tech-trpc, tech-drizzle, tech-vitest, design-frontend |
| ios-swift | swift-concurrency, liquid-glass-ios |
| backend-api | lang-typescript, tech-trpc, tech-drizzle, platform-testing |
Use this section when making changes to the corvus CLI itself (TypeScript source in cli-ts/).
Both must be kept in sync on every release:
| File | Field |
|------|-------|
| cli-ts/src/core/paths.ts | CORVUS_VERSION constant |
| cli-ts/package.json | "version" field |
cli-ts/src/.cd cli-ts && npm testcli-ts/src/core/paths.ts, propose the next version to the user (increment build number), and wait for approval:
"Current version is
0.1.0. Proposed next version:0.1.1. Approve?"
CORVUS_VERSION in paths.ts and "version" in package.json atomically.ruby scripts/skill_version.rb skills/assistant/agent-skills-manager/SKILL.md buildUser: "Install AI skills for my React + tRPC + Drizzle project"
Expected behavior: Run corvus install --recipe fullstack-ts in the project directory. This installs all 6 skills with their dependencies resolved automatically.
User: "Fix the TypeScript error in my API handler"
Expected behavior: Do not use this skill. Choose a more relevant skill like lang-typescript or tech-trpc.
corvus: command not found after installation.~/.local/bin is not in PATH, or shell was not restarted.source ~/.zshrc (or ~/.bashrc) or restart the terminal. If still missing, add export PATH="$HOME/.local/bin:$PATH" to your shell config.Registry not found when running install.corvus update to re-pull the repository cache at ~/.corvus/repo/.corvus status shows skills behind latest but update reports all up to date..corvusrc version numbers may be stale.corvus remove <skill> then corvus install <skill> to force a fresh install.testing
Transform user requests into detailed, precise prompts for AI models. Use when users say 'promptify', 'promptify this', 'rewrite this prompt', 'make this prompt better/more specific', or explicitly request prompt engineering or improvement of their request for better AI responses.
development
Generate a gallery of design variations for a UI component. Takes an existing component (referenced by name, pasted code, or screenshot) and produces N distinct rendered alternatives in a single comparison page. Use when exploring visual directions, generating mockups, comparing design approaches for a component, creating A/B candidates, or when anyone says "show me options" or "give me variations" for a UI element.
tools
Create custom QA agent personalities for project-specific testing needs. Guided builder that asks about the specialty, tools, and test scenarios, then generates a personality file and registers it in the QA config. Trigger on "create a QA personality", "add a custom test agent", "build a webhook tester", or when the user needs a project-specific QA agent. Also triggered by /qa-create-personality.
testing
Orchestrate QA agent workflows — spawn test agents in parallel, collect results, triage bugs, trigger the bug fixer, and generate QA reports. The main entry point for running a QA session. Trigger on "run QA", "start QA session", "test the PR", "orchestrate QA agents", or when the user wants to run multiple QA agents together. Also triggered by /qa-orchestrator.