LLVM IR and pass pipeline skill. Use when working directly with LLVM Intermediate Representation (IR), running opt passes, generating IR with llc, inspecting or writing LLVM IR…
Score 70/100
Automate Lmnt tasks via Rube MCP (Composio). Always search tools first for current schemas.
Score 70/100
Configure learning management system settings, user roles, course templates, gradebooks, and third-party integrations
Score 70/100
Commits and pushes all changes (staged, unstaged, untracked) to remote. Use when you need a quick push of everything at once.
Score 70/100
Analyzes current or recent session for errors, inefficiencies, and improvement opportunities across skills, tools, hooks, and communication.
Score 70/100
Installs agents, configures MCP servers, aligns marketplace plugins, creates and audits instructions. Use after setup or when agents/MCP/plugins need alignment.
Score 70/100
Use when installing MCP packages and configuring Claude-side MCP registration, hooks, permissions, IDE extension mode, and migrations.
Score 70/100
Use when installing or verifying this marketplace in Claude and Codex, aligning selected plugins, MCP settings, and Codex execution defaults.
Score 70/100
Creates AGENTS.md canonical and CLAUDE.md @AGENTS.md stub; audits token budget, cache safety, import-pattern compliance. Use when instruction files need alignment.
Score 70/100
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.
Score 70/100
Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.
Score 70/100
Creates root documentation files (AGENTS.md, CLAUDE.md, docs/README.md, standards, principles). Use for initial project doc setup.
Score 70/100
Creates backend docs (api_spec.md, database_schema.md). Use when project has backend API or database.
Score 70/100
Extracts procedural content from project docs into slash commands. Use when docs contain deploy, test, or troubleshoot procedures.
Score 70/100
Creates slash commands from procedural doc sections. Use when transforming documentation prose into executable commands.
Score 70/100
Reviews skills (D1-D11 + M1-M6 criteria) or .claude/commands for quality. Use when validating skill correctness before release.
Score 70/100
Decomposes scope into Epics, Stories, and RICE priorities. Use when user has project scope and wants full Agile breakdown.
Score 70/100
Discovers growth opportunities using Traffic-First KILL funnel. Use when searching for next product direction with validated demand.
Score 70/100
Creates or replans 3-7 Epics from scope using Decompose-First pattern. Use when initiative needs Epic-level breakdown or Epic scope changed.
Score 70/100
Analyzes Story and builds optimal task plan (1-8 tasks), then routes to create or replan. Use when Story needs task breakdown or replanning.
Score 70/100
Compares ideal plan vs existing tasks and applies KEEP/UPDATE/OBSOLETE/CREATE changes. Use when Story tasks need re-sync with updated requirements.
Score 70/100
Use when an evaluation run needs review-driven documentation updates and a structured documentation summary.
Score 70/100
Use when accepted findings require bounded repair changes and a structured repair summary.
Score 70/100
Use when an evaluation run requires bounded iterative refinement with trace and cleanup evidence.
Score 70/100
Executes implementation tasks through Todo, In Progress, To Review. Use when task needs coding with KISS/YAGNI. Not for test tasks.
Score 70/100
Reviews task implementation for quality, code standards, and test coverage. Use when task is in To Review. Sets task Done or To Rework.
Score 70/100
Fixes tasks in To Rework by applying reviewer feedback, then returns to To Review. Use when task was rejected during review.
Score 70/100
Runs existing test suite to catch regressions after implementation changes. Use when Story needs regression verification. No status changes.
Score 70/100
Audit project documentation quality across 8 categories (Hierarchy, SSOT, Compactness, Requirements, Actuality, Legacy, Stack Adaptation, Semantic Content).
Score 70/100
Checks hierarchy, links, SSOT, compression, requirements compliance, freshness, legacy cleanup. Use when auditing documentation structure.
Score 70/100
Checks inline code documentation quality: WHY-not-WHAT, density, forbidden content, docstrings quality, actuality, legacy cleanup. Use when auditing comments and docstrings.
Score 70/100
Verifies claims in .md files (paths, versions, counts, configs, endpoints) against codebase, cross-checks contradictions. Use when auditing docs accuracy.
Score 70/100
Checks DRY, KISS/YAGNI, error handling, DI patterns. Use when auditing code principles compliance.
Score 70/100
Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.
Score 70/100
Checks unreachable code, unused imports/variables/functions, commented-out code, unsupported patterns. Use when auditing dead code.
Score 70/100
Checks structured logging, health checks, metrics collection, request tracing, log levels. Use when auditing observability.
Score 70/100
Checks async races, thread safety, TOCTOU, deadlocks, blocking I/O, resource contention. Use when auditing concurrency safety.
Score 70/100
Checks bootstrap initialization, graceful shutdown, resource cleanup, signal handling, liveness/readiness probes. Use when auditing app lifecycle.
Score 70/100
Analyzes single pattern implementation, calculates compliance/completeness/quality scores, identifies gaps. Use when auditing a specific pattern.
Score 70/100
Checks layer leakage in method signatures, missing DTOs, entity leakage to API, inconsistent error contracts. Use when auditing API contracts.
Score 70/100
Builds dependency graph, detects cycles, validates boundary rules, calculates coupling metrics (Ca/Ce/I). Use when auditing dependency structure.
Score 70/100
Discovers custom modules replaceable by OSS, evaluates alternatives (stars, license, CVE), generates migration plan. Use when reducing custom code.
Score 70/100
Checks file hygiene, ignore files, framework conventions, domain/layer organization, naming. Use when auditing project structure.
Score 70/100
Checks env var config sync, missing defaults, naming conventions, startup validation. Use when auditing environment configuration.
Score 70/100
Checks transaction scope, missing rollback handling, long-held transactions, trigger/notify interaction. Use when auditing transaction correctness.
Score 70/100
Checks blocking IO in async, unnecessary allocations, sync sleep, string concat in loops, redundant copies. Use when auditing runtime performance.
Score 70/100
Checks session scope mismatch, missing cleanup, pool config, error path leaks, resource holding. Use when auditing resource lifecycle.
Score 70/100
Bootstraps projects to production-ready structure. Use when creating new or transforming existing projects.
Score 70/100
Configures environment variables and secrets protection. Use when setting up .env files and gitignore rules for a project.
Score 70/100
Sets up logging, error handling, CORS, health checks, and API docs. Use when adding cross-cutting concerns to backend projects.
Score 70/100
Configures CORS policy for development and production environments. Use when setting up cross-origin access for APIs.
Score 70/100
Verifies bootstrapped projects via build, test, and container health checks. Use when validating project setup completeness.
Score 70/100
Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.
Score 70/100
Multi-cycle performance optimization with profiling and bottleneck analysis. Use when optimizing application performance.
Score 70/100
Profiles runtime performance with CPU, memory, and I/O metrics. Use when measuring bottlenecks before optimization.
Score 70/100
Upgrades dependencies across all detected package managers. Use when updating npm, NuGet, or pip packages project-wide.
Score 70/100
Upgrades .NET NuGet packages with breaking change handling. Use when updating .NET dependencies.
Score 70/100
Modernizes codebase via OSS replacement and bundle optimization. Use when acting on audit findings to reduce custom code.
Score 70/100
Reduces JS/TS bundle size via tree-shaking, code splitting, and unused dependency removal. Use when optimizing frontend bundle size.
Score 70/100
Use when benchmarking hex-line MCP against Claude built-in tools with scenario manifests, activation checks, and diff-based correctness.
Score 70/100