Collection de AI Agent Skills installables pour les workflows développeur agentic platforms orchestration dans Claude Code, Cursor et Windsurf.
Cette page est centrée sur les plateformes d'agents IA et les outils d'orchestration, et non sur une simple liste de serveurs. Les projets sélectionnés aident les équipes à concevoir des skills d'agents, coordonner plusieurs agents et piloter l'exécution dans des environnements applicatifs réels. Ils permettent de définir les périmètres de capacités, planifier des flux multi-étapes, superviser les exécutions et maintenir une exploitation cohérente à mesure que le système grandit. Certains outils proposent des adaptateurs compatibles MCP, mais l'objectif principal reste le développement d'agents au niveau plateforme et leur orchestration. Pour les équipes qui passent du prototype à la production, cette sélection met en avant des options concrètes en matière de structure, de contrôle et de fiabilité.
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.
A practical bridge into command behavior, sync rules, and what operators should validate after installation.
CLI documentation proves the site has operational depth beyond discovery wrappers.
A scenario page for users who already know the workflow problem they need to solve.
High-intent solution pages are safer recovery surfaces than broad skill detail expansion.
Write or update documentation for the Inkeep docs site (agents-docs package). Use when: creating new docs, modifying existing docs, introducing features that need documentation, touching MDX files in agents-docs/content/. Triggers on: docs, documentation, MDX, agents-docs, write docs, update docs, add page, new tutorial, API reference, integration guide.
Use when we want to turn a just-finished Formax workflow (e.g. commands, overlays, tools, hooks, permissions, UI parity) into a reusable Codex Skill under .codex/skills, including scaffolding, guardrails, and the minimum test checklist.
Use when preparing a Formax code handoff: selecting files, generating repomix bundles, and writing a high-quality prompt for WebGPT or another coding agent with clear constraints and validation scope.
Use when adding or modifying generator scripts that write files; keeps generated artifacts out of docs/ and aligns script defaults with ownership paths plus CI gate updates.
nanobot-ts is the TypeScript version of nanobot, an ultra-lightweight personal AI assistant framework.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Manage git worktrees for parallel AI agent development. Use this when asked to create, list, open, close, or merge worktrees, or when working with wt-* commands.
Guided workflow for diagnosing and fixing harness bugs in deployed instances
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 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.