Results for “losing-streak”

Analyze closed deals and lost opportunities for patterns

Use to extract competitor mentions, switching language and feature-gap evidence from support conversations as an input to win/loss and product strategy. Trigger for "what competitors do customers mention", "why do customers switch away", "find feature gaps customers ask about", competitive intelligence from support, or win/loss analysis that only samples deals sales remembers.

当感到生活失控、注意力分散，需要系统性重获专注力时

Find the earliest decisive failure in an agent run trace and propose an evidence-backed targeted repair. Load when a run failed, results are wrong, or the user asks what went wrong in an agent session. Also triggers on "localize the fault", "first incorrect step", "debug this run", "trace attribution", "why did the agent fail", or after run-trace captures errors. Pairs with debug-and-fix for code defects and dynamic-routing for plan faults.

Manages automated dynamic/trailing stop losses (DSL only) for leveraged perpetual positions on Hyperliquid. Default mode: High Water (pct_of_high_water) — the trailing floor is a percentage of the peak ROE, recalculated every tick, no ceiling. Also supports fixed ROE tiers for legacy positions. Monitors price via cron, ratchets profit floors through configurable tiers, syncs the stop loss to Hyperliquid via edit_position, and auto-closes positions on breach via mcporter. Supports LONG and SHORT, strategy-scoped state isolation, and automatic cleanup.

LEMON v2.0 — The Degen Fader. Identifies historically reckless traders (DEGEN activity + CHOPPY consistency) on Hyperliquid, monitors their live positions, and counter-trades them when they're bleeding at high leverage. If a cluster of degens goes max-leverage long on a coin and starts losing, LEMON shorts it — betting on their inevitable liquidation cascade. DSL exit managed by plugin runtime via runtime.yaml.

JAGUAR v3.0 — Striker-Only. Stalker and Hunter removed. Pyramiding removed. v1.0 lost -29.3% across 5 trades. 4 of 5 had broken DSL (missing size field in state file). v2.0 fixes DSL state generation with wallet+size fields, reduces leverage to 7x, and focuses exclusively on STRIKER signals (violent FIRST_JUMP explosions, score 9+, volume 1.5x). DSL exit managed by plugin runtime via runtime.yaml.

Almost every downstream bug traces back to an index that was assumed regular and

Produce displace/team/ghost talk tracks for the incumbent on a recompete pursuit. Use when user wants competitive angles saved to the pursuit vault; optional multi-turn LLM for customer-facing phrasing.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

Choose and audit startup metrics using the Lean Analytics framework: separate actionable metrics from vanity metrics, identify the One Metric That Matters for your business model and stage, set targets, and plan instrumentation.

当意识到自己处于长期迷茫、缺乏动力阶段，需要系统性方法走出困境时

Linkable-Asset Skill — data studies that pull links (Lesson 7)

Trace deprecated shim

Debug LangChain and LangGraph agents by fetching execution traces from LangSmith. Analyze agent behavior, investigate errors, and review tool calls and performance metrics.

Sigmoid Loss for Language Image Pre-Training

Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences.

Creates or resumes a HANDOFF.md so a fresh Claude Code session can continue work without repeating dead ends, with strict anti-hallucination verification.

Weekly engineering retrospective. (gstack)

WOLVERINE v2.0 — HYPE alpha hunter. Entry-only scanner, DSL-exit-only architecture. v1.1 lost -22.7% because the scanner's thesis exit chopped 25/27 trades before DSL could manage them. v2.0 removes thesis exit entirely. Scanner decides entries (score 8+, 4H/1H aligned, SM consensus). DSL manages all exits (wide Phase 1 for HYPE volatility, trailing tiers starting at +15% ROE). Leverage lowered to 7x. Max 4 entries/day. 3-hour cooldown between entries. DSL exit managed by plugin runtime via runtime.yaml.

当需要在多个领域积累独特竞争优势，避免单一技能风险时

Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.

Harness Strategy

Conduz investigação de incidentes com método: triagem, hipóteses, mitigação, RCA e postmortem, priorizando evidências e confirmação humana.

Select alternative execution paths when a plan step fails — branch on outcomes instead of blind retry. Load when a structured plan step fails, an unexpected observation arrives, or the user asks what to try next after an error. Also triggers on "try another approach", "route around this failure", "replan on failure", "if X fails try Y", or outcome-based branching during multi-step work. Pairs with structured-planning and debug-and-fix. Does not replace root-cause debugging — adds plan-level path selection.

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

Graceful degradation when primary approach fails. Try alternates in priority order; record which path succeeded for future routing.

Turn "which leads should I work?" into a lead-by-lead work plan. Per-lead status (never-touched, engaged-not-replied, gone-cold, hot), days-dark per lead, last-touch quality, a re-engagement ranker, and a recommended next action for every lead. Built for SDRs and full-cycle reps, customizable to your CRM and your outreach tool. Trigger on "which leads should I work?", "who haven't I touched?", "show me cold leads", "hot leads to follow up on", "who's gone dark?", "re-engagement candidates", or any lead-level work-assignment question.

Documents Linear's dark-canvas marketing design system with near-black backgrounds, lavender-blue accent, four-step surface hierarchy, aggressive negative tracking on display type, and product UI screenshots as the primary visual rhythm.

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

Recover a PR whose head SHA disagrees with its branch ref (webhook desync). Force-push and close+reopen rarely fix it — recreate the PR.

Turn scattered closed deals into a win/loss program that changes what you ship and what you say. Picks who to interview, gives you the question guide, codes themes across deals so a pattern beats a single anecdote, and turns the pattern into a specific messaging or product change. Built for B2B GTM, product, and RevOps leaders, customizable to your motion and your CRM. Trigger on "start a win-loss program", "why are we losing deals", "run win-loss interviews", "what patterns are in our closed-lost", "who should I interview", or any win/loss or closed-deal analysis.

GRIZZLY v3.0 — BTC Alpha Hunter. Tightened configs. 7x leverage. 360-minute timeout. No thesis exit. Plugin runtime DSL.

Implements a complete observability stack with Prometheus metrics, Grafana dashboards, Jaeger distributed tracing, and structured logging, including heartbeat-based absence detection for scheduled jobs on Google Cloud.

Use to design overnight and follow-the-sun support — coverage models, handoff quality and measuring what is lost between shifts. Trigger for "after-hours coverage", "follow the sun", overnight support design, night shift vs defer async, handoff packet, shift handover quality, global coverage gaps, or when customers reopen tickets after every handoff.