Loading...
Loading...
Found 1,937 Skills
Initialize a Harness Engineering framework in the current project. Use when user says 'harness', 'init harness', 'initialize framework', 'setup harness engineering', '/harness', or wants to set up a Plan-Build-Verify development workflow with specialized agents (planner, generator, evaluator). Creates CLAUDE.md, agent definitions, command templates, hooks, and documentation structure for autonomous AI-driven development.
Use when evaluating ideas in voting phase. Be aggressive - score misaligned or poor ideas low enough to veto, score weak proposals below approval, score strong aligned ideas high. First check directive, then vote.
Describe what an existing SigNoz alert rule does in plain language — the signal it watches, the threshold and evaluation behavior, the notification routing, and a one-line fire-frequency summary so the user knows whether the alert has been active. Make sure to use this skill whenever the user asks "what does this alert do", "explain alert X", "walk me through this rule", "how does my [Y] alert work", "is this alert configured correctly", or otherwise asks for an interpretation of an existing alert's configuration. Static explanation only — for diagnosing a specific firing incident, use `signoz-investigating-alerts`.
Industry / sector panorama report — generates a comprehensive industry overview covering market dynamics, competitive landscape, key players, thematic trends, valuation ranges, and catalysts/risks. Outputs industry sizing, growth rate, major-player market share estimates, and valuation bands. Triggers: "行业概览", "行业报告", "板块报告", "行业全景", "竞争格局", "行业分析", "板块分析", "行業概覽", "行業報告", "板塊報告", "行業全景", "競爭格局", "industry overview", "sector overview", "industry report", "sector analysis", "market landscape", "competitive landscape", "industry sizing", "sector deep dive", "semiconductor industry", "AI sector overview".
Expert evaluator for Grafana Loki label strategy. Audits, designs, and improves label schemas using cardinality scoring, access-pattern alignment, static vs. dynamic label rules, and consistency checks. Use when the user asks to evaluate, audit, design, or improve a Loki label strategy — or asks why their Loki queries are slow.
Elliott Wave technical timing analysis for individual stocks. Identifies current wave cycle position (impulse 5-wave / corrective ABC), validates with Fibonacci ratios, confirms with momentum indicators (MACD, RSI, volume divergence), and evaluates market environment per market (HK / US / A-share / SGX). Outputs structured natural language report with Fibonacci price zones and actionable reference. Triggers on "波浪分析", "艾略特波浪", "Elliott Wave", "波浪周期", "wave analysis", "技术择时", "technical timing", stock ticker + wave/timing keywords, "现在是第几浪", "处于哪个波浪", "波浪判断", "波浪理论", "浪形分析", "波浪择时".
Use when writing or reviewing n8n expressions (`{{...}}` syntax), `$json` / `$node` references, Luxon date code, or expression errors. Triggers on `{{}}`, `$json`, `$node`, `$input`, `DateTime`, `Luxon`, "expression error", "evaluating", "format date", "transform field", or any node-parameter assignment.
Guides senior system and solution architecture—cross-service boundaries, integration patterns, non-functional requirements (scale, reliability, security, cost), ADRs, C4-style modeling, architecture review, build-vs-buy, and phased migration (strangler, dual-write). Use when designing multi-service systems, evaluating platform or vendor choices, writing or reviewing architecture decision records, defining standards and principles, or assessing technical risk across domains—not for single-service RFCs and module design (senior-software-engineer), data platform or mesh decisions (data-architect), cloud landing zone, Well-Architected, and migration architecture (cloud-architect), cloud/IaC implementation (infrastructure-engineer, cloud-engineer), internal developer platform product (platform-engineer), or program tracking (technical-program-manager). For business strategy and cases, use business-consultant; for applied AI (RAG, agents, copilots), use applied-ai-architect-commercial-enterprise.
Guides corporate legal support—entity structure, board and stockholder governance, corporate resolutions and minutes, equity and cap table mechanics, corporate policies, intercompany arrangements, and corporate closing checklists for financings or M&A. Use when drafting board materials, reviewing governance documents, entity formation or subsidiary setup, stockholder consents, option plan mechanics, D&O considerations at checklist level, or corporate approval packages—not for B2B MSAs and vendor/customer redlines (commercial-counsel), SOC/ISO evidence (compliance-engineer), tax/accounting treatment (senior-revenue-accountant), or employee HRIS and lifecycle operations (people-operations-specialist). For live deal execution—diligence coordination, closing matrix, signing, funds flow—use transaction-manager. For deal thesis, valuation, and negotiation mandate, use transaction-principal. Output is drafting assistance; human counsel must approve binding actions.
End-to-end pipeline from unlabeled ml_app traces to a bootstrapped evaluator suite. Runs trace classification → root cause analysis → eval bootstrap in sequence with user checkpoints. Use when user says "run the eval pipeline", "go from traces to evals", "bootstrap evals end to end", "classify then RCA then bootstrap", "build an eval set from scratch", or wants a guided walkthrough from production data to evaluator code.
Screen core candidate stocks with high capital returns, stable moats, long-term compound interest potential, and strong earnings quality, and output priorities, valuation disciplines, and key points for continuous tracking. Applicable to scenarios such as long-term core position stock selection, compound interest asset pool construction, and high-quality company comparison.
Expert evaluator for Prometheus label strategy. Audits, designs, and improves label schemas using cardinality scoring, access-pattern alignment, static vs. dynamic label rules, histogram bucket discipline, instrumentation hygiene, and source-side prevention via relabel_config / metric_relabel_configs. Use when the user asks to evaluate, audit, design, or improve Prometheus labels — or asks how to prevent high cardinality at the source. For post-ingest aggregation, see the adaptive-metrics skill. For "why is my Prometheus slow / expensive right now" triage, see prometheus-cardinality-troubleshooter.