Loading...
Loading...
Found 384 Skills
20 "In Market" Bridgebound triggers from Flip The Script - Adjacent Vendors, Competitors, and Time-Based signals. Use when targeting active buyers, building competitive displacement campaigns, or leveraging seasonal/event timing.
SolidJS and SolidStart performance and correctness guidelines for AI agents. This skill should be used when writing, reviewing, or refactoring SolidJS/SolidStart code to ensure correct reactivity patterns and optimal performance. Triggers on tasks involving SolidJS components, signals, stores, Solid Query, SolidStart server functions, routing, or fine-grained reactivity.
Salesloft platform help — config, Rhythm, Conversations, Deals, Forecast, Analytics, Drift, integrations, admin, API. Use when asking 'how do I do X in Salesloft', configuring Salesloft settings, understanding Rhythm signals, setting up Analytics dashboards, managing Drift chatbots, or troubleshooting Salesloft integrations. Do NOT use for building cadences (use /sales-cadence), reviewing calls (use /sales-call-review), inspecting deals (use /sales-deal-inspect), or forecasting (use /sales-forecast).
Designer role. Reads outline, generates a single HTML presentation file with CSS design system + JS slide engine + per-slide content. Accepts visual references (URLs, screenshots, design specs) and extracts design signals to inform the isomorphic mapping. Use whenever the user says "design slides", "generate deck", "generate the deck", "build slides", "visual style", "reference this style", "like this design", "design", "generate slides", "visual style", "reference this style", or wants to turn an outline into actual slides.
Trigger: Call this skill when you need to collect opinions from multiple parties, integrate fragmented feedback into an actionable plan, or bring the plan back to real users/executors for validation. Common trigger signals include stakeholder input, user feedback, opinion summarization, alignment and verification. English: Trigger when input must be gathered from many people, synthesized into a clearer plan, and returned to the affected users or executors for validation. Use this skill for a collect-synthesize-validate loop.
Deep Angular 21 clean code audit with parallel specialist agents and senior team lead. Scans architecture, signals, stores, AI slop, ViewModel patterns, and more. Guarantees craftsman-level output. Use whenever the user says 'clean code', 'audit Angular', 'review frontend', 'check quality', 'anti-patterns', wants Angular code reviewed, or needs senior-level code standards enforced — even if they don't say 'clean code' explicitly.
Analyze cryptocurrency K-line trends with multi-timeframe technical analysis. Provides long-term analysis (4h/daily), trend detection, top/bottom identification, and short-term signals using Binance API.
Beat Editor for aibtc.news: review and approve/reject signals on assigned beat, file editorial reviews, manage beat cap via displacement, earn per-review sats
Invoke this when users react disproportionately intensely to losing (or about to lose) something, or feel an urgent need to "break even" and fail to cut losses after a loss. Typical trigger signals: sunk cost trap, gambler's doubling down, irrational bidding in auctions, inability to abandon failed projects with heavy resource investment. Not applicable to general investment valuation (use value-assessment) or herd behavior (use misjudgment-checklist).
Ultra-compressed PR review comments. One issue per line: Location • Problem • Fix. Remove preambles, prioritize signals. Supports Japanese. Trigger with "PR review please", "code review", "/review", "/genshijin-review". Candidate for automatic activation during pull request reviews.
Identify early warning signals of potential PR crises through pattern recognition, escalation triggers, and risk assessment
Triage mixed game demo and playtest feedback into a prioritized fix brief, weighted evidence summary, and next artifact recommendation. Use when a team has playtest notes, Steam Playtest responses, creator or streamer demo reactions, survey comments, wishlist/context signals, bug lists, or performance findings and needs to decide what to fix first before the next build, festival, or launch beat, even if they only say "sort our playtest feedback", "what should we fix before Next Fest", "players are confused", "streamers bounced off the demo", or "turn these demo notes into priorities".