Update to Lukka Digital Assets Intel

{
  "description": "Bulk resolve white paper codes to Lukka asset codes and prices",
  "included_files": [],
  "name": "resolve-assets",
  "skill_md_contents": "---\nname: resolve-assets\ndescription: \"Bulk resolve white paper codes to Lukka asset codes and prices\"\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: `pricing___get_latest_prices`, `refdata___get_asset_by_id`, `refdata___get_asset_mappings`.\n\n# resolve-assets workflow\n\n> See [CONNECTORS.md](../../CONNECTORS.md) for tool details.\n\n## Usage\n\nresolve-assets workflow <user input>\n\nParse <user input> as comma-separated white paper codes.\n\n## Flow\n\nUses the **asset-resolver** skill workflow. Resolution path: alias map -> `get_asset_mappings(entityAssetCode)` -> `get_asset_by_id`. The input is a **street ticker**, not a `lukkaAssetCode` - resolving a raw ticker through `lukkaAssetCode` returns the oldest (often inactive) holder of a collided code (the older migrated asset, never the current one). Aliases (BTC -> XBT, SOL -> SOLN, GALA -> GALAT3) are unique canonical codes and resolve directly.\n\n1. **Per ticker**:\n   - In alias map -> use the unique canonical code: `get_asset_mappings({ lukkaAssetCode: \"{alias}\", mappingStatus: \"Active\", limit: 200 })`.\n   - Not in alias map -> raw ticker: `refdata___get_asset_mappings({ entityAssetCode: \"{ticker}\", mappingStatus: \"Active\", limit: 200 })` . Collect distinct `lukkaAssetId` values.\n2. **Validate + collapse**: `refdata___get_asset_by_id({ assetLid })`  per distinct LID -> drop `Inactive`/`Contract Migrated`, collapse chain-variants to the group `isPrimaryAsset: true` LID, dedupe to active groups.\n3. **Resolve or flag**: one active group -> winner. More than one -> emit `AMBIGUOUS` (see below); do **not** block the batch or auto-pick.\n4. **Price**: `pricing___get_latest_prices({ sourceId: 1000, pairCodes: \"{lukkaAssetCode}-USD\" })`  (sourceId 1000 = Lukka Prime EOD)\n\n## Output\n\n### Asset Resolution Results\n\n| White Paper Code | Lukka Code | Lukka ID | Active Mappings | Price (USD) | Confidence |\n|-----------------|------------|----------|-----------------|-------------|------------|\n| BTC | XBT | LA6EV2NKQ95 | 52 | $XX,XXX | HIGH |\n| (collided ticker) | (multiple) | - | - | - | AMBIGUOUS |\n\nNote: Lukka IDs always follow the format `LA` + 9 alphanumeric characters (e.g. `LA6EV2NKQ95`). Never display abbreviated or placeholder formats like `lid-xxx`.\n\n**Confidence levels**: HIGH (10+ active mappings), MEDIUM (3-9), LOW (1-2), UNRESOLVED (0), AMBIGUOUS (>1 active asset group shares the ticker)\n- If result count equals limit (200), display as \"200+ (truncated)\" and confidence as \"HIGH (truncated)\"\n- For `AMBIGUOUS` rows, follow the table with a short list of competing candidates (name, blockchain, group primary LID) so the user can re-run `asset-report workflow` on the right one. Never silently pick one.\n"
}