Collection de AI Agent Skills installables pour les workflows développeur assistant developers dans Claude Code, Cursor et Windsurf.
Cette page s’adresse aux développeurs qui utilisent des assistants IA dans des workflows de livraison réels. Elle met en avant des skills pratiques, des intégrations et des outils companion pour le code, la qualité de documentation, les checks de release et la coordination d’équipe. MCP peut être présent en support, mais le cœur reste le workflow développeur.
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.
Move from assistant-tool comparison into install flow, validation checklist, and first command path before branching out.
Open the Install PathOnce 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.
A use-case page for users searching for repeatable automation patterns instead of one-off tools.
Workflow automation demand is easier to satisfy with curated intent clusters than with flat directory coverage.
A high-trust collection that lets the site lead with official and strongly verified ecosystems instead of random long-tail repos.
Trusted-brand collections are the fastest way to rebuild authority after pruning.
Reviewed on 2026-04-17 against developer workflow fit, install clarity, operational usefulness, and day-to-day assistant value. This page is now positioned as an install-first comparison surface instead of a vague tooling list.
We prioritize this page for users who already know they need an AI assistant layer in daily development. The right move is to shortlist a tool, install it, validate the path, and only then expand into broader workflow decisions.
Use this page when you want one assistant layer that can help in real development, not just another tool to compare endlessly.
Use the collection as an editorial filter when you need assistants that improve output quality without overcomplicating the stack.
pair is the process layer for AI-assisted development. It gives your AI assistant the context, guidelines, and skills to work the way your team works.
Manages feature flag lifecycle: creation, activation, deactivation, and cleanup. Follows feature-flags guidelines. Idempotent: detects existing flags, shows current state, offers lifecycle actions rather than re-creating.
Debug container agent issues. Use when things arent working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.
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.
Add WhatsApp as a channel. Can replace other channels entirely or run alongside them. Uses QR code or pairing code for authentication.
Read and extract text from PDF files — documents, reports, contracts, spreadsheets. Use whenever you need to read PDF content, not just when explicitly asked. Handles local files, URLs, and WhatsApp attachments.
Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator
Un workflow Git pour l'agent AI est un ensemble de règles et d'outils pour gérer le code et la collaboration
🔬 AI-powered medical paper writing toolkit — from PubMed search to Word export, all inside VS Code
更新 ROADMAP.md 狀態。觸發：roadmap、路線、規劃、里程碑。
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.
A high-trust collection that lets the site lead with official and strongly verified ecosystems instead of random long-tail repos.
Trusted-brand collections are the fastest way to rebuild authority after pruning.
A workflow-first collection that explains why related skills belong together and what job they solve.
Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.
A platform-specific collection for one of the clearest demand clusters in the product ecosystem.
Platform collections let the site recover with narrower, more trustworthy topical intent.
A clean surface for editor-specific demand with explicit workflow intent.
Editor-specific demand should land on curated surfaces, not random repo coverage.
This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.
Ces collections sont conçues autour de l'automatisation de flux, processus, documents, données et piles de compétences réutilisables.
Le répertoire est meilleur pour la recherche directe, tandis que les collections regroupent des compétences complémentaires autour d'un flux complet.
Oui. Les compétences de ces collections fonctionnent généralement dans Claude Code, Cursor, Windsurf et d'autres environnements via un flux d'installation unifié.
These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.
A workflow-first collection that explains why related skills belong together and what job they solve.
Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.
Comparison pages are one of the best ways to prove independent judgment and avoid the mirror-site posture.
Comparisons make Killer-Skills look editorial-first instead of repo-wrapper-first.