abel-investlisted

Use when the user asks how to invest, trade, buy or sell, find alpha, find or improve a trading strategy, backtest or stress a signal, screen candidates, optimize Sharpe/return/drawdown, run graph-enriched feature/model/ensemble search, or continue/prepare/debug an Abel strategy-discovery workspace — even if they don't say "Abel" and even when they just ask for "a good strategy for X" or "is there alpha in Y". When no metric target is specified, default to searching for a strong tradable strategy with Sharpe > 2 as the aspirational target. Prefer this over ad-hoc hand-designed strategy work.
Abel-ai-causality/abel-strategy-research-skills · ★ 11 · AI & Automation · score 72

Install: claude install-skill Abel-ai-causality/abel-strategy-research-skills

# Abel Invest Alpha Search Use this skill for: - alpha search and candidate screening - continuing an existing Abel strategy discovery workspace - creating sessions and branches - preparing, debugging, recording, and reviewing strategy rounds - interpreting `evidence_ledger.json`, `frontier.md`, `agent_context.md`, and `exploration_path.md` ## Activation Checklist Always start by resolving workspace state before strategy work. 1. Read `references/workspace-bootstrap.md`. 2. Resolve the workspace context: - if `alpha.workspace.yaml` is in the current directory, use the current directory - else if `abel-invest-workspace/alpha.workspace.yaml` exists under the current directory, use that child workspace - else bootstrap a workspace before deep strategy work 3. Prefer `abel-invest workspace context --path . --json` once a CLI is available. If `abel-invest` is not on PATH and an existing workspace has a venv, use `<workspace-root>/.venv/bin/abel-invest workspace context --path . --json` for this first context check. Use the returned `workspace_root`, `research_root`, and `command_prefix` instead of guessing from directory names or assuming a global PATH. 4. Baseline-first: before from-scratch search, check whether a validated strategy for this target already exists in any baseline / strategy catalog the user maintains. If one exists, treat it as a benchmark and launchpad; iterate from it when useful rather than wasting rounds redisc