Debugging
Find and fix bugs, error analysis
linear-create
by Finesssee
Create Linear issues. Use when creating bugs, tasks, or feature requests.
swe
by knoopx
Applies software engineering best practices, design principles, and avoids common anti-patterns. Use when designing systems, reviewing code quality, refactoring legacy code, making architectural decisions, or improving maintainability.
writing
by 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.
generic-feature-developer
by travisjneuman
Guide feature development with architecture patterns for any tech stack. Covers frontend, backend, full-stack, and automation projects. Use when adding new features, modifying systems, or planning changes.
debugging-dbt-errors
by AltimateAI
Debugs and fixes dbt errors systematically. Use when working with dbt errors for: (1) Task mentions "fix", "error", "broken", "failing", "debug", "wrong", or "not working" (2) Compilation Error, Database Error, or test failures occur (3) Model produces incorrect output or unexpected results (4) Need to troubleshoot why a dbt command failed Reads full error, checks upstream first, runs dbt build (not just compile) to verify fix.
optimizing-query-text
by AltimateAI
Optimizes Snowflake SQL query performance from provided query text. Use when optimizing Snowflake SQL for: (1) User provides or pastes a SQL query and asks to optimize, tune, or improve it (2) Task mentions "slow query", "make faster", "improve performance", "optimize SQL", or "query tuning" (3) Reviewing SQL for performance anti-patterns (function on filter column, implicit joins, etc.) (4) User asks why a query is slow or how to speed it up
operational-risk
by JoelLewis
"Operational risk management: trade breaks, settlement fails, error handling, loss event taxonomy, key risk indicators, incident management, and business continuity for trading operations."
order-lifecycle
by JoelLewis
"Order lifecycle management: order states, FIX protocol basics, order types, time-in-force, cancel/replace workflows, order validation, and state machine design for trading systems."
linear-bulk
by Finesssee
Bulk operations on Linear issues. Use when updating multiple issues at once.
condor-strategy
by Senpi-ai
CONDOR v4.0.1 — One Amazing Trade per Day. Top 50 HL assets, pure trend continuation, apex confluence only. 3TF alignment hard gate + MACRO_TREND_GATE + SM consensus >=70%, MIN_SCORE 12, score-scaled sizing (50%/70%/80%), 10x leverage cap, 6-tier DSL ladder from Kodiak SOL empirical wins. v4.0.1 ships a race-window dedup cache that eliminates the ENGINE_FAILURE retry noise on already-held assets, plus a doubled DSL exit interval to throttle REDUCE_ONLY spam when runtime position-state lags HL.
jaguar-strategy
by Senpi-ai
JAGUAR v4.0.0 — Striker (rank-jump detector), senpi_runtime_helpers migration. Plumbing-only flip from openclaw-CLI subprocess + mcporter subprocess + cron-driven self-executing scanner to in-process SenpiClient + long-lived producer_daemon + helpers-native push_signal. Thesis preserved verbatim from v3.7: violent FIRST_JUMP signals, rank-jump ≥ 10, MIN_SCORE 9, conviction-scaled leverage (10x apex / 7x conviction), 15m velocity hard gate, $3M day-notional liquidity floor, XYZ ban, one-amazing-trade-per-day discipline. Risk policy: max 3 entries/day when day is RED, unlimited when GREEN (cap losers, ride winners).
testing-blocks
by adobe
Guide for testing code changes in AEM Edge Delivery projects including blocks, scripts, and styles. Use this skill after making code changes and before opening a pull request to validate functionality. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how
classifying-review-findings
by bitwarden
Use this skill when categorizing code review findings into severity levels. Apply when determining which emoji and label to use for PR comments, deciding if an issue should be flagged at all, or classifying findings as CRITICAL, IMPORTANT, DEBT, SUGGESTED, or QUESTION.
generic-fullstack-ux-designer
by travisjneuman
Professional UI/UX design expertise for full-stack applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting design reviews.
perl-development
by Jamie-BitFlight
This skill should be used when the user asks to "write a Perl script", "create Perl code", "modern Perl best practices", "Perl 5.30+", "use strict warnings autodie", or mentions Perl pragmas, subroutines, error handling, or scripting patterns. Provides comprehensive Perl 5.30+ development guidance.
bash-development
by Jamie-BitFlight
This skill should be used when the user asks to "write a bash script", "create a shell script", "implement bash function", "parse arguments in bash", "handle errors in bash", or mentions bash development, shell scripting, script templates, or modern bash patterns.
bash-logging
by Jamie-BitFlight
This skill should be used when the user asks to "add logging to bash script", "colorize output", "implement log levels", "CI/CD sections", "terminal colors in bash", or mentions logging functions, emoji output, collapsible CI sections, or shlocksmith.
commitlint
by Jamie-BitFlight
When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.
conventional-commits
by Jamie-BitFlight
When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.
telnyx-account-management-go
by team-telnyx
Manage sub-accounts for reseller and enterprise scenarios. This skill provides Go SDK examples.
telnyx-texml-go
by team-telnyx
Build voice applications using TeXML markup language (TwiML-compatible). Manage applications, calls, conferences, recordings, queues, and streams. This skill provides Go SDK examples.
telnyx-messaging-hosted-go
by team-telnyx
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides Go SDK examples.
telnyx-messaging-profiles-go
by team-telnyx
Create and manage messaging profiles with number pools, sticky sender, and geomatch features. Configure short codes for high-volume messaging. This skill provides Go SDK examples.
debug
by whawkinsiv
"Use this skill when features break, users report errors, deployments fail, or tests don't pass. Guides systematic debugging: reproducing bugs, gathering diagnostic info, reading error messages, and working with AI tools to fix issues efficiently."