Library
87,622 resources from 11 public sources. 54 checked by hand. The rest are indexed automatically and not reviewed.
Results
-
vercel-cli-with-tokens
SkillsDeploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
Source for vercel-cli-with-tokens (opens github.com) npx skills add vercel-labs/agent-skills -
vercel-optimize
SkillsUse for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core…
Source for vercel-optimize (opens github.com) npx skills add vercel-labs/agent-skills -
web-design-guidelines
SkillsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Source for web-design-guidelines (opens github.com) npx skills add vercel-labs/agent-skills -
writing-guidelines
SkillsReview docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
Source for writing-guidelines (opens github.com) npx skills add vercel-labs/agent-skills -
brainstorming
SkillsYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
-
diagnosing-superpowers
SkillsUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
-
dispatching-parallel-agents
SkillsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
-
executing-plans
SkillsUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
-
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
-
receiving-code-review
SkillsUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
-
requesting-code-review
SkillsUse when completing tasks, implementing major features, or before merging to verify work meets requirements
-
subagent-driven-development
SkillsUse when executing implementation plans with independent tasks in the current session
-
systematic-debugging
SkillsUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
-
test-driven-development
SkillsUse when implementing any feature or bugfix, before writing implementation code
-
using-git-worktrees
SkillsUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
-
using-superpowers
SkillsUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
-
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
-
writing-plans
SkillsUse when you have a spec or requirements for a multi-step task, before touching code
-
writing-skills
SkillsUse when creating new skills, editing existing skills, or verifying skills work before deployment
-
ask-matt
SkillsAsk which skill or flow fits your situation. A router over the skills in this repo.
-
code-review
SkillsReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".
-
codebase-design
SkillsShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
-
diagnosing-bugs
SkillsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
-
domain-modeling
SkillsBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
Indexed entries aren't reviewed or tested by InnerVault. Details come straight from each source. Anything that can reach your accounts, files or browser can do damage, so read the source before you install it.