Loading...
Loading...
Found 2,778 Skills
Warning system for identifying potentially malicious software distribution repositories
AI-powered skill discovery tool. Used when users ask "how to implement X", "find a skill for X", or "is there a skill with X functionality".
Load codebase context by analyzing structure and README. Use when starting a new session.
Draft and submit one high-quality Nexus idea for a Propose / ProposalScout dispatch action. Use when the action prompt names skill nexus-proposal-scout or route ProposalScout.
Install all AntiGravity lazy package skills at once. Load when saying "Install all" or "Install all AntiGravity lazy packages".
Use when checking live Capy task or PR state through Brave, Computer Use, or a Capy browser panel.
Usar al pedir implementar, desarrollar o ejecutar trabajo referenciado por una historia de usuario o tarea. Solo debe usarse si la historia o tarea se encuentra en estado `Ready`. Activar tambien cuando el usuario mencione "ejecutar tareas", "codificar", "desarrollar la US", "trabajar en el TK" o cualquier variante que implique escribir codigo para una historia o tarea ya especificada.
Track tasks and issues using the bd CLI. Use for task management, sprint planning, dependency tracking, and project organization. Replaces TodoWrite.
Run a comprehensive pull request review using multiple specialized agents. Each agent focuses on a different aspect of code quality, such as comments, tests, error handling, type design, and general code review. The skill aggregates results and provides a clear action plan for improvements. Triggers include "review PR", "analyze pull request", "code review", and "PR quality check".
Create atomic user-approved commits with `feat`/`fix`/`chore` titles and finalise branch merge/cleanup with tracking sync. Triggers: commit changes, split commits, finalise branch, commit message.
This skill should be used when the user asks to "finish a feature", "merge feature branch", "complete feature", "git flow feature finish", or wants to finalize and merge a feature branch into develop.
Before ANY destructive, irreversible, or high-impact action, pause and surface a clear checklist of what's about to happen. This includes: file deletions, database changes, production deployments, mass updates, permission changes, or anything that can't easily be undone. Require explicit confirmation before proceeding. Never auto-execute dangerous operations.