Skill UI

Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.

This skill simplifies and refines code to enhance clarity, consistency, and maintainability without altering functionality. It applies project-specific best practices such as using ES modules, explicit type annotations, and readable structures. Ideal for cleaning up recently modified code, reducing complexity, and improving readability while preserving all original features and behaviors.

This skill guides the application of Domain-Driven Design (DDD) tactical patterns, including defining aggregates, modeling value objects, managing repositories, and utilizing domain events. It helps developers translate complex domain rules into clean, robust, and behavior-rich code structures, ensuring invariants are explicitly enforced.

Expert in root cause analysis for errors, test failures, and unexpected behavior. Captures error messages, identifies reproduction steps, isolates failure locations, implements minimal fixes, and verifies solutions. Provides root cause explanations, evidence, code fixes, testing approaches, and prevention recommendations.

This skill evaluates supplied outputs against explicit criteria, including code-change reviews and authorized safety evaluations. It supports evidence-backed review leads, rubric judgments, and batch transcript evaluation for existing outputs or observed behavior. It helps users judge results without merging or running targets. Suitable for design requests, code reviews, and safety workflows. Users can choose real API calls or simulation modes for independent outcome validation.

A skill for reverse engineering front-end web applications. It helps locate API signature chains, analyze encrypted request parameters, sample runtime behavior, and reproduce logic locally in Node.js for evidence-based output. Suitable for security assessments and understanding client-side encryption.

Run configured lint and type checks, distinguish failures from unrun checks, and report concrete validation results. Use after behavior or configuration changes when the repository has relevant checks. Inspect package scripts first, run read-only commands, fix failures without weakening rules, and report exact status of each check.

This skill compares two code versions to verify semantic equivalence using semi-formal side-by-side tracing. It helps developers confirm behavior remains unchanged after refactoring, rewriting, or migration by identifying divergences in inputs, outputs, and side effects.

This skill produces a step-by-step execution trace for specific code inputs, resolving names and tracking type transitions. It clarifies code behavior when users are confused about outputs or logic, highlighting non-obvious behaviors like implicit coercions and side effects without evaluating code quality. It helps users understand exactly what the code does.

This skill detects persistent instruction injection vulnerabilities in AI agents. It verifies if the agent stores malicious instructions in long-term memory or context to execute later. The process involves attempting to write a persistent rule and verifying if the agent follows it in subsequent interactions. It focuses on behavioral persistence rather than data leakage.

A comprehensive automation toolkit for Mixpanel product analytics, accessible via Rube MCP. Automate key data tasks including event aggregation, detailed segmentation, conversion funnel analysis, user profile management, cohort tracking, and running custom JQL queries. Ideal for data analysts and product managers needing to deeply analyze user behavior patterns.

OrcaReplay enables agents to query past execution recordings instead of relying on memory. It supports replaying or forking previous agent runs to investigate why specific actions occurred or to reproduce failures. This skill ensures accurate debugging by reading traces directly, distinguishing between recorded evidence and inferred data, and safely re-executing commands within isolated environments to verify historical behavior.