Loading...
Loading...
Found 461 Skills
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.
Comprehensive SEO analysis for any website or business type. Performs full site audits, single-page deep analysis, technical SEO checks (crawlability, indexability, Core Web Vitals with INP), schema markup detection/validation/generation, content quality assessment (E-E-A-T framework per Dec 2025 update extending to all competitive queries), image optimization, sitemap analysis, and Generative Engine Optimization (GEO) for AI Overviews, ChatGPT, and Perplexity citations. Analyzes AI crawler accessibility (GPTBot, ClaudeBot, PerplexityBot), llms.txt compliance, brand mention signals, and passage-level citability. Industry detection for SaaS, e-commerce, local business, publishers, agencies. Triggers on: "SEO", "audit", "schema", "Core Web Vitals", "sitemap", "E-E-A-T", "AI Overviews", "GEO", "technical SEO", "content quality", "page speed", "structured data".
Methodology for defining product-qualified lead (PQL) signals, scoring, and routing.
Prospeo platform help — person enrichment, company enrichment, person search, company search, bulk enrichment, Chrome extension, LinkedIn Sales Navigator extraction, 5-step email verification, intent signals, API. Use when asking 'how do I do X in Prospeo', configuring Prospeo settings, managing enrichment, using the Prospeo API, or troubleshooting Prospeo issues. Do NOT use for building prospect lists (use /sales-prospect-list), enrichment strategy across tools (use /sales-enrich), cross-platform deliverability (use /sales-deliverability), or interpreting buying signals (use /sales-intent).
OSINT-based technology stack identification. Discovers company tech stacks using passive reconnaissance across 17 intelligence domains. Given a company name (and optional domain hint), infers frontend, backend, infrastructure, and security technologies using publicly available signals.
Invoke for ANY personal Bible devotion or scripture meditation request. This is a daily quiet time (QT) guide — use it whenever the user wants spiritual reflection on a Bible passage, NOT academic analysis. Common signals: asking for today's reading, wanting guided devotion, seeking stillness with scripture, mentioning a personal reading plan, or using terms like 靈修、靈糧、默想、嗎哪、 QT、quiet time、devotional. Even short or casual requests like just saying "QT" or "今天讀什麼" should trigger this skill. Delivers a first-century Jewish perspective devotional for mainstream Christians. Depends on bible-buddy skill. EXCLUDE: theological scholarship, academic exegesis, verse-by-verse analysis, sermon/teaching prep, translation comparison, comparative religion essays, or original-language research tasks — those belong to bible-buddy or bible-fact-check.
Searches the live web via Nimble APIs to monitor competitors and produce a structured intelligence briefing. Runs parallel searches for news, product launches, hiring signals, and funding — then compares against previous findings to highlight only what's new. Use this skill when the user asks about competitors, competitive intelligence, or what rival companies are doing. Common triggers: "what are my competitors doing", "competitor update", "competitor news", "competitive landscape", "market intel", "what's new with [company]", "track [company]", "competitor briefing", "who's making moves", "competitive analysis", "losing deals to [company]", "battlecard". Also use before board meetings or strategy sessions when the user wants competitive context. Requires the Nimble CLI (nimble search, nimble extract) for live web data. Do NOT use for single-company deep dives (use company-deep-dive), meeting prep with attendees (use meeting-prep), or non-business queries.