Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 36931–36960 of 41409 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| performance-reviewnledford/engineering-review-boardReview performance and scalability using workload, baseline, profiling, query-plan, rendering, concurrency, and resource evidence. Use for bottleneck audits, benchmark plans, capacity risks, or performance-sensitive changes; do not use for active unexplained regressions or implementation mechanics alone. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| playwright-e2enledford/engineering-review-boardPlaywright browser E2E guidance. Use when adding, updating, running, or debugging checked-in Playwright tests, playwright.config files, browser test helpers, targeted test runs, traces, reports, cross-browser projects, or testing browser-visible behavior through checked-in Playwright tests. Do not use for non-browser domain logic, frontend implementation without a durable Playwright artifact, or generic manual browser automation. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| postgresql-sql-engineeringnledford/engineering-review-boardPostgreSQL and SQL engineering guidance. Use with sql-engineering when adding, changing, reviewing, testing, or optimizing PostgreSQL schemas, SQL queries, migrations, transactions, constraints, indexes, views, functions, row-level security, privileges, data behavior, or database performance in any language stack. Do not use for unchanged-SQL ORM or adapter mechanics. Use api-design when migrations or query outputs affect published contracts and observability-engineering for PostgreSQL telemetry signals. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| prompt-engineering-reviewnledford/engineering-review-boardReview and improve prompts and bounded agent-system instruction interfaces for coding agents. Use for prompt audits, rewrites, multi-agent roles, delegation and handoff contracts, acceptance criteria, and quality gates; do not use for application implementation, runtime architecture audits, or reusable SKILL.md authoring. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| python-antipatternsnledford/engineering-review-boardPython anti-pattern detection and correction guidance. Use when reviewing or refactoring generated or hand-written Python for mutable defaults, global state, import-time side effects, broad Any or dict-shaped data, broad exception handling, monkeypatch-heavy tests, Pydantic/ORM/framework leakage, async blocking, resource leaks, dependency sprawl, brittle tests, or architecture boundary violations. Do not use for ordinary Python implementation or workflow, or for positive pattern selection. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| python-design-patternsnledford/engineering-review-boardPython design pattern guidance. Use when choosing, implementing, or reviewing idiomatic Python patterns such as dataclasses, value objects, protocols, context managers, dependency injection, adapters, repositories, factories, CLI/service boundaries, async resource handling, pytest fixtures, or Clean/Hexagonal/Onion expression in Python. Use python-antipatterns for smell-focused audits and python-engineering for broader Python workflow. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| python-engineeringnledford/engineering-review-boardPython engineering guidance with uv. Use when adding, changing, reviewing, testing, packaging, linting, formatting, typing, dependency-managing, or refactoring Python code, pyproject.toml, uv.lock, pytest/unittest tests, Python scripts, Python web templates, or Python project workflows. Do not use as the primary skill for distributed PySpark SQL/DataFrame execution, execution plans, shuffles, Structured Streaming, or notebook/cluster lifecycle; use data-platform-engineering. Do not use as the primary skill for smell-focused Python audits; use python-antipatterns. Do not use for checked-in hosted CI/release-provider or Docker/OCI/Compose configuration except the Python commands they invoke; use ci-release-engineering or container-engineering. Use api-design for public service/SDK/CLI contracts, observability-engineering for telemetry/logging signal design, and css-scss-styling for CSS/SCSS/template styling decisions. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| random-data-identifiersnledford/engineering-review-boardRandomness, generated identifiers, random words, sentences, passphrases, synthetic text, and test data guidance. Use when generating random numbers, UUIDs, CUIDs, ULIDs, nonces, tokens, filenames, fixture data, reproducible seeded simulations, human-readable synthetic content, or collision-resistant IDs in code or tests. Prefer cryptographically secure randomness for secrets, passphrases, security-sensitive IDs, and public IDs that must be unguessable; use explicit seeded PRNGs for reproducible tests and simulations. Do not use for fixed examples with no randomness, copyediting fixed text, or database-native ID/index design without a generated-value decision. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| release-readinessnledford/engineering-review-boardAssess merge and release readiness across tests, docs, migrations, rollout, rollback, operations, and cross-functional risk. Use for a final ship or hold decision; do not use to choose a semantic patch, minor, or major version, or as the primary implementation, code-review, or deployment workflow. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| review-verification-protocolnledford/engineering-review-boardMandatory evidence gates for review findings. Load with code-review and any specialist review skill before reporting findings, or read/apply manually if the runtime hides this skill. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| root-cause-analysisnledford/engineering-review-boardStructured root-cause analysis for recurring failures, incidents, regressions, systemic process gaps, and postmortem-style prevention work. Use after the direct cause of a current symptom is understood; use systematic-debugging first for active failing tests, crashes, or unknown immediate causes. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| ruby-engineeringnledford/engineering-review-boardRuby engineering guidance. Use when creating, changing, reviewing, testing, packaging, or scripting Ruby source, gems, Gemfiles, Bundler, Rake, Minitest, RSpec, Rails-adjacent Ruby, or Ruby CLIs. Do not use merely to choose among scripting languages without Ruby implementation, or for framework-specific behavior whose owning skill is more precise. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| rust-antipatternsnledford/engineering-review-boardRust anti-pattern detection and correction guidance. Use when reviewing or refactoring Rust code for generated-code smells, borrow-checker workarounds, unnecessary clones, Arc<Mutex> misuse, boxed indirection, deref polymorphism, deny-warnings misuse, panic/unwrap at boundaries, async overuse, leaky framework or SQL types, brittle tests, or architecture boundary violations. Do not use for ordinary Rust implementation; use rust-engineering instead. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| rust-async-webnledford/engineering-review-boardAsync Rust and Rust web/full-stack guidance. Use when working with Tokio, async tasks, cancellation, timeouts, backpressure, channels, shared state, synchronization, Axum handlers/extractors/state/middleware, Leptos components, leptos-use, server functions, SSR/hydration/WASM, or Axum-Leptos full-stack applications. Use rust-desktop-gui for native desktop GUI event-loop integration, api-design for endpoint contracts, observability-engineering for durable telemetry, css-scss-styling for CSS/SCSS/Leptos styling decisions, rust-persistence-sql for SQLx/database work, and rust-testing-quality for test lanes. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| rust-code-reviewnledford/engineering-review-boardReview Rust code with Rust-specific rigor. Use with code-review when changes touch Rust ownership, lifetimes, traits, error contracts, crate boundaries, feature flags, tests, Rustdoc, async, Tokio, Axum, Leptos, SQLx, SeaQuery, SeaORM, Diesel, SQLite, unsafe code, macros, FFI, public APIs, design patterns, anti-patterns, or performance-sensitive behavior. Use sql-engineering, postgresql-sql-engineering, mysql-mariadb-sql-engineering, or sqlite-sql-engineering too for database-native schema, SQL, migrations, privileges, or query plans. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| rust-design-patternsnledford/engineering-review-boardRust design pattern and idiom guidance. Use when choosing, implementing, or reviewing Rust patterns such as newtypes, builders, RAII guards, traits, strategy, visitor, command, compose-structs, small crates, contained unsafe modules, custom traits for complex bounds, macros, or ownership-driven API design. Use rust-antipatterns for smell-focused audits and load rust-engineering whenever applying or implementing a pattern. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| rust-desktop-guinledford/engineering-review-boardNative Rust desktop GUI guidance. Use when building, changing, testing, debugging, or packaging Windows, macOS, or Linux desktop applications with Iced, egui/eframe, Slint, or Tauri, including event loops, UI-thread work, widgets, themes, accessibility, background work, and native distribution. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| rust-engineeringnledford/engineering-review-boardCore Rust engineering guidance. Use when adding or changing Rust crates, modules, public APIs, domain logic, ownership and lifetime structure, traits, generics, error types, feature flags, workspaces, refactors, design patterns, or declarative/procedural macros. Do not use for checked-in hosted CI/release-provider or Docker/OCI/Compose configuration except the Rust commands they invoke; use ci-release-engineering or container-engineering. Use api-design for public service/SDK/CLI contracts, observability-engineering for telemetry/logging signal design, rust-testing-quality for test and CI lanes, rust-async-web for Tokio/Axum/Leptos work, rust-desktop-gui for native desktop GUI frameworks and delivery, rust-persistence-sql for SQLx, SeaQuery, and database adapter work, and rust-code-review for requested reviews. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| rust-persistence-sqlnledford/engineering-review-boardRust persistence, SQLx, SeaQuery, and SQL-library guidance. Use when adding, changing, reviewing, or testing SQLx queries/macros, SeaQuery builders, SeaORM, Diesel, raw SQL choices, Rust database adapters, pools, transactions, offline query metadata, migrations invoked from Rust, SQLite support, database-backed Rust tests, dynamic SQL construction, or persistence boundaries. Use sql-engineering, postgresql-sql-engineering, mysql-mariadb-sql-engineering, or sqlite-sql-engineering for database-native design. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| rust-testing-qualitynledford/engineering-review-boardRust testing and quality-gate guidance. Use when writing, updating, running, filtering, or reporting Rust unit, integration, end-to-end, property-style, compile-fail, or Rustdoc tests; when applying TDD or BDD to Rust changes; or when using cargo fmt, cargo check, cargo test, cargo test --doc, cargo clippy, cargo-nextest, Bacon/bacon.toml feedback loops, and CI-oriented Rust validation. Do not use for checked-in hosted CI/release-provider configuration except the Rust commands and test lanes it invokes; use ci-release-engineering. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| script-engineeringnledford/engineering-review-boardScript and automation engineering guidance. Use when creating, changing, reviewing, or testing POSIX shell, Bash, zsh, Fish, PowerShell, Python, Ruby, PHP, Node, Object Pascal/Delphi, or other repository scripts; choosing a scripting language or interpreter; deciding whether automation belongs in a script or shell; or exposing script workflows through Just or package scripts. Do not use when only running an existing script or recipe, for ordinary application code with no automation surface, or for hosted CI/release-provider or container semantics beyond the commands scripts invoke. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| security-reviewnledford/engineering-review-boardSecurity review and audit guidance for concrete code, config, docs, and command-surface changes. Use when implemented changes touch authentication, authorization, crypto, certificates, tokens, signatures, secrets, passwords, sessions, session cookies, CORS, CSP, CSRF, OAuth/OIDC/SAML, redirect/callback handling, input validation, file paths, command execution, or other trust boundaries. Pair with code-review for review findings; use threat-modeling for design-time boundary analysis and dependency-supply-chain-review for supply-chain-specific review. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| security-review-evidencenledford/engineering-review-boardCompanion evidence checklist for security-sensitive changes and reviews. Use only with security-review, threat-modeling, or dependency-supply-chain-review to keep evidence sanitized, scoped, and tied to repository policy. Do not use as standalone security analysis. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| semantic-versioningnledford/engineering-review-boardDetermine, recommend, review, or apply Semantic Versioning changes. Use when deciding whether a release needs a patch, minor, or major bump; calculating the next version; auditing changes since the last release; handling 0.x, 1.0.0, prerelease, deprecation, dependency, or mixed-change cases; or updating version metadata after the bump is chosen. Do not use as the primary skill for designing an API contract, changing checked-in release automation, creating Git tags, publishing artifacts, or making the final ship-or-hold decision. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| sql-engineeringnledford/engineering-review-boardDatabase-neutral SQL engineering guidance. Use when reading, writing, refactoring, reviewing, testing, or optimizing SQL queries, schemas, migrations, tables, views, functions, triggers, constraints, indexes, transactions, reporting queries, or data behavior before choosing a database-specific skill. Use api-design when SQL changes affect published contracts, observability-engineering for database telemetry, and PostgreSQL, MySQL/MariaDB, or SQLite skills for engine-specific behavior. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| sqlite-sql-engineeringnledford/engineering-review-boardSQLite and SQL engineering guidance. Use with sql-engineering when adding, changing, reviewing, testing, or optimizing SQLite schemas, migrations, constraints, indexes, transactions, query behavior, local/embedded database workflows, SQLite-backed tests, or SQLite-specific adapter boundaries in any language stack. Do not use for unchanged-SQL ORM or generic adapter mechanics. Use api-design when SQLite schemas or exports affect published contracts and observability-engineering for durable SQLite diagnostics. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| suggest-lucide-iconsnledford/engineering-review-boardPick real Lucide icons for a concept, UI placement, button, section header, or note frontmatter. Use when the user asks what Lucide icon to use, requests icon candidates, or needs an icon name verified. Do not use for non-Lucide icon libraries or general icon or artwork design. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| svelte-sveltekit-engineeringnledford/engineering-review-boardSvelte and SvelteKit engineering guidance. Use when adding, changing, reviewing, or testing .svelte components, Svelte 5 runes, stores, context, SvelteKit routing, load functions, form actions, hooks, adapters, or deciding between standalone Svelte and full SvelteKit. Use javascript-typescript-engineering for generic JS/TS package/build/test mechanics, css-scss-styling for stylesheet and Tailwind decisions, api-design for backend contract shape, and ux-accessibility-review for accessibility audits. Do not use for non-Svelte frontend frameworks. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| systematic-debuggingnledford/engineering-review-boardEvidence-driven debugging for active bugs, failing tests, runtime exceptions, flaky behavior, performance regressions, build/lint/type/compile failures, integration failures, crashes, and unexpected behavior. Use before proposing fixes for a current symptom. Use root-cause-analysis for recurring incidents, systemic failures, and postmortem-style prevention work. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |
| technical-debt-auditnledford/engineering-review-boardPerform repository-wide or focused technical-debt audits covering maintainability, complexity, duplication, dependency health, testing gaps, architecture erosion, documentation drift, and remediation priorities. Use when the user asks to assess accumulated debt, modernization risk, change friction, quick wins, or blockers to future work or scaling. Do not use for an ordinary diff review, an active unexplained failure, implementation, or a vulnerability-only audit. | Stars: 11 | Updated | Claude CodeCodex | Unverified | Install |