agent-skills-manager
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".
Best use case
agent-skills-manager is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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".
Teams using agent-skills-manager should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agent-skills-manager/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-skills-manager Compares
| Feature / Agent | agent-skills-manager | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# AI Skills Manager (corvus) Manage Ravn AI Toolkit skills using the `corvus` CLI. Install, update, remove, and configure skills for any project without needing Bash knowledge. ## Prerequisites Check if corvus is installed: ```bash corvus --version ``` If not installed, run the bootstrap installer: ```bash curl -fsSL https://raw.githubusercontent.com/ravnhq/ai-toolkit/main/install.sh | bash ``` After installation, restart the shell or `source ~/.zshrc`. ## Workflow ### 1. Browse Available Skills List all skills grouped by category: ```bash corvus list ``` Search by keyword: ```bash corvus search <keyword> ``` Preview a specific skill's details, rules, and dependencies: ```bash corvus info <skill-name> ``` ### 2. Install Skills **Interactive mode** (recommended for first-time users) — launches a picker UI: ```bash corvus ``` **Direct install** to the current project: ```bash 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) | ```bash 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: ```bash corvus install --recipe fullstack-ts corvus install --recipe ios-swift corvus install --recipe backend-api ``` Dependencies are resolved automatically. Use `--no-deps` to skip. ### 3. Update Skills Pull latest toolkit and update all installed skills: ```bash corvus update ``` corvus auto-checks for updates every 7 days and prompts when new versions are available. ### 4. Manage Installed Skills Check installed versions vs latest: ```bash corvus status ``` Remove a skill: ```bash corvus remove <skill-name> corvus remove --global <skill-name> ``` ### 5. Team Collaboration The `.corvusrc` file in the project root tracks installed skills and can be committed to git. Teammates can sync all project skills with: ```bash corvus sync ``` ### 6. Health Check Run diagnostics to verify installation, dependencies, and configuration: ```bash corvus doctor ``` ### 7. Shell Completions Print setup instructions for your shell: ```bash 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`. ## Configuration ### Global Config (`~/.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 | ### Project Config (`.corvusrc`) | Key | Description | |-----|-------------| | `install_dir` | Where skills are copied (e.g., `.claude/skills`, `.cursor/skills`) | | `skills` | Comma-separated list of installed skills with versions | ## Skill Scoping **Global skills** apply to every project. Set personal defaults: ```bash corvus install --global core-coding-standards lang-typescript ``` **Project skills** are project-specific additions. Stored in `.corvusrc`: ```bash corvus install tech-react tech-drizzle ``` Both layers merge at runtime. Project versions take priority on conflicts. ## Available Recipes | 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 | ## Maintaining corvus Use this section when making changes to the corvus CLI itself (TypeScript source in `cli-ts/`). ### Version Locations 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 | ### Workflow for Every corvus Change 1. Make the code changes in `cli-ts/src/`. 2. Run tests: `cd cli-ts && npm test` 3. Read the current version from `cli-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?" 4. Update `CORVUS_VERSION` in `paths.ts` and `"version"` in `package.json` atomically. 5. Bump the skill version: `ruby scripts/skill_version.rb skills/assistant/agent-skills-manager/SKILL.md build` 6. Commit, push to fork, update PR. ## Examples ### Positive Trigger User: "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. ### Non-Trigger 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. ## Troubleshooting ### corvus Command Not Found - Error: `corvus: command not found` after installation. - Cause: `~/.local/bin` is not in PATH, or shell was not restarted. - Solution: Run `source ~/.zshrc` (or `~/.bashrc`) or restart the terminal. If still missing, add `export PATH="$HOME/.local/bin:$PATH"` to your shell config. ### Skills Not Installing - Error: `Registry not found` when running install. - Cause: The local toolkit cache is missing or corrupted. - Solution: Run `corvus update` to re-pull the repository cache at `~/.corvus/repo/`. ### Outdated Skills After Update - Error: `corvus status` shows skills behind latest but `update` reports all up to date. - Cause: The `.corvusrc` version numbers may be stale. - Solution: Run `corvus remove <skill>` then `corvus install <skill>` to force a fresh install.
Related Skills
type-system-audit
Audit a repository for type-system weaknesses using recent bug-fix commits as hard evidence. Produces prioritized findings tied to specific commits showing which types allowed real bugs. Use when: reviewing type safety, auditing types, analyzing type bugs. Triggers on: type audit, type system review, audit types, type safety audit.
ts-linter
Set up and enforce a strict, production-grade ESLint configuration for TypeScript projects, then systematically fix all linting issues. Use this skill whenever the user asks to add a linter or ESLint, enforce code quality rules, fix linting errors, clean up code style, or add type-aware linting. Trigger on: "lint", "eslint", "code quality", "static analysis", "strict linting", "make it stricter", "make the code stricter", "add better rules", "clean up the codebase", "enforce standards", "fix all the warnings", or "ShadCN lint errors". Handles detection, config generation, dependency installation, auto-fix, and manual remediation. Do NOT use for Biome or Rome projects, Prettier-only formatting, non-TypeScript/JavaScript projects, writing custom ESLint rules or plugins, husky/lint-staged/pre-commit hook setup, or when the user just wants to run an existing linter without changing its configuration.
transcript-notes
Convert meeting transcript .txt files into structured .md notes with metadata, TL;DR, key topics, action items, and quotes. Use when processing raw transcripts into formatted notes. Triggers on: "process transcript", "generate notes from transcript", "transcript to notes", "/transcript-notes".
test-plan-gen
Generate professional QA Test Plan documents (.docx or .pdf) from a structured interview. Trigger on "create/write a test plan", "I need a test plan", "prepare QA documentation", /testplan, or when a user uploads a PRD/requirements and wants a test plan generated.
test-case-gen
Generate, evaluate, audit, and normalize QA test cases to RAVN standards. Trigger on "generate/write/create test cases", "evaluate/score my test cases", "audit my test suite", "review test coverage", "normalize/reformat test cases", or when a user wants test design help. Also triggered by /testcases.
tech-react
React 19 patterns for components, hooks, Server Components, and data fetching. Use when writing React components, managing state with hooks, implementing Suspense boundaries, optimizing renders with proper memoization, or building Server/Client component hierarchies.
tech-drizzle
Drizzle ORM typesafe schema design, relational queries, prepared statements, migrations, and transactions. Use when working with Drizzle ORM, writing database queries, managing migrations, or optimizing query performance with prepared statements.
tech-android
Android and Kotlin development patterns — Compose, architecture, coroutines, Room, navigation, Hilt. Use when building Android apps, writing Jetpack Compose UI, or reviewing Android-specific code.
swift-concurrency
Swift Concurrency patterns — async/await, actors, tasks, Sendable conformance. Use when writing async/await code, implementing actors, working with structured concurrency, or ensuring data race safety.
rewrite-commit-history
Rewrite a feature branch's commit history into clean conventional commits that tell a progressive, linear story. Handles backup, soft reset, and atomic recommit. Use when: (1) Cleaning up messy WIP commits before PR, (2) Reorganizing commits into logical units, (3) Converting commits to conventional commit format. Triggers on: "rewrite history", "clean up commits", "rewrite commits", "conventional commits", "squash and rewrite", "reorganize commits".
qa-personality-builder
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.
qa-orchestrator
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.