skills y frameworks de la comunidad para creadores de agentes de IA | AI Agent Skills
Colección de AI Agent Skills instalables para workflows de desarrollo de community en Claude Code, Cursor y Windsurf.
Esta colección está pensada para quienes construyen agentes de IA apoyándose en el ecosistema comunitario. Reúne herramientas prácticas, skills reutilizables y frameworks para prototipado, depuración, evaluación e integración. El objetivo es pasar de la experimentación a producción con flujos más claros y menos soluciones aisladas.
Page-Level Review Standard
This Page Is a Curated Decision Surface, Not Just a Themed List
A collection page should not just add more cards to the screen. It should explain why these skills belong together, how the next step moves into installation and validation, and which path should continue the decision afterwards.
Reviewed On
2026-04-17
Maintained By
Killer-Skills editorial review within the recovery-focused authority queue.
Verification
Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.
Primary Audience
High-intent users who roughly know the direction and need a faster path to an installable shortlist.
Three Minimum Standards For This Collection
- A collection page must narrow users into a better shortlist instead of flattening more repositories onto the screen.
- The next click should continue into installation docs, CLI validation, or a better-fit solution page instead of resetting back to a broad directory.
- This page only becomes a real first-party judgment surface when its selection logic, maintenance posture, and delivery path are all visible.
Primary Install Bridge
Pick One Skill, Then Take the Install Path
This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.
The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory
Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.
Reviewed on 2026-04-17 against community workflow fit, installation clarity, operator handoff, and builder usefulness. This page is now positioned as an install-first community entry point instead of a broad community roundup.
We prioritize this page because community-intent users usually need a shortlist they can install, validate, and carry into real builder loops quickly.
Trust Signals
- Entries are chosen for practical community workflow value such as reuse, experimentation, debugging support, and installability.
- Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
- The page is curated for repeatable builder execution, not for vague community keyword coverage or generic repository popularity.
Grouping Logic
- Lead with tools that can enter a community-driven workflow without adding heavy setup ambiguity.
- Keep the shortlist compact enough for quick comparison while still covering reuse, debugging, experimentation, and workflow support.
- Use installation as the bridge from community discovery into validated daily execution.
Maintenance & Review
Last Reviewed
2026-04-17
Cadence
Re-check when install flow, maintainer posture, or community workflow relevance changes upstream; otherwise review monthly.
Maintained By
Killer-Skills editorial review within the recovery-focused authority queue.
Verification
Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.
Execution Examples
How These Skills Work Together In Practice
Install one community skill first
Use this page when you want one community-tested skill that can enter real builder work without turning evaluation into another endless repo crawl.
1. Open the installation docs before opening more community repositories.
2. Choose one skill that best supports reuse, debugging, experimentation, or workflow speed.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
4. Only after the base path works, expand the setup across the wider team workflow.
Reduce open-source selection drag
Treat the collection as an editorial filter when you need community-adjacent tools that improve builder confidence without overcomplicating the stack.
1. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated path before scaling it to more repos, flows, or teammates.
4. Document the chosen community workflow baseline after the first clean rollout.
Babysit a GitHub pull request after creation by continuously polling CI checks/workflow runs, new review comments, and mergeability state until the PR is ready to merge (or merged/closed). Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and stop only when user help is required (for example CI infrastructure issues, exhausted flaky retries, or ambiguous/blocking situations). Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.
The project-guidelines-example skill provides a template for project-specific skills, leveraging Next.js, FastAPI, and Claude API. It helps developers manage complex projects and improve coding efficiency.
Set up and manage the Sentry development environment using devenv. Handles fresh setup, updating existing environments, starting dev services, and troubleshooting. Use when asked to set up sentry, setup dev environment, get sentry running, start dev server, devenv setup, devservices not working, sentry wont start, or any development environment issue.
Run initial NanoClaw setup. Use when user wants to install dependencies, authenticate messaging channels, register their main channel, or start the background services. Triggers on setup, install, configure nanoclaw, or first-time setup requests.
Check out a GitHub pull request for review in this repo, either in the current directory or in a new isolated worktree at ../yaak-worktrees/pr-<PR_NUMBER>. Use when asked to run or replace the old Claude check-out-pr command.
Creates or updates README files following Ankane-style template for Ruby gems. Use when writing gem documentation with imperative voice, concise prose, and standard section ordering.
If This Page Is Close, Keep Narrowing With Related Authority Collections
Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.
This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.
¿Para qué flujos de trabajo están diseñadas estas colecciones?
Estas colecciones están diseñadas para automatización de flujos, procesos, documentos, datos y pilas de habilidades reutilizables.
¿Cómo se diferencia una colección del directorio principal?
El directorio es mejor para búsqueda directa, mientras las colecciones ayudan a encontrar habilidades complementarias agrupadas por flujo completo.
¿Puedo instalar estas colecciones para Claude Code o Cursor?
Sí. Las habilidades de estas colecciones generalmente funcionan en Claude Code, Cursor, Windsurf y otros entornos mediante instalación unificada.
Additional Next Paths
Use These Additional Paths If You Need One More Step To Narrow The Decision
These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.
