Loading...
Loading...
Found 1,372 Skills
Manual testing workflow for Claude HUD to verify core functionality. Use when asked to "test the app", "verify the app works", "run manual tests", "test after changes", or after implementing significant features. Performs full reset, launches app, and guides through verification checklist.
Use when dealing with 2 or more tasks that can be performed independently, with no shared state or sequential dependencies
Compare OpenAI Codex GPT-5.3 and code-searcher responses for comprehensive dual-AI code analysis. Use when you need multiple AI perspectives on code questions.
React Native & Expo engineering standards.
Enabled when investigating and isolating the cause of a problem
This skill should be used when the user asks to "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior", "understand a production incident", "query telemetry data", "look at logs", "check traces", "examine spans", "analyze RUM data", "check frontend performance", "investigate backend latency", "find transaction data", "check payment metrics", "analyze user journeys", or wants to answer questions using observability data from logs, metrics, traces, RUM, or APM - this is the gateway skill for deciding where to look first.
Finds the most informative session recording linked to an error tracking issue. Use when a user has an error tracking issue ID and wants to watch a replay showing what the user was doing when the error occurred. Ranks linked sessions by recency, activity score, and journey completeness, then summarizes the pre-error context. Replaces blind session picking from potentially hundreds of linked recordings.
Activate when the user clearly has a skill issue. Generates chaotic, barely-functional code with maximum confidence and sarcastic commentary. Guarantees an infinite loop of attempted fixes that never quite land.
Guide for testing Codex TUI interactively
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.
Deeply interviews the user about a bug before investigating or fixing it. Use this when the user says "interview me about [bug]", "I have a bug to report", "let's work on this bug", "found a bug", "there's a bug", or describes a bug they encountered. Asks probing questions about reproduction steps, environment, patterns, impact, and context that help isolate the root cause. Continues until the bug is well-understood, then writes a detailed investigation/fix plan.
Use this skill when the user needs to build Move code, or when when the user asks about sui move build.