Loading...
Loading...
Found 1,744 Skills
Review the current branch diff for real bugs and security issues, verify findings against surrounding code, and report only issues that survive context checks. Runs as a forked review workflow so the audit has separate reasoning budget and stays isolated from the main task flow. Use when the user asks to find bugs, review changes, or audit branch risk.
Spatial storytelling and flow specialist - Masters layout theory, pacing architecture, encounter design, and environmental narrative across all game engines
McKinsey-style storyline framework for building presentation decks. Use when users need to structure presentations, pitch decks, or strategic communications. Creates logical flow where each storyline becomes a slide title, progressing from problem to solution.
Design the words in a product — labels, instructions, errors, confirmations, empty states, onboarding copy, tooltips, voice and tone frameworks, and content models. UX writing and content strategy as a deep discipline. Trigger when writing or reviewing UI copy, error messages, empty states, onboarding text, CTAs, tooltips, confirmation dialogs, or any user-facing text in a product. Also trigger for voice and tone frameworks, content models, microcopy patterns, inclusive language guidance, or asking "what should this say?" and "how should we sound?" Use this skill any time the words in an interface are the problem — not the flow they live in, not the structure they navigate, not the visual presentation.
End-to-end hotel booking with USDC wallet payment. Use when the user wants the agent to search, book, and pay for a hotel in one autonomous flow — phrases like "book me a hotel in Tokyo and pay with USDC", "find a place in Paris and pay from my wallet", "handle the whole booking for next week". Orchestrates: search → select → authenticate wallet → fund if needed → pay via x402 → confirm. Do NOT use for search-only, payment-only, or non-hotel bookings.
Use when user requests diagrams, flowcharts, architecture charts, or visualizations. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that benefit from visual representation. Generates .tldr JSON files and exports to PNG/SVG locally using @kitschpatrol/tldraw-cli.
Use when user requests diagrams, flowcharts, architecture charts, or visualizations. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that benefit from visual representation. Generates .excalidraw files and exports to PNG/SVG via Kroki API or locally using excalidraw-brute-export-cli.
Custom Watchlist Tracking Radar. Monitors users' custom watchlists and generates scheduled morning/evening briefings. Based on the Longbridge Open Platform, it scans 7-dimensional catalyst signals including earnings beats, policy changes, abnormal capital flows, insider trading, and analyst rating changes, and generates pre-market/post-market incremental briefings grouped by market. Supports four markets: US stocks, A-shares, Hong Kong stocks, and Singapore stocks. This skill is triggered when users ask investment-related questions such as "What should I pay attention to today?", "Show me the morning briefing", "Morning report", "Evening report", "Review", "Any news on my watchlist", "morning briefing", "catalyst update", etc.
Market microstructure analysis via Longbridge Securities — bid-ask spread, order-flow toxicity (large-order pressure), liquidity depth, price impact, and institutional order direction. Covers A-share call-auction analysis and HK block-trade mechanics. Triggers: "盘口分析", "微观结构", "订单流", "大单分析", "买卖价差", "逐笔分析", "买卖盘深度", "挂单墙", "主力动向", "集合竞价", "盤口分析", "微觀結構", "訂單流", "大單分析", "買賣價差", "逐筆分析", "買賣盤深度", "掛單牆", "主力動向", "market microstructure", "order flow", "bid-ask spread", "depth analysis", "large order", "order book imbalance", "price impact", "auction analysis", "institutional order flow".
Use when writing, fixing, or editing TypeScript async flows, promises, retries, timeouts, cancellation, shared mutable state across awaits, race conditions, or flaky async tests.
Produce implementation-ready UX and UI specifications: user flows, states, component briefs, design tokens, accessibility constraints, and handoff guidance for frontend engineering agents. Use for new features, redesigns, or design-system work where implementation should follow a clear product and interaction spec.
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this before'. Also use when you see `[memsearch] Memory available` hints injected via SessionStart or UserPromptSubmit. Typical flow: search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format. Skip when the question is purely about current code state (use Read/Grep), ephemeral (today's task only), or the user has explicitly asked to ignore memory.