Update to Lukka Digital Assets Intel

{
  "description": "Resolve exchange pair codes to Lukka canonical pairs, or find how a Lukka pair is named across exchanges",
  "included_files": [],
  "name": "pair-mapping",
  "skill_md_contents": "---\nname: pair-mapping\ndescription: \"Resolve exchange pair codes to Lukka canonical pairs, or find how a Lukka pair is named across exchanges\"\n---\n\n## OpenAI connection notes\n\nTool identifiers below are raw operation names. The host may add a namespace;\nuse the matching advertised Global MCP tool. Resolve `<resolved-package-root>`\nto this plugin's installed directory before using paths. Workflow names identify\npackaged skills; they are not literal Claude slash commands.\n\nOriginal procedure tool scope: `refdata___get_pair_mappings`, `refdata___list_entities`.\n\n# pair-mapping workflow\n\n> See [CONNECTORS.md](../../CONNECTORS.md) for tool details.\n\n## Usage\n\npair-mapping workflow <user input>\n\nParse <user input> - can be:\n- A Lukka pair code: `XBT-USD`\n- An exchange-specific pair code: `BTC/USDT`, `XBTUSD`\n- An exchange name/code + pair: `KRAK XBT/USD`\n- An exchange code only: `KRAK` (returns all pairs for that exchange)\n\nUse canonical Lukka codes (`CPRO`, `KRAK`, `BINA`, ...) - never `COINBASE`.\n\n## Personas\n\n- **FX & Stablecoin Settlement**: Normalize obscure pairs (e.g. USDT/UAHG) for PnL and fiat on/off-ramp reconciliation\n- **Regulatory & Tax Reporting**: Translate every exchange pair into standard base/quote for capital gains and jurisdictional reporting\n\n## Flow\n\n### Case A: Resolve exchange pair -> Lukka canonical\n\n1. If a free-form exchange name is given, resolve to entityCode via `refdata___list_entities({ })` \n2. `refdata___get_pair_mappings({ entityPairCode: \"{code}\", entityCode: \"{code}\", mappingStatus: \"Active\", })` \n3. Returns: `lukkaPairCode`, `lukkaAssetOneCode` (base), `lukkaAssetTwoCode` (counter), direction\n\n### Case B: All exchange names for a Lukka pair\n\n1. `refdata___get_pair_mappings({ lukkaPairCode: \"XBT-USD\", mappingStatus: \"Active\", limit: 1000 })` \n2. Returns all entity-specific codes for that pair\n   - **`lukkaPairCode` is the Lukka identifier; `entityPairCode` is the exchange-side code** (e.g. Lukka `XBT-USD` == Binance `BTCUSD`). To confirm a specific exchange, pin `entityCode` too - do NOT conclude \"not mapped\" from a partial `lukkaPairCode`-only page (80+ venues on a flagship pair; page until `next` is null).\n\n### Case C: All pairs for an exchange\n\n1. `refdata___get_pair_mappings({ entityCode: \"{KRAK}\", mappingStatus: \"Active\", limit: 1000 })` \n\n### Supplemental search\n\nWhen the exact code is unknown, page through `get_pair_mappings({ entityCode: \"{code}\", mappingStatus: \"Active\", limit: 1000 })`  and filter client-side on the `entityPairCode` substring.\n\n## Output\n\n### Pair Mapping: {input}\n\n**Canonical Lukka Pair**: {lukkaPairCode}\n- Base asset: {lukkaAssetOneCode} ({assetName})\n- Counter asset: {lukkaAssetTwoCode} ({assetName})\n\n**Exchange Names** ({count} active mappings)\n| Exchange | Pair Code | Direction | Status |\n|----------|-----------|-----------|--------|\n| Kraken | XBT/USD | Standard | Active |\n| Binance | BTCUSDT | Reversed | Active |\n\n- Direction vocabulary: \"Standard\" = exchange base/counter matches Lukka pair order. \"Reversed\" = exchange pair is inverted relative to Lukka canonical. \"Ambiguous\" = cannot determine (rare, flag for review).\n\n**Notes**: {any reversed pairs, deprecated codes, or ambiguous mappings}\n- \"Ambiguous\" heuristic: when `lukkaAssetOneCode` and `lukkaAssetTwoCode` are both digital assets (no fiat counter), direction is determined by `pairDirection` field. If absent, mark as \"Ambiguous\".\n"
}