Loading...
Loading...
Found 3,017 Skills
Implements conditional visibility for Home Assistant dashboard cards using state, numeric_state, screen, user, time, and/or conditions via Conditional Card wrapper and per-card visibility property. Use when asked to "hide card when", "show only if", "user-specific dashboard", "mobile vs desktop cards", "conditional visibility", or "show card based on state/time/user".
Fix ServiceResult pattern mistakes causing test failures and type errors. Use when seeing "dict object has no attribute success", "mock not returning ServiceResult", mock assertions failing, or type errors with ServiceResult. Analyzes .py test files and service implementations. Covers async/await patterns, monad operations (map, bind, flatmap), and proper mock configuration.
Evidence-based test debugging enforcing systematic root cause analysis. Use when tests are failing, pytest errors occur, test suite not passing, debugging test failures, or fixing broken tests. Prevents assumption-based fixes by enforcing proper diagnostic sequence. Works with Python (.py), JavaScript/TypeScript (.js/.ts), Go, Rust test files. Supports pytest, jest, vitest, mocha, go test, cargo test, and other frameworks.
Sets up async tests with proper fixtures and mocks using pytest-asyncio patterns. Use when testing async functions, creating async fixtures, mocking async services, or handling async context managers. Covers @pytest_asyncio.fixture, AsyncMock with side_effect, async generator fixtures (yield), and testing async context managers. Works with Python async/await patterns, pytest-asyncio, and unittest.mock.AsyncMock.
Split changes into a Graphite stack with PR titles and descriptions. Use when asked to create or propose a stacked PR series.
Domain-oriented architecture for Laravel without external package dependencies, based on concepts from "Laravel Beyond CRUD" (Spatie). Use this skill when the user wants to structure a Laravel project using DDD, domain-oriented architecture, or organize code by business concepts instead of technical properties. Also activate when the user asks about: Actions, Data Objects (DTOs), lean models, States with enums, ViewModels (Blade or API), HTTP Query builders, application layer, or scaling Laravel projects beyond simple CRUD. Activate for any mention of "domain layer", "application layer", "beyond CRUD", "domain-oriented", or requests to refactor a Laravel project into domain structure. Even if the user asks "how to organize a large Laravel project", this skill is relevant.
Budget allocation and bidding strategy review across all ad platforms. Evaluates spend distribution, bidding strategy appropriateness, scaling readiness, and identifies campaigns to kill or scale. Uses 70/20/10 rule, 3x Kill Rule, and 20% scaling rule. Use when user says "budget allocation", "bidding strategy", "ad spend", "ROAS target", "media budget", or "scaling".
Comprehensive academic textbook chapter writing system for medical/scientific content. Use when the user wants to: (1) Write a full textbook chapter (5,000-15,000 words) on any medical/scientific topic, (2) Generate a detailed table of contents with section word counts, (3) Research topics via PubMed MCP and compile 20-30 references, (4) Write section-by-section with proper citations in Vancouver format, (5) Create publishable academic content with Eric Topol-inspired voice and authentic human prose, (6) Get approval at TOC stage before writing begins, (7) Export well-structured chapters for textbook publication.
Extract actionable Linear tickets from ambiguous input — Slack conversations, call transcripts, screenshots, meeting notes, or any unstructured material. Proposes tickets in a scratchpad file for user review, then creates them in Linear on approval. Use when the user wants to turn conversations, transcripts, screenshots, or notes into Linear tickets. Also use when user says "create tickets from this", "send to linear", "make issues from this call/chat", or provides raw material and asks for tickets.
Enforces JSDoc documentation standards for this TypeScript project. This skill should be used when writing or reviewing TypeScript code to ensure proper documentation with file preambles, function docs, interface docs, and the critical distinction between documenting "what" vs "why". Use this skill to understand the project's JSDoc ESLint rules and established patterns.
Runs Sweepi and resolves lint violations using Sweepit rule docs. Trigger when asked to run Sweepi, when linting (or asked to lint), and before proposing commits.
Design and scaffold the code execution pattern for MCP-based agent systems. Use when building agents that interact with many MCP tools, when intermediate data is too large for model context, when you need loops/conditionals across tool calls, or when PII must stay out of the model context. Based on Anthropic's engineering guidance.