Loading...
Loading...
Found 41 Skills
Enforces complete execution, mode-aware delivery, compact sub-agent communication, independent agent-review gating, validation, and reporting for implementation, bugfix, hardening, documentation, specification, architecture, design, review, and post-mortem tasks. Use whenever work must be completed, reviewed, validated, or documented through an explicit execution mode instead of handled ad hoc.
Expert Site Reliability Engineer specializing in SLOs, error budgets, and reliability engineering practices. Proficient in incident management, post-mortems, capacity planning, and building scalable, resilient systems with focus on reliability, availability, and performance.
Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually went wrong.
Personal US-equity options trading knowledge base. Use for trade analysis, options strategy recommendations, earnings plays, post-mortems, or ticker mentions in a trading context (e.g., "analyze APP", "sell put on TSLA", "structure for NVDA earnings"). Triggers on multi-leg options (Jade Lizard, bull put spread, iron condor, diagonal, calendar), IV / IV crush, channel checks, earnings positioning, AH action, LEAPS / stock replacement, dealer GEX / gamma exposure / max pain / options chain analysis, or any single-stock options play. Provides concrete strikes, IV-aware structures, and probability -weighted scenarios drawn from 21 trading pitfalls, a gamma framework, and case studies (INTC, Mag-7, APP, NOK, CBRS). Market data via TradingView + Funda AI. Responds in Chinese with English technical terms. **Always sanity-check net vega sign before recommending a directional structure** — wrong vega (credit spread at low IVR, debit spread at high IVR) is a known failure mode; see pitfall 19.
Guide incident response from detection to post-mortem using SRE principles, severity classification, on-call management, blameless culture, and communication protocols. Use when setting up incident processes, designing escalation policies, or conducting post-mortems.
Generate self-contained, beautiful HTML documents that replace walls of markdown. Use this skill whenever the user asks for a report, comparison, explainer, slide deck, diagram, post-mortem, status update, code walkthrough, design system showcase, prototype, or interactive editor — or mentions creating HTML outputs, dashboards, visual documentation, or "instead of markdown". Covers 10 battle-tested patterns: comparison, walkthrough, review, design-system, prototyping, diagram, deck, explainer, report, and editor.
Gain wisdom from setbacks — Go through the 5-step interactive reflection (Setback → Automatic Output → Old Weights → New Parameters → Alternative Action), move from "emotional review" to "behavioral training", and update the L3 weights of your first reactions. Use when Wang Jianshuo reflects on a personal setback, mistake, or recurring pattern (reflection, post-mortem review, review, draw lessons, learn from a setback, gain wisdom, "I messed up again", "Why does this keep happening?", "Why do I always…?", "I can't just let it go", "I know the principles but can't put them into practice"). For the user as a human, not for Claude's task post-mortems.
Investigates completed DEX sandwich-style MEV from public blocks and bundles—front-victim-back ordering on EVM and Solana, Jito bundle traces, swap decoding, victim slippage vs searcher profit estimates, and evidence-style case studies. Use when the user asks for sandwich attack analysis, MEV sandwich post-mortems, high-slippage swap forensics, or searcher clustering—not for building sandwich bots, mempool manipulation for profit, or harassing labeled wallets.
Use when reviewing, scoring, or auditing third-party SaaS / vendor relationships — running a vendor scorecard, tracking SLA compliance, classifying third-party risk, preparing a tier-1 vendor review, or auditing the SaaS portfolio. Triggers on "vendor SLA", "vendor scorecard", "third-party risk", "TPRM", "vendor review", "SaaS audit", "supplier performance", "vendor health check", "renewal review". Forks context so large vendor catalogs (50-500 line items) and SLA logs don't pollute the parent thread. Ships 3 stdlib-only Python tools (vendor scorer with industry tuning, SLA compliance tracker with credit-claim flags, vendor risk classifier across 4 risk vectors), 3 reference docs each citing 7+ authoritative sources (Gartner / Shared Assessments / NIST / ISO 27036 / breach post-mortems), and a 5-vendor catalog template. Distinct from c-level-advisor/general-counsel-advisor (contract law, not operational management), business-growth/contract-and-proposal-writer (outbound proposals, not inbound vendor scoring), and sibling procurement-optimizer (spend categorization, not vendor performance).
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.
Creates a structured lessons learned entry for organizational memory. Use after projects, incidents, or significant learnings to capture knowledge for future teams and initiatives.
Post-mortem analysis for any Intelligems A/B test. Extracts learnings from funnel data, segment patterns, and customer behavior — then suggests what to test next based on findings.