Loading...
Loading...
Found 2,152 Skills
Diagnose and resolve common Guidewire InsuranceSuite errors. Use when encountering API errors, Gosu exceptions, validation failures, or integration issues in PolicyCenter, ClaimCenter, or BillingCenter. Trigger with phrases like "guidewire error", "policycenter error", "claimcenter error", "gosu exception", "api error 422".
Full Sentry SDK setup for Flutter and Dart. Use when asked to "add Sentry to Flutter", "install sentry_flutter", "setup Sentry in Dart", or configure error monitoring, tracing, profiling, session replay, or logging for Flutter applications. Supports Android, iOS, macOS, Linux, Windows, and Web.
Shows the Wasp plugin's available features, commands, and skills.
This skill should be used when the user asks to "diagnose context problems", "fix lost-in-middle issues", "debug agent failures", "understand context poisoning", or mentions context degradation, attention patterns, context clash, context confusion, or agent performance degradation. Provides patterns for recognizing and mitigating context failures.
A disciplined diagnostic loop for tricky bugs and performance regressions. Reproduce → Minimize → Hypothesize → Instrument → Fix → Regression-test. Use this when the user says "diagnose this" / "debug this", reports a bug, states that something is broken/throwing errors/failing, or describes a performance regression.
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.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use this skill when the user needs to build Move code, or when when the user asks about sui move build.
Debug Compact contracts and manage toolchain versions. Covers static vs dynamic errors, reading compiler messages, the --skip-zk dev loop, version synchronization, and common traps.
Implement and run measurements that settle hypotheses before making implementation or fixes, and make decisions based only on the results. Use when investigating the cause of a defect, comparing performance or behavior, starting a new feature, or whenever you are about to judge something with “probably.”
Avoid common mistakes and debug issues in PydanticAI agents. Use when encountering errors, unexpected behavior, or when reviewing agent implementations.
Use when app feels slow, memory grows, battery drains, or diagnosing ANY performance issue. Covers memory leaks, profiling, Instruments workflows, retain cycles, performance optimization.