调试
定位并修复问题，分析错误
nansen-batch-wallet
nansen-ai
"Which of these addresses are smart money? Batch-profile a list in one call."
decisive-action
athola
Guidance on when to ask clarifying questions vs proceed with standard
response-compression
athola
hype, and unnecessary framing. Includes termination and directness guidelines.
shared-patterns
athola
'Reference these patterns to validate consistency across the ecosystem.
e2e
NeverSight
Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.
code-review
RTGS2017
代码审查和质量分析技能。用于审查代码、发现潜在问题、提供改进建议。当用户请求代码审查、代码质量分析或最佳实践建议时使用。
bridgebound-symptoms-11
sachacoldiq
11 Symptoms & Signs Bridgebound triggers from Flip The Script - Overt Negatives, Lacking Positives, and Industry Influencers. Use when identifying pain-based opportunities, building problem-aware campaigns, or leveraging influencer audiences.
gtm-philosophy
sachacoldiq
Core GTM philosophy principles and multi-channel coordination strategy. Use when defining outbound strategy, training sales teams, or establishing GTM fundamentals.
claims-validator
jmagly
Validation reports: .aiwg/reports/claims-validation.md
systematic-debugging
FradSer
Provides systematic debugging methodology with 4-phase process (root cause investigation, pattern analysis, hypothesis testing, implementation). Use when encountering any bug, error, failure, broken functionality, test failure, unexpected behavior, troubleshooting issue, or investigating why something isn't working. Always apply before proposing fixes or making changes.
debugging-dags
astronomer
Comprehensive DAG failure diagnosis and root cause analysis. Use for complex debugging requests requiring deep investigation like "diagnose and fix the pipeline", "full root cause analysis", "why is this failing and how to prevent it". For simple debugging ("why did dag fail", "show logs"), the airflow entrypoint skill handles it directly. This skill provides structured investigation and prevention recommendations.
playwright-best-practices
currents-dev
Provides comprehensive guidance for writing, debugging, and maintaining Playwright tests in TypeScript. Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
check-consistency
dykyi-roman
Analyzes PHP code for consistency issues. Detects mixed coding styles, inconsistent patterns, API inconsistencies, naming convention violations.
pua-debugging
tanweai
"Use when any task fails two or more times, when about to give up or say 'I cannot', when deflecting to the user ('you should manually...', 'please check...', 'you may need to...'), blaming the environment without verification ('might be a permissions issue', 'could be a network problem'), producing any excuse to stop trying, spinning in circles (repeatedly tweaking the same code/parameters without new information — busywork/磨洋工), fixing only the surface issue without checking for related problems, skipping verification after a fix and claiming 'done', giving suggestions instead of actual code/commands, saying 'this is beyond scope' or 'this requires manual intervention', encountering permission/network/auth errors and stopping instead of trying alternatives, or showing any passive behavior (waiting for user instructions instead of proactively investigating). Also triggers on user frustration phrases in any language: '你怎么又失败了', '为什么还不行', '换个方法', '你再试试', '不要放弃', '继续', '加油', 'why does this still not work', 'try harder', 'you keep failing', 'stop giving up', 'try again', 'don't give up', 'keep going', 'figure it out'. Applies to ALL task types: debugging, implementation, config, deployment, research, DevOps, infrastructure, API integration, data processing. Do NOT trigger on first-attempt failures or when a known fix is already in progress."
telnyx-oauth-go
team-telnyx
Implement OAuth 2.0 authentication flows for Telnyx API access. This skill provides Go SDK examples.
telnyx-iot-go
team-telnyx
Manage IoT SIM cards, eSIMs, data plans, and wireless connectivity. Use when building IoT/M2M solutions. This skill provides Go SDK examples.
config-validator
jmagly
Migration guides: docs/config-migrations.md
python-best-practices
NeverSight
Provides Python patterns for type-first development with dataclasses, discriminated unions, NewType, and Protocol. Must use when reading or writing Python files.
zig-best-practices
NeverSight
Provides Zig patterns for type-first development with tagged unions, explicit error sets, comptime validation, and memory management. Must use when reading or writing Zig files.
op-cli
NeverSight
Secure 1Password CLI patterns for reading secrets, discovering vaults/items, and piping credentials to other tools. Use when reading from 1Password, rotating secrets, or piping credentials to wrangler/kubectl/etc. Triggers on op CLI, 1Password, secret rotation, or credential piping tasks.
simplifying-code
iliaal
Simplifies, polishes, and declutters code without changing behavior. Use when asked to "simplify code", "clean up code", "polish code", "refactor", "declutter", "reduce complexity", "remove dead code", "remove AI slop", "improve readability", or "tighten up this file".
nodejs-backend
iliaal
Node.js backend patterns: framework selection, layered architecture, TypeScript, validation, error handling, security, production deployment. Use when building REST APIs, Express/Fastify servers, microservices, or server-side TypeScript.
pinescript
iliaal
Pine Script v6 patterns: syntax rules, performance, debugging, backtesting, visualization. Use when asked to "write a Pine Script", "create an indicator", "build a strategy", "fix Pine code", or mentions PineScript, TradingView, indicator, strategy, or backtest.
writing
iliaal
Prose editing, rewriting, and humanizing text for natural tone. Use when asked to "write", "rewrite", "edit", "humanize", "improve text", "fix the tone", "remove AI language", "proofread", or when writing copy, docs, blog posts, articles, emails, PR descriptions, or plans.