Loading...
Loading...
Found 403 Skills
Comprehensive guide for creating Telegram Mini Apps with React using @tma.js/sdk-react. Covers SDK initialization, component mounting, signals, theming, back button handling, viewport management, init data, deep linking, and environment mocking for development. Use when building or debugging Telegram Mini Apps with React.
Analyse Datadog observability data including metrics, logs, monitors, incidents, SLOs, APM traces, RUM, security signals, and more. Use when asked to investigate infrastructure health, query metrics, search logs, check monitors, diagnose errors, or analyse any Datadog data.
Routes .NET/C# requests to the correct domain skill and loads coding standards as baseline for all code paths. Determines whether the task needs API, UI, testing, devops, tooling, or debugging guidance based on prompt analysis and project signals, then invokes skills in the right order. Always invoked after [skill:using-dotnet] detects .NET intent. Do not use for deep API, UI, testing, devops, tooling, or debugging implementation guidance.
Interpret Qwilr engagement signals and decide what to do next. Use when a prospect viewed or didn't view a proposal, analyzing Qwilr analytics, understanding proposal engagement patterns, figuring out why a buyer went dark after a proposal, deciding when to follow up after sending a proposal, understanding read receipts on proposals, or seeing who viewed a Qwilr quote.
Transaction-verified trading signals on Base. Register agent as signal provider, publish trades with TX hash proof, consume signals from top performers via REST API. All track records verified against blockchain data. No fake performance claims. Triggers on: "publish signal", "post trade signal", "register provider", "subscribe to signals", "copy trade", "bankr signals", "signal feed", "trading leaderboard", "read signals", "get top traders".
Generate a time-windowed pulse report on what users experienced and how the product performed - usage, quality, errors, signals worth investigating. Use when the user says 'run a pulse', 'show me the pulse', 'how are we doing', 'weekly recap', 'launch-day check', or passes a time window like '24h' or '7d'. Configures via .compound-engineering/config.local.yaml and saves reports to docs/pulse-reports/.
Earnings estimate revision analysis for listed companies via Longbridge — tracks analyst consensus revision direction (upgrade / downgrade), earnings surprise (SUE = standardised unexpected earnings), PEAD post-earnings drift signals (consecutive beats + upward revisions = positive momentum), and management guidance revision impact. Builds on raw data from longbridge-consensus. Triggers: "预期修正", "盈利修正", "分析师上调", "分析师下调", "超预期", "低于预期", "PEAD", "财报后漂移", "业绩意外", "管理层指引", "預期修正", "盈利修正", "分析師上調", "分析師下調", "超預期", "低於預期", "財報後漂移", "業績意外", "管理層指引", "earnings revision", "estimate revision", "analyst upgrade", "analyst downgrade", "beat miss surprise", "SUE", "PEAD post-earnings drift", "guidance revision", "estimate cut raise".
Helps engineering managers support direct report growth — produces a stage-by-stage model of engineering impact (Circles of Influence), a framework for non-linear career planning (Tarzan Method), diagnostic signals for stalled growth, conversation scripts for career talks, and a promotion readiness vs. timing distinction. Use when the user says "career growth," "promotion," "career path," "this person wants to grow," "career conversation," "what's next for this person," "career ladder," "IC vs manager track," "how do I help my report advance," "help someone grow," or "engineer wants a promotion." Do NOT use for formal written performance reviews or underperformance — use performance-reviews instead.
Use when adding, modifying, optimizing, or debugging CuTile autotuning code. Trigger signals: `exhaustive_search` / `replace_hints` / `hints_fn` / `cuda.tile.tune` in code, `autotune` in filenames, or correctness/performance issues in autotuned CuTile kernels. Covers: tune-once/cache/launch pattern, per-architecture configs (sm80–sm120), parameter space design (tile sizes, occupancy, num_ctas), and 7 common pitfalls with solutions.
Estimate Amazon monthly sales and revenue from a Best Seller Rank, and size a niche or competitor from observable signals. Explains the BSR-to-sales relationship, adjusts by category and price, and returns a sales range with a confidence note. Use when a user asks how many units a product sells, to estimate sales from BSR, size a market or niche, gauge a competitor's volume, or judge demand. Trigger phrases: "sales estimate", "how many units", "estimate from BSR", "best seller rank", "market size", "competitor sales", "monthly sales". Works with zero tools. the user provides BSR, category, and price.
Predict market/tech/business-model trends and market-entry timing (enter/wait/avoid) by analyzing 2-3 years of signals to forecast 1-2 years ahead; use for questions like market timing, trend trajectory (rising/peaking/declining), adoption curve stage, or what comes next.
Orchestrate jobs via depth propagation, parallel decomposition, relations, and control signals