yeaight7
UserCurated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Categories
Indexed Skills (45)
tri-model-review
Use when a request needs parallel external perspectives — combined backend and UI work, code review from multiple angles, or cross-validation where different models may disagree.
prompt-evaluation-runner
Use when evaluating prompts, LLM outputs, red-team suites, or model behavior with local eval configs and safe provider/cost controls.
red-team-eval-authoring
Use when creating or reviewing red-team eval plugins, attack templates, grader rubrics, safety fixtures, or model-risk test metadata.
skill-evaluation-workbench
Use when designing, running, debugging, or hardening deterministic eval suites for agent skills, prompts, tool workflows, or MCP-backed cases.
model-routing
Use when selecting a model for a new task or subagent, deciding whether to escalate after a failed attempt, or designing a multi-agent pipeline with mixed task complexity.
local-rag-mcp
Use when querying, ingesting, or maintaining a local RAG MCP corpus for semantic document retrieval with privacy controls.
managed-codebase-context
Use when connecting to a managed codebase-context MCP/session service, checking stale maps, or safely using MCP-provided repository context.
search-before-building
Use when about to add a new helper, utility, or abstraction, a task sounds like a solved problem, a new external dependency is being considered, or custom code is proposed without checking what already exists.
structured-code-search-mcp
Use when designing or using MCP-backed structured code search with search, AST query, symbol inventory, and bounded extraction workflows.
ai-slop-cleaner
Use when a working code path feels bloated, noisy, or over-abstracted, when asked to clean up or deslop AI-generated code, or when a reviewer-only anti-slop pass is requested.
deploy-pipeline-runbook
Use when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt state in a downstream system.
bigquery-cost-audit
Use when reviewing BigQuery spend, query failure patterns, or scan inefficiencies -- identifying which jobs, users, or projects drive cost, or preparing optimization recommendations for a cost review.
data-quality
Use when adding or reviewing data quality tests for dbt models in warehouse-backed analytics projects. Covers dbt generic tests, singular tests (assert_*.sql), accepted-values macros, dbt_utils patterns, cross-system consistency tests, and warehouse-oriented validation. Use when writing data tests, creating assert_*.sql files, testing business logic, or validating referential integrity.
dbt-strategy
Use when creating or modifying dimensional dbt models in warehouse-backed analytics projects. Covers a four-layer warehouse architecture (sources/staging/core/marts), naming conventions, no-alias SQL rule, surrogate-key and missing-record patterns, incremental strategies, deduplication, and common project macros. Use when building fact tables, dimension tables, staging models, writing SQL, or designing tests.
metric-impact-analyzer
Use when a change may affect metrics, semantic models, dashboards, reporting, or stakeholder-facing KPIs and you need to know whether business meaning or downstream BI assets change.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
agent-runtime-patterns
Use when optimizing agent runtime loops, card packs, MCP session lifecycle, tool-call count, or multi-agent orchestration patterns.
agent-session-forensics
Use when diagnosing agent session history, interrupted tool loops, missing tool results, timing bottlenecks, or subagent trace correlation.
brainstorming
Use when starting any creative work — creating features, building components, adding functionality, or modifying behavior — before any implementation begins.
context-compression
Use when conversation context is bloated, constraints are being forgotten, or a compact handoff is needed before continuing work.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
canonical-advisor-routing
Use when routing a prompt to a local provider CLI for a second opinion, review, or plan -- you are about to call a provider directly, need the response saved for later, or want a single consistent way to invoke codex/gemini/claude.
architecture-simplification
Use when a codebase carries over-engineered abstractions, unnecessary layers, or redundant logic that should be collapsed without changing behavior.
dead-code-removal
Use when unused functions, classes, exports, or files need to be identified and safely deleted.
dependency-cleanup
Use when package manifests carry unused or redundant third-party dependencies that slow builds, widen the security surface, or complicate updates.
incremental-migration
Use when migrating APIs, libraries, or patterns across a large codebase and a single mega-commit would be too risky to review or merge.
naming-and-structure-cleanup
Use when naming conventions or file structure drift across a project and need to be made consistent without changing business logic.
test-preserving-refactor
Use when code needs restructuring and observable behavior must stay unchanged, with existing tests kept green at every step.
dbt-incremental-strategy-audit
Use when reviewing a new or changed dbt incremental model -- the strategy looks over-engineered, rebuild or delete behavior is unclear, or the model deviates from how the rest of the repo handles incrementals.
dbt-preflight
Use when a dbt change needs preflight before a PR, review, or merge -- changed models, snapshots, seeds, macros, or semantic YAML whose blast radius and test coverage are not yet known.
semantic-layer-change-review
Use when a change touches dbt semantic models, metrics, saved queries, or other semantic-layer YAML -- especially when an existing metric's expression, aggregation, filters, or dimensions are modified.
sql-business-logic-review
Use when reviewing SQL that affects reporting, metrics, transformations, financial logic, product logic, or stakeholder-facing outputs -- especially when a query still runs fine but its business meaning may have drifted.
failure-triage
Use when confronted with an unknown failure in CI or production, before committing to a deep debugging approach.
flaky-test-investigation
Use when tests pass and fail intermittently without code changes, or a test passes alone but fails in the full suite.
log-driven-diagnosis
Use when debugging complex runtime failures, distributed systems, or issues where a local debugger cannot be attached.
minimal-reproduction
Use when a bug must be isolated from a large application into a standalone, runnable script or single test case.
regression-bisecting
Use when a bug was recently introduced but you don't know which commit caused it.
context-minimization
Use when a task runs long and the context window is filling -- large files are being read whole, command output is flooding the transcript, or responses are getting verbose and slow.
handoff-discipline
Use when ending a session, handing a task back to the user, or approaching the context limit with work unfinished -- the next session or engineer must be able to resume the work instantly.
agent-harness-design
Use when designing tool definitions for a new agent or subagent, an agent shows high retry rates, ambiguous tool invocations, or silent failures, or an existing agent harness needs a quality review.
context-retrieval-loop
Use when starting work in an unfamiliar area of a codebase, spawning a subagent that needs targeted file context, a first search pass missed the relevant file, or the file scope of a task is unclear.
safe-refactor
Use when code needs restructuring without changing observable behavior.
bug-hunt
Use when reproducing, isolating, and fixing a bug with the smallest safe change.
no-fluff
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "no fluff", "be concise", "use less tokens", or similar.
repo-map
Use when the task is to understand an unfamiliar codebase, locate key entry points, or summarize architecture before editing.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.