trading-skills-navigator

---
name: trading-skills-navigator
description: Use when a user states a trading/investing goal and asks where to start, which skill or workflow to use, what works without paid API keys, or needs routing by persona or time budget.
category: Strategy R&D
version: 1.0.0
tools: []
---

# Trading Skills Navigator

The interactive on-ramp to this skill library. Turn a user's goal into a concrete recommendation: which workflow to run, which skillset (category) it belongs to, its API requirement, and the setup path. Router only — never execute trades, place orders, or auto-run other skills.

## When to Use

- The user states a trading/investing goal and asks where to start or which skill/workflow fits
- The user asks what works without paid API keys
- The user wants the no-API vs API path separated, or a beginner path
- The user describes a persona ("part-time swing trader," "dividend investor," "I want to short," "I want to backtest ideas") and needs routing

## Methodology

**Step 1 — Capture goal and constraints.** Extract the natural-language goal verbatim, plus any stated constraints: no-API only, a daily time budget (15/30/60/90 minutes), and experience level (beginner/intermediate/advanced). Ask at most one clarifying question, and only if the goal is empty or has no discernible intent — otherwise proceed; the recommendation degrades gracefully with partial information.

**Step 2 — Match to a workflow.** Score available workflows against the goal, weighing: topical fit, whether the workflow satisfies a no-API constraint if requested, whether it fits the stated time budget, and whether it suits the stated experience level. Identify one primary workflow and, if relevant, secondary supporting workflows.

**Step 3 — Narrate the recommendation.** Explain plainly: what the primary workflow does, its cadence and rough time cost, and its API profile. If secondary workflows apply, explain how they relate (e.g. "run the regime check first, then this when it allows risk"). Identify the skillset/category the recommendation belongs to.

**Step 4 — Be explicit about API requirements.** State whether the *entire* recommended path (primary + every secondary workflow) works without paid API keys, or name exactly which paid key(s) it needs. If a workflow was excluded for a no-API request, say which paid integration it needed.

**Step 5 — Handle honest gaps.** If no workflow genuinely covers the stated intent, say so directly rather than force-fitting a recommendation — then suggest the closest-fitting skills from the relevant category and explain the gap plainly. Never invent a workflow that doesn't exist.

**Step 6 — Explain the setup path.** Walk through what to install: required skills first, then recommended, then optional — citing why each is needed and how the bundle is run together. Union the install list across the primary skillset and every secondary workflow so nothing needed gets dropped.

**Step 7 — Point to the improvement loop.** Close by connecting the recommended path to the ongoing Plan → Trade → Record → Review → Improve loop, so the user has a way to keep learning from results over time, not just a one-off recommendation.

## Output

Narrate conversationally, always covering: primary workflow (what/when/cost), secondary workflows (if any) and how they chain, skillset/category, explicit no-API-vs-API verdict for the whole path, honest-gap handling if applicable, the setup/install path, and the pointer to the improvement loop. Always explain *why* — the rationale behind the recommendation, not just the recommendation itself.