Update to Keel

{
  "description": "Find the Keel component(s) that implement a concept the user names: search by concept, batch the candidates' schemas, show what precedes and follows the best one. Use when the user asks \"what component does X\", \"is there a way to Z\", \"find a component for Y\", or names a trading concept and wants what implements it. Not for composing a strategy (strategy-creation) or for one already-named component (keel_components_get).\n",
  "included_files": [],
  "name": "component-discovery",
  "skill_md_contents": "---\nname: component-discovery\ndescription: |\n  Find the Keel component(s) that implement a concept the user names: search by concept, batch the candidates' schemas, show what precedes and follows the best one. Use when the user asks \"what component does X\", \"is there a way to Z\", \"find a component for Y\", or names a trading concept and wants what implements it. Not for composing a strategy (strategy-creation) or for one already-named component (keel_components_get).\nreferences:\n  - step: 2\n    topic: \"types\"\n    why: \"the type universe, when a filtered typed search proves absence (reference/)\"\n  - step: 4\n    topic: \"composition_mechanics\"\n    why: \"how the candidate wires: slot-reading components, Parallel partners, the two mask systems\"\n  - step: 4\n    topic: \"slots\"\n    why: \"slot reads/writes semantics for a slot-reading candidate (reference/)\"\n  - step: 4\n    topic: \"strategy_patterns\"\n    why: \"the pattern a candidate usually lives in\"\ntools:\n  - keel_components_search\n  - keel_components_get_many\n  - keel_components_get\n---\n\n# References\n\nReference topics this workflow cites (keel_help topics):\n\n- Step 2 — `types` — the type universe, when a filtered typed search proves absence (reference/)\n- Step 4 — `composition_mechanics` — how the candidate wires: slot-reading components, Parallel partners, the two mask systems\n- Step 4 — `slots` — slot reads/writes semantics for a slot-reading candidate (reference/)\n- Step 4 — `strategy_patterns` — the pattern a candidate usually lives in\n\n# Method\n\n## Step 1 — Translate words into a concept\n\n\"Beta hedge\", \"trailing stop\", \"regime detection\", \"Kalman filter\" — search\nfor the concept, not the literal word; the search is semantic and the catalog\nholds names (`BetaHedgeAllocator`, `TrailingStopExit`, `FundingLevelRegime`)\nthat no pattern doc lists. A name from another platform is translated to the\nKeel concept first.\n\n## Step 2 — `keel_components_search`\n\nQuery the concept; narrow with `category`, `input_type` / `output_type`\n(a filtered typed search is exhaustive — an empty one is the evidence for \"no\ncomponent does X\"; a thin keyword search is not), or `clock_direction`.\nSurface the top 3–5, ranked, with one line each. Nothing fits → say \"the\nclosest is X but it does not cover Y\"; never fabricate a fit.\n\n## Step 3 — Batch the candidates\n\n`keel_components_get_many(names=[...])` once for the 3–5 candidates: full\nparams, types, slot reads/writes, examples, pitfalls, version — compared side\nby side. A single component the user already named →\n`keel_components_get(name=<name>)` is cheaper. Note when a locked version\ndiffers from the latest; changing a pinned version is the user's call.\n\n## Step 4 — Show how it wires\n\n`keel_components_search(after=<name>)` lists what can follow the candidate;\n`(before=<name>)` what can precede it. A component alone is half the answer —\nwhat feeds it and what consumes it is the other half. For a slot-reading\ncandidate (`entry_slot`, `ohlcv_slot`), say which earlier `Store` it needs.\n\n## Step 5 — Where discovery ends\n\nThis workflow ends at discovery. Building a new strategy with the component is\nthe `strategy-creation` workflow; adding it to an existing one is\n`strategy-fork-and-iterate`.\n\n# Decision points\n\n- Universe / asset-filter questions are discovery like any other; there is no\n  separate universe skill.\n- The catalog is the truth, not training data: a component you have not seen\n  in a result this session is not asserted to exist — or not to.\n\n# Output shape\n\n1. One-sentence interpretation of the concept.\n2. Top 3–5 candidates: name × one line × category.\n3. For the leading candidate: param highlights and 1–2 example usages.\n4. What precedes and follows it.\n5. If the user wants to build with it: `strategy-creation` (new strategy) or\n   `strategy-fork-and-iterate` (existing strategy).\n\n# When NOT to use\n\n- Building a strategy → `strategy-creation`.\n- One named component → `keel_components_get` (or\n  `keel://components/<name>/schema` where the host browses resources).\n- A failing strategy → `recover-from-error`; discovery fixes no validation\n  error.\n\n# Test prompts\n\n1. \"Is there a component for beta hedging in Keel?\"\n2. \"How do I add a trailing stop to my strategy?\"\n3. \"What components handle regime detection on funding rates?\"\n"
}