cuckoo-strategy
CUCKOO v1.0.0 โ Copy-the-Copiers (meta-strategy follower). Auto-discovers the top strategies by realized performance (discovery_get_top_strategies), pulls each one's current positions, and trades the asset + direction the top performers agree on most โ performance-weighted, so a stronger strategy gets more say (capped so one outlier can't dominate). Because the strategies it follows are themselves copy/algo strategies, Cuckoo copies the copiers. Distinct from Remora (operator-picked whales) and the individual trader- followers. NEW archetype #14. Let-winners-run DSL with a staleness cap.
What this skill does
# ๐ฆ CUCKOO v1.0.0 โ Copy-the-Copiers (Meta-Strategy Follower) **Let the best strategies do the work.** A cuckoo lays its eggs in other birds' nests. Cuckoo lets the platform's top-performing *strategies* find the trades, then rides whatever they agree on most โ weighted by how well each one is actually doing. ## Why this strategy exists Following a single trader (Remora) or a leaderboard universe (Raptor/Jackal/Spider) is one layer. Cuckoo is a layer *above* that: it follows the top-performing **strategies** โ which are themselves copy/algo/trader-following strategies โ so it captures the *consensus of the consensus*. When the best strategies on the platform are independently piling into the same asset+direction, that agreement is a strong, self-cleaning signal: underperformers fall out of the top-N automatically, so the pool refreshes toward whatever is working. ## CRITICAL RULES ### RULE 1: Auto-discovered, not hand-picked Cuckoo pulls the top `topN` strategies by realized performance every tick (`discovery_get_top_strategies`). There is no operator whale list (that's Remora) โ the pool is *discovered* and refreshes as performance changes. ### RULE 2: Performance-weighted consensus Each top strategy casts one vote per `(asset, direction)` it holds above `minNotionalUsd`, weighted by `performance_weight(roi) = clamp(1 + roi/50, 0.5, weightCap)`. A flat strategy weighs 1.0; a +100% strategy hits the cap; a losing strategy floors at 0.5. The cap stops one outlier from dominating. ### RULE 3: Consensus is the gate Votes are tallied into `(asset, direction)` candidates. Entry requires at least `minStrategies` (default 2) top strategies in agreement โ one strategy's position is never enough. ### RULE 4: Producer enters. DSL exits. No `close_position` call site. The top strategies hold conviction positions, so the DSL is the **let-winners-run** preset โ wide ladder (T0 +10% / lock 0), `max_loss 18%`, time-cuts OFF except a **96h hard_timeout** staleness cap. โ ๏ธ Cuckoo re-evaluates the consensus each tick but does **not yet mirror an EXIT** โ the hard_timeout prevents holding a stale consensus indefinitely. Exit-mirroring is a planned v1.1 enhancement. ## How Cuckoo scores a trade **Gate:** `>= minStrategies` top strategies hold the same `(asset, direction)`. **Score components** (max ~6): | Signal | Points | |---|---| | Held by at least one top strategy | +2 | | Consensus: 2 strategies agree | +1 | | Consensus: 3 strategies agree | +2 | | Consensus: 4+ strategies agree | +3 | | Aggregate consensus weight โฅ `highWeight` (default 6.0) | +1 | **Floor:** `minScore: 4` (so a 2-strategy consensus needs the high-weight bonus, or 3+ strategies, to clear). ## DSL preset (let-winners-run โ with a staleness cap) | Phase | Component | Setting | |---|---|---| | Phase 1 | max_loss_pct | 18% | | Phase 1 | retrace_threshold | 10 | | Time cuts | hard_timeout | **96h (staleness cap)** | | Time cuts | weak_peak_cut | DISABLED | | Time cuts | dead_weight_cut | DISABLED | | Phase 2 | T0 โ T4 | +10/0 ยท +20/45 ยท +35/65 ยท +55/78 ยท +90/88 | ## Scanner pattern Introduces the **Meta-strategy follower / copy-the-copiers** archetype (#14) โ see `senpi-trading-runtime/references/producer-patterns.md`. Primary MCP calls: `discovery_get_top_strategies` (the producer signature; defensive multi-key unwrap of the strategy list), `leaderboard_get_trader_positions` (each top strategy's positions; unwraps the nested `data.positions.positions` shape). The pure functions (`performance_weight`, `mirror_direction`, `tally_consensus`, `consensus_score`) are unit-tested in `tests/test_signal.py`. ## Operator install See [README.md](README.md). ## Changelog ### v1.0.0 (2026-05-26) โ initial release First fleet agent to follow the auto-discovered top STRATEGIES (not individual traders) and trade their performance-weighted consensus โ the copy-the-copiers meta-layer, a new archetype. Let-winners-run DSL class (wide ladder, time-cuts off except a 96h staleness cap), taker-true entry, no null numeric signal fields, defensive multi-key shape unwrapping on `discovery_get_top_strategies` + `leaderboard_get_trader_positions`, and unit-tested pure functions. Exit-mirroring is a planned v1.1 enhancement. ## License MIT โ Copyright 2026 Senpi (https://senpi.ai). ## Skill Attribution When creating a strategy, include `skill_name` and `skill_version`. See `references/skill-attribution.md`.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing โ use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.