AGENT SKILLS · ÉQUIPEMENT DE MISSION
Des Agent Skills utiles classés selon leur usage réel
Comparez les Skills vérifiés par fonction, contenu, installations et fiabilité de la source avant de les ajouter.
- PÉRIMÈTRE
- VÉRIFIÉ
- Skills
- 23 248
- dépôts
- 3589
- dernière synchronisation
- 4 nov. 2026
jasonjgardnerblockbench-texturing
Create and paint textures in Blockbench using MCP tools. Use when creating textures, painting on models, using brush tools, filling colors, drawing shapes, applying gradients, managing texture layers, or working with UV mapping. Covers pixel art texturing, procedural painting, and UV manipulation.
- Installations / 1h
- 1
- GitHub Stars
- 18
- Mis à jour
- 17 sept.
jasonjgardnerblockbench-use
Load before Blockbench MCP calls that create, modify, or export content. Discover the active format and tools, route to modeling, UV/texturing, animation, PBR, or Hytale guidance, and verify the requested result.
- Installations / 1h
- 1
- GitHub Stars
- 18
- Mis à jour
- 17 sept.
bsenec4-diagram
Generates C4 model architecture diagrams using Structurizr DSL (primary) or Mermaid C4 (fallback). Use when: user asks to "draw a diagram", "create a C4 diagram", "show architecture as a diagram", "generate architecture diagram", "document the system". DO NOT USE for code explanation or walkthroughs (use explain-code), class/sequence/ER diagrams (C4 is system-architecture only), or when a diagram is incidental to a code change — only when a C4 diagram is the primary deliverable.
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bseneclean-code
Use when writing new code, naming modules/files/functions/classes/variables, reviewing or refactoring code for readability, assessing/reducing complexity, deciding whether an abstraction belongs, or reviewing with CUPID. For behavior-preserving refactors within a function, class, or file, route to the refactoring/ sub-skill. Trigger on requests like "name this function", "is this a good variable name", "review this for clean code", "reduce complexity", "should I add a comment here", "should I ab
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bseneclojurescript
Write, review, debug, and configure ClojureScript code and projects. Use this whenever the user mentions ClojureScript, .cljs/.cljc files, shadow-cljs, figwheel, the CLJS compiler, JS interop from Clojure, Reagent/re-frame/Reagent-style UI code, or asks to convert JS/TS logic into ClojureScript. Also use it for questions about CLJS compiler options (:optimizations, :main, :npm-deps, :externs, etc.), consuming JS/npm libraries from CLJS, source maps, Google Closure Library usage, or the newer ^:a
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bsenecommunication
Analyze a real communication artifact (Slack/Teams message, email, meeting transcript, pitch or presentation draft, CV, or resume) and coach it sharper using seven rhetoric + structure techniques: ethos/logos/pathos, reframing tough questions, centering the other person, the Pyramid Principle, pattern interrupt, making ideas feel safe, and the cognitive-load through-line. Diagnose what works, what's missing, then rewrite. TRIGGER when: user wants to improve communication, "review my email/Slack/
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bsenedantotsu
Use this skill when the user wants to investigate a bug, defect, incident, or quality issue and find its root cause — including requests to run a "5 whys" analysis, write a postmortem, do a root-cause analysis (RCA), figure out why a bug reached production or slipped past code review/QA, set up a recurring defect-analysis routine, or run a daily/weekly quality-improvement (Kaizen) triage. Also known as the Dantotsu method (Sadao Nomura's Toyota-derived defect-analysis approach, adapted for softw
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bseneexplain-code
Explains code with C4 model diagrams, analogies, and step-by-step walkthroughs. Use when explaining how code works, teaching about a codebase, onboarding to architecture, or when the user asks "how does this work?", "explain this system", "walk me through this", "what does this code do?", "help me understand this", "show me the architecture", "explain this service", "how is this structured?", "trace the flow", "what happens when X calls Y?", or is new to a codebase and needs orientation. DO NOT
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bsenegit-hero
Git best practices — commit discipline, branching/history hygiene, safety, and CI/CD pipelines. Routes to git-guru (expert Q&A), gitmoji, and gitlab-dag sub-skills. TRIGGER when: commits (Conventional Commits, atomic commits, commit message format, commit hygiene, commit types, scope selection, breaking change), history (branch naming, rebase vs merge, clean git history, interactive rebase, history management), safety (force push safety, recover lost commits, reflog, reset), CI/CD (GitLab CI, pi
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bsenemikado-method
Enforce and guide the Mikado Method for large, graph-driven refactors where a single naive change cascades into many failing call sites. The skill enforces the full Mikado loop: goal → naive attempt → map prerequisites → revert → implement leaves → commit → repeat. TRIGGER when: user mentions Mikado Method, dependency untangling, circular dependencies, "breaking everything" on a refactor, change cascading across many files, ripple effects, large-scale legacy refactor with tight coupling, untangl
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bsenemonoids
Recognize and apply the monoid abstraction (binary associative operation + neutral element) in Clojure/ClojureScript code. Use whenever the user is combining, aggregating, merging, or reducing data — metrics and counters, event logs, config objects, or any reduce/fold/merge-with over a collection — even if they don't use the word "monoid". Also use when reviewing code that special-cases empty lists/collections, when discussing Map-Reduce or parallel aggregation (including pmap-based reduction),
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bseneocaml
Write, review, debug, and explain OCaml code and dune projects. Use whenever the user mentions OCaml, .ml/.mli files, dune, dune-project, opam, Alcotest, qcheck, shrinking, counterexamples, property-based testing, mutation testing, katas or exercises written in OCaml, or asks to convert JS/TS/PHP logic into OCaml. Trigger even if the user just pastes OCaml code with a compiler error and asks "what's wrong here", asks to set up a new dune project, or asks for the OCaml idiom for something they al
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bsenereview
Reviews current branch changes: reads the actual diff, produces structured feedback (Blockers / Concerns / Nits), asks targeted questions, then applies fixes on approval. TRIGGER when: user says "/review", "review this PR", "review my changes", "code review", "review the diff", "PR review", "review branch", "what do you think of my code", "look at my changes", "give me feedback on this". DO NOT USE when: user wants to understand what changed without requesting feedback; user asks for explanation
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bseneshow-me-the-code
Enforces one rule: every code change must be presented as a unified diff (diff -u format) with 3 lines of context. No exceptions, even one-liners. TRIGGER when: user requests a code modification — fix, refactor, update, replace, edit, patch, change, tweak, rename, rewrite, apply changes, modify this, edit the file, change this code, or explicitly asks for a diff — "show me the diff", "as a unified diff", "what changed", "show the patch", "/show-me-the-code". DO NOT USE when: producing a brand-ne
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
bsenesimple
Use this skill whenever writing new code, proposing a bugfix, reviewing a PR/diff, or discussing whether to add an abstraction, config layer, plugin system, or generic mechanism. Also trigger for architecture/design discussions, is this too complex" questions, or any point where Claude is about to suggest introducing a new abstraction layer. The core stance — code is written for humans to read, not as an artwork to admire — optimize for affordance (like a road sign, instantly readable) rather th
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 21 sept.
full-stack-skillsrust-api-design
Design Rust library APIs that follow the Rust API Guidelines — naming (C-CASE, C-CONV, C-GETTER), interop traits (C-COMMON-TRAITS, C-CONVERT, C-ITER, C-SERDE), predictability (C-INTUITIVE, C-CONST), flexibility (C-GENERIC, C-NEWTYPE, C-EXT), type safety (C-BOOL, C-NONZERO, C-WRAPPER, C-STR), dependability (C-PANIC, C-UNWRAP), debuggability (C-DEBUG), and future-proofing (C-SEALED, C-STRUCT-FIELD, C-NON-EXHAUSTIVE). Use when users design a public crate API, choose between generics/concrete/newtyp
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 19 sept.
full-stack-skillsrust-by-example
Show Rust patterns through short compilable examples — type conversions (From/Into/TryFrom/as/Deref), flow control (if let/while let/match/loop), functions and closures (Fn/FnMut/FnOnce, captures), modules (mod/use/pub/super/self), generics and traits (bounds/associated types/trait objects), error handling (?/Result/thiserror/anyhow), attributes (derive/cfg/inline/allow), unsafe (raw pointers/unions/ABI), procedural macros (derive/attribute/function-like), and inline asm. Use when users ask "how
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 19 sept.
full-stack-skillsrust-cargo-build
Configure, operate, diagnose, and automate Cargo for Rust packages and workspaces. Cover manifests and targets, commands, dependency resolution and features, profiles, build scripts, configuration and environment variables, caches and build diagnostics, cross-compilation, registries, packaging, publishing, metadata, CI reproducibility, and stable-versus-nightly feature gates. Use for Cargo.toml, Cargo.lock, .cargo/config.toml, cargo build/check/run/tree/metadata/package/publish, resolver or feat
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 19 sept.
full-stack-skillsrust-cli
Design, implement, test, and release production Rust command-line applications, including command contracts, subcommands, configuration precedence, stdin/stdout/stderr, exit codes, file safety, daemon IPC, terminal handling, packaging, and process-level tests. Use when users ask for a Rust CLI, command parser, clap integration, Unix-style pipelines, daemon clients, PTY/TUI behavior, shell completion, or CLI release engineering.
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 19 sept.
full-stack-skillsrust-code-review
Review Rust changes for correctness, memory and thread safety, error semantics, unnecessary allocation or cloning, lock scope, API compatibility, test gaps, documentation, and dependency risk, applying the Rust API Guidelines checklist (C-PANIC, C-UNWRAP, C-TRANSMUTE, C-BOOL, C-NEWTYPE, C-COMMON-TRAITS, C-CONVERT, C-SEALED, C-NON-EXHAUSTIVE). Use when reviewing Rust diffs, pull requests, libraries, unsafe boundaries, or production incidents; report actionable findings by severity before summarie
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 19 sept.
full-stack-skillsrust-concurrency
Design, implement, diagnose, and test Rust concurrency and parallelism with threads, Send and Sync, locks, atomics, channels, Tokio, Rayon, Crossbeam, bounded backpressure, actor ownership, task supervision, graceful shutdown, runtime diagnostics, and Loom model tests. Use when users ask about shared state, deadlocks, async tasks, CPU parallelism, high concurrency, daemon resource budgets, slow consumers, worker pools, lock-free structures, or concurrent correctness.
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 19 sept.
full-stack-skillsrust-crate-discovery
Discover, evaluate, score, and compare Rust crates for adoption — search crates.io, fetch metadata from 4 sources (crates.io API, docs.rs, GitHub API, RustSec advisory DB), apply a weighted 0-100 scoring model across adoption/maintenance/documentation/maturity/community/license, flag red concerns (unmaintained, advisories, no docs, single-maintainer), and recommend the best fit. Use when users ask "which crate should I use for X", "is this crate maintained/safe/popular", "compare these 3 crates"
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 19 sept.
full-stack-skillsrust-dependencies
Manage Rust dependency governance at scale — version requirement strategy, crate and source selection, feature minimization, transitive dependency analysis, cargo-deny license/ban/advisory/source policy, cargo-audit, cargo-outdated, Renovate/Dependabot automation, dependency update cadence, cycle diagnosis, and supply-chain security. Use for dependency strategy, crate approval, license compliance, advisories, allowed sources, automated updates, or dependency-graph governance; hand Cargo manifest
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 19 sept.
full-stack-skillsrust-documentation
Design, write, build, test, and publish Rust documentation with rustdoc, cargo doc, doctests, intra-doc links, crate-level guides, examples, README synchronization, mdBook, docs.rs metadata, link checking, documentation CI, and the Rust API Guidelines Documentation chapter (C-DOC, C-LINK, C-META, C-EXAMPLE). Use when users ask for Rust API docs, a project book, runnable examples, docs.rs readiness, missing-doc policy, API guideline compliance, documentation architecture, or stale documentation r
- Installations / 1h
- 1
- GitHub Stars
- 5
- Mis à jour
- 19 sept.