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.

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

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

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".

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

Trace deprecated shim

Sigmoid Loss for Language Image Pre-Training

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

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.

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.

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.

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

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.

Debugging is the scientific method under time pressure.

ROACH v1.0 — Striker-only scanner. Stalker mode disabled entirely. Tests whether Stalker adds any value or is pure drag. Only trades violent FIRST_JUMP explosions backed by 1.5x volume. Will have long stretches of silence — that patience is the edge. All hardened gates preserved. XYZ banned. Leverage 7-10x. DSL exit managed by plugin runtime via runtime.yaml.

Resume an interrupted AgenTeam run with verify-first strategy.

当遭遇挫折、失败或结果不如预期时，用于将负面经验转化为成长燃料

FOX v2.0 — Dual-mode emerging movers scanner. All live trading lessons from Fox v1.0 applied, plus one experimental tweak: Stalker minReasons = 3. Stalker entries must have at least 3 distinct scoring reasons, not just pass the score threshold. This forces breadth of confirmation beyond the auto-awarded base climb score + one bonus. Stalker minScore 7, minTotalClimb 8, tighter Phase 1 for low-score entries, consecutive-loss streak gate. XYZ banned. Leverage 7-10x. DSL exit managed by plugin runtime via runtime.yaml.

Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>

Analyze complex systems through stocks, flows, and feedback loops to find high-leverage interventions. For organizational, environmental, social, and technical systems exhibiting circular causality. NOT for linear problems or simple cause-effect chains.