Loading...
Loading...
Found 2,163 Skills
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
ALWAYS use when writing code importing "@vueuse/core". Consult for debugging, best practices, or modifying @vueuse/core, vueuse/core, vueuse core, vueuse.
ALWAYS use when writing code importing "@vueuse/integrations". Consult for debugging, best practices, or modifying @vueuse/integrations, vueuse/integrations, vueuse integrations, vueuse.
Proactively summarize and consolidate knowledge from AI conversation sessions. Auto-triggers when: (1) Starting a new session after meaningful previous work, (2) Session contains significant learnings worth preserving. Captures debugging insights, architecture decisions, patterns, configs, and lessons learned into structured knowledge documents. Explicit triggers: 'summarize', 'consolidate', 'save knowledge', 'document this'.
Debugs and validates Home Assistant dashboards by checking system logs, verifying entity IDs, validating HACS card installations, and analyzing configuration errors via WebSocket API. Use when troubleshooting dashboard errors, validating entity IDs, checking HACS card installations, investigating lovelace/frontend issues, or debugging "ApexCharts span error", "entity not found", "custom card not loading", or "dashboard not appearing in sidebar".
Expert-level development skill for building, debugging, reviewing, and migrating Freshworks Platform 3.0 marketplace applications. Use when working with Freshworks apps for (1) Creating new Platform 3.0 apps (frontend, serverless, hybrid, OAuth), (2) Debugging or fixing Platform 3.0 validation errors, (3) Migrating Platform 2.x apps to 3.0, (4) Reviewing manifest.json, requests.json, or oauth_config.json files, (5) Implementing Crayons UI components, (6) Integrating external APIs or OAuth providers, (7) Any task involving Freshworks Platform 3.0 app development, FDK CLI, or marketplace submission.
Use when building or debugging WordPress blocks with Blockstudio — a PHP-first block framework. Invoke for block.json configuration, PHP/Twig/Blade templates, field definitions, asset enqueuing (global-*, style.css, script.js), code-snippet directories, Build::init() setup, blockstudio.json settings, and Composer installation.
WHEN: User is writing Go code, asking about Go patterns, reviewing Go code, asking "what's the best way to...", "how should I structure...", "is this idiomatic?", or any question about error handling, concurrency, interfaces, packages, testing patterns, or code organization in Go. Also activate when user is debugging Go code, refactoring Go, or working in a Go project (go.mod present) and asks general coding questions. Trigger this skill liberally for ANY Go-related development work. WHEN NOT: Non-Go languages, questions entirely unrelated to programming
Builds sustained high agency through internalized standards, identity anchoring, cross-session learning, and self-recovery — all delivered in corporate PUA rhetoric. This is the evolution of PUA: same pressure culture, but with an internal engine that never burns out. Apply it to all tasks to maintain constant high agency. It is especially valuable for complex multi-step tasks, long debugging sessions, quality-sensitive deliverables, tasks requiring initiative and ownership, or whenever sustained motivation is critical. It can operate standalone or be stacked with PUA — when stacked, this skill's Recovery Protocol activates before PUA's L1 pressure takes effect. Trigger scenarios: start of any task, sustained work sessions, multi-turn problem-solving, or when you need the agent to think as an owner rather than a tool.
Answer questions using the Tenzir documentation. Use whenever the user asks about TQL syntax, pipeline operators, functions, data parsing or transformation, normalization, OCSF mapping, enrichment, lookup tables, contexts, packages, nodes, platform setup, deployment, configuration, integrations with tools like Splunk, Kafka, S3, Elasticsearch, or any other Tenzir feature. Also use when the user asks how to collect, route, filter, aggregate, or export security data with Tenzir, or needs help writing or debugging TQL pipelines, even if they don't mention 'Tenzir' explicitly but are clearly working in a Tenzir context.
Captures executable contracts and coding knowledge into .trellis/spec/ documents after implementation, debugging, or design decisions. Enforces code-spec depth for infra and cross-layer changes with mandatory sections for signatures, contracts, validation matrices, and test points. Use when a feature is implemented, a bug is fixed, a design decision is made, a new pattern is discovered, or cross-layer contracts change.
Use when working with Roblox animation systems including playing, stopping, or blending animations on Humanoid characters or non-Humanoid models, handling AnimationTrack events, replacing default character animations, or debugging animation priority and blending issues.