Loading...
Loading...
Found 10,827 Skills
Investigate transcription factor binding, cis-regulatory elements, chromatin accessibility, and regulatory variant annotation. Use when asked about TF binding sites, enhancers, promoters, ChIP-seq data, ATAC-seq signals, candidate cis-regulatory elements (cCREs), or the regulatory impact of genomic variants.
Help users integrate Runway audio APIs (TTS, sound effects, voice isolation, dubbing)
When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.
How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.
Use when naming or renaming TypeScript identifiers, especially cryptic names, ambiguous parameters, I-prefixed interfaces, Hungarian notation, misleading side effects, or requests for clearer names.
Design high-level functional and technical specifications by defining scope, modules, contracts, boundaries, responsibilities, architecture models, constraints, and verification criteria.
Explains business financial terms and frameworks for engineering managers — produces term definitions (ARR, COGS, CAC, LTV, gross margin, burn rate, EBITDA, AARRR), translation formulas for making engineering work visible in business language, and a three-layer framework for building business credibility. Use when the user says "business terms," "EBITDA," "burn rate," "CAC," "LTV," "gross margin," "ARR," "how do I speak to business people," "I don't understand finance," "make the case for engineering work," "connect engineering to business outcomes," "talk to the P&L owner," or "business impact." Do NOT use when the user wants to connect engineering metrics (DORA, velocity) to business metrics — use developer-productivity instead.
Performs a structured code review on the current diff or specified files. Checks for correctness, security vulnerabilities, test coverage, code style, and adherence to the project's architecture patterns. Invoked when the user asks for a review, code check, pr review, or quality assessment.
Help users discover and install Claude Code skills. Use this skill when users ask "how to do X", "find a skill that can do X", "are there any skills that can..." or want to expand AI capabilities. Search, verify quality, and assist with installation through the skills.sh ecosystem.
ARK-style single-stock disruptive-innovation diagnostic. Suitability gate on 4 dimensions (platform fit / innovation revenue / R&D intensity / management vision); if it passes, builds TAM (low/base/high), Wright's-Law cost curve with sourced learning rate, three-scenario 5-year target (Bull/Base/Bear, 15% discount), risks, conditional action frame. Data: Longbridge CLI first, MCP fallback, WebSearch only for TAM / learning rates / industry runway. Runs cross-statement reconciliation BEFORE analysis. Closes with a data-source appendix whose final row is the reconciliation summary. Independent implementation — not affiliated with ARK Invest. Triggers: "木头姐", "ARK", "ARKK", "颠覆式创新", "莱特定律", "TAM", "5年目标价", "情景分析", "AI 与大数据", "自动化与机器人", "能源存储", "基因革命", "区块链与金融科技", "木頭姐", "顛覆式創新", "萊特定律", "5年目標價", "Cathie Wood", "ARK Invest", "disruptive innovation", "Wright's Law", "learning rate", "bull base bear", "scenario analysis".
List all installed EvoNexus plugins with status, version, and update availability. Use when the user asks about installed plugins, wants an inventory, or mentions plugins generally. Triggers on "quais plugins tenho", "list plugins", "plugins instalados", "o que tem instalado".
Implement a conformance-test runner script (Bash on macOS/Linux, PowerShell on Windows) for an arbitrary programming language, in one of two variants: install-inline (when no prepare_environment_<lang> script exists) or activate-only (when one does). Use when the user wants to add a conformance-test runner for a new language (Node.js, Go, Rust, Flutter, etc.) to a ***plain project, or wants to regenerate / adapt one of the existing runners.