skills v3

.idea/SKILL.md

@@ -106,6 +106,78 @@ For OpenClaw, inspect `raw` for domain-specific fields:
 - Placeables: production types, power/water fields, craftable recipe relationships.
 - NPCs: `raw.description`, `raw.npcTags`, category metadata.
 
+## Discord Markdown Output Contract
+
+Rich Discord embeds are not available yet. When OpenClaw asks for Discord output, return a plain Discord message string formatted with Discord-supported Markdown only. Do not return embed JSON.
+
+Use supported Markdown:
+
+- Headings with `#`, `##`, or `###` for short section titles.
+- Bold with asterisks, for example `**Assassin's Rifle**`. Do not use underscores for bold.
+- Italic sparingly for secondary text.
+- Unordered lists with `-` for fields and search results.
+- Ordered lists for ranked results.
+- Inline code for ids, dataset names, stat keys, and short values.
+- Fenced code blocks for compact JSON or command examples.
+- Links with `[label](url)` when a clean label helps.
+- Blockquotes with `>` or `>>>` for quoted descriptions.
+- Strikethrough only when it adds useful meaning.
+
+Avoid unsupported or unreliable formatting:
+
+- No Markdown tables.
+- No HTML.
+- No horizontal rules.
+- No task lists.
+- No footnotes, heading ids, definition lists, subscript, superscript, or highlight syntax.
+- No images in Markdown.
+- Do not rely on Markdown paragraph syntax or special line-break syntax; use normal newline-separated lines.
+
+Default Discord result format:
+
+```text
+## Assassin's Rifle
+**Type:** `item`
+**Language:** `en`
+**Source ID:** `LongRifle_Unique_Poison_03`
+**Category:** `weapon` / `rifle`
+
+**Stats**
+- Damage: `128.25`
+- Accuracy: `1.2`
+- Clip Size: `2`
+
+[Open in Dune API](https://dune.api.coppnic.cc/api/item/LongRifle_Unique_Poison_03?language=en)
+```
+
+Search result format:
+
+```text
+## Search Results: poison
+1. **Poison Mine** (`skill`) - `skills_ability_poisonmine`
+2. **Assassin's Rifle** (`item`) - `LongRifle_Unique_Poison_03`
+
+Use `/api/{dataset}/{id}?language=en` for details.
+```
+
+Discord response rules:
+
+- Keep responses concise enough for Discord message limits.
+- Show at most 10 compact search results unless the user asks for more.
+- For detailed records, prefer the most useful 5 to 8 fields.
+- Do not dump the full `raw` object.
+- Omit empty, null, unknown, or noisy fields.
+- Include a Dune API link for single-record answers.
+- Prefer singular datasets: `item`, `skill`, `recipe`, `placeable`, `npc`.
+
+Dataset field ideas:
+
+- `item`: grade, category, subcategory, weapon stats, armor stats, fillable stats.
+- `skill`: category, subcategory, max skill level, level bonuses.
+- `recipe`: output items, input items, crafting time, required stations.
+- `placeable`: category, power, water, supported production types.
+- `npc`: category, tags, description.
+
 ## Repository Map
 
 Look here when changing behavior:

SKILL.md

@@ -40,6 +40,78 @@ items, skills, recipes, placeables, npcs
 
 Use singular datasets for complete stats and relationships. Use plural datasets only when a compact Questlog page-summary record is enough.
 
+## Discord Markdown Output Contract
+
+Rich Discord embeds are not available yet. When OpenClaw asks for Discord output, return a plain Discord message string formatted with Discord-supported Markdown only. Do not return embed JSON.
+
+Use supported Markdown:
+
+- Headings with `#`, `##`, or `###` for short section titles.
+- Bold with asterisks, for example `**Assassin's Rifle**`. Do not use underscores for bold.
+- Italic sparingly for secondary text.
+- Unordered lists with `-` for fields and search results.
+- Ordered lists for ranked results.
+- Inline code for ids, dataset names, stat keys, and short values.
+- Fenced code blocks for compact JSON or command examples.
+- Links with `[label](url)` when a clean label helps.
+- Blockquotes with `>` or `>>>` for quoted descriptions.
+- Strikethrough only when it adds useful meaning.
+
+Avoid unsupported or unreliable formatting:
+
+- No Markdown tables.
+- No HTML.
+- No horizontal rules.
+- No task lists.
+- No footnotes, heading ids, definition lists, subscript, superscript, or highlight syntax.
+- No images in Markdown.
+- Do not rely on Markdown paragraph syntax or special line-break syntax; use normal newline-separated lines.
+
+Default Discord result format:
+
+```text
+## Assassin's Rifle
+**Type:** `item`
+**Language:** `en`
+**Source ID:** `LongRifle_Unique_Poison_03`
+**Category:** `weapon` / `rifle`
+
+**Stats**
+- Damage: `128.25`
+- Accuracy: `1.2`
+- Clip Size: `2`
+
+[Open in Dune API](https://dune.api.coppnic.cc/api/item/LongRifle_Unique_Poison_03?language=en)
+```
+
+Search result format:
+
+```text
+## Search Results: poison
+1. **Poison Mine** (`skill`) - `skills_ability_poisonmine`
+2. **Assassin's Rifle** (`item`) - `LongRifle_Unique_Poison_03`
+
+Use `/api/{dataset}/{id}?language=en` for details.
+```
+
+Discord response rules:
+
+- Keep responses concise enough for Discord message limits.
+- Show at most 10 compact search results unless the user asks for more.
+- For detailed records, prefer the most useful 5 to 8 fields.
+- Do not dump the full `raw` object.
+- Omit empty, null, unknown, or noisy fields.
+- Include a Dune API link for single-record answers.
+- Prefer singular datasets: `item`, `skill`, `recipe`, `placeable`, `npc`.
+
+Dataset field ideas:
+
+- `item`: grade, category, subcategory, weapon stats, armor stats, fillable stats.
+- `skill`: category, subcategory, max skill level, level bonuses.
+- `recipe`: output items, input items, crafting time, required stations.
+- `placeable`: category, power, water, supported production types.
+- `npc`: category, tags, description.
+
 Repository guide:
 
 ```text

public/SKILL.md

@@ -106,6 +106,78 @@ For OpenClaw, inspect `raw` for domain-specific fields:
 - Placeables: production types, power/water fields, craftable recipe relationships.
 - NPCs: `raw.description`, `raw.npcTags`, category metadata.
 
+## Discord Markdown Output Contract
+
+Rich Discord embeds are not available yet. When OpenClaw asks for Discord output, return a plain Discord message string formatted with Discord-supported Markdown only. Do not return embed JSON.
+
+Use supported Markdown:
+
+- Headings with `#`, `##`, or `###` for short section titles.
+- Bold with asterisks, for example `**Assassin's Rifle**`. Do not use underscores for bold.
+- Italic sparingly for secondary text.
+- Unordered lists with `-` for fields and search results.
+- Ordered lists for ranked results.
+- Inline code for ids, dataset names, stat keys, and short values.
+- Fenced code blocks for compact JSON or command examples.
+- Links with `[label](url)` when a clean label helps.
+- Blockquotes with `>` or `>>>` for quoted descriptions.
+- Strikethrough only when it adds useful meaning.
+
+Avoid unsupported or unreliable formatting:
+
+- No Markdown tables.
+- No HTML.
+- No horizontal rules.
+- No task lists.
+- No footnotes, heading ids, definition lists, subscript, superscript, or highlight syntax.
+- No images in Markdown.
+- Do not rely on Markdown paragraph syntax or special line-break syntax; use normal newline-separated lines.
+
+Default Discord result format:
+
+```text
+## Assassin's Rifle
+**Type:** `item`
+**Language:** `en`
+**Source ID:** `LongRifle_Unique_Poison_03`
+**Category:** `weapon` / `rifle`
+
+**Stats**
+- Damage: `128.25`
+- Accuracy: `1.2`
+- Clip Size: `2`
+
+[Open in Dune API](https://dune.api.coppnic.cc/api/item/LongRifle_Unique_Poison_03?language=en)
+```
+
+Search result format:
+
+```text
+## Search Results: poison
+1. **Poison Mine** (`skill`) - `skills_ability_poisonmine`
+2. **Assassin's Rifle** (`item`) - `LongRifle_Unique_Poison_03`
+
+Use `/api/{dataset}/{id}?language=en` for details.
+```
+
+Discord response rules:
+
+- Keep responses concise enough for Discord message limits.
+- Show at most 10 compact search results unless the user asks for more.
+- For detailed records, prefer the most useful 5 to 8 fields.
+- Do not dump the full `raw` object.
+- Omit empty, null, unknown, or noisy fields.
+- Include a Dune API link for single-record answers.
+- Prefer singular datasets: `item`, `skill`, `recipe`, `placeable`, `npc`.
+
+Dataset field ideas:
+
+- `item`: grade, category, subcategory, weapon stats, armor stats, fillable stats.
+- `skill`: category, subcategory, max skill level, level bonuses.
+- `recipe`: output items, input items, crafting time, required stations.
+- `placeable`: category, power, water, supported production types.
+- `npc`: category, tags, description.
+
 ## Repository Map
 
 Look here when changing behavior:

src/SKILL.md

@@ -106,6 +106,78 @@ For OpenClaw, inspect `raw` for domain-specific fields:
 - Placeables: production types, power/water fields, craftable recipe relationships.
 - NPCs: `raw.description`, `raw.npcTags`, category metadata.
 
+## Discord Markdown Output Contract
+
+Rich Discord embeds are not available yet. When OpenClaw asks for Discord output, return a plain Discord message string formatted with Discord-supported Markdown only. Do not return embed JSON.
+
+Use supported Markdown:
+
+- Headings with `#`, `##`, or `###` for short section titles.
+- Bold with asterisks, for example `**Assassin's Rifle**`. Do not use underscores for bold.
+- Italic sparingly for secondary text.
+- Unordered lists with `-` for fields and search results.
+- Ordered lists for ranked results.
+- Inline code for ids, dataset names, stat keys, and short values.
+- Fenced code blocks for compact JSON or command examples.
+- Links with `[label](url)` when a clean label helps.
+- Blockquotes with `>` or `>>>` for quoted descriptions.
+- Strikethrough only when it adds useful meaning.
+
+Avoid unsupported or unreliable formatting:
+
+- No Markdown tables.
+- No HTML.
+- No horizontal rules.
+- No task lists.
+- No footnotes, heading ids, definition lists, subscript, superscript, or highlight syntax.
+- No images in Markdown.
+- Do not rely on Markdown paragraph syntax or special line-break syntax; use normal newline-separated lines.
+
+Default Discord result format:
+
+```text
+## Assassin's Rifle
+**Type:** `item`
+**Language:** `en`
+**Source ID:** `LongRifle_Unique_Poison_03`
+**Category:** `weapon` / `rifle`
+
+**Stats**
+- Damage: `128.25`
+- Accuracy: `1.2`
+- Clip Size: `2`
+
+[Open in Dune API](https://dune.api.coppnic.cc/api/item/LongRifle_Unique_Poison_03?language=en)
+```
+
+Search result format:
+
+```text
+## Search Results: poison
+1. **Poison Mine** (`skill`) - `skills_ability_poisonmine`
+2. **Assassin's Rifle** (`item`) - `LongRifle_Unique_Poison_03`
+
+Use `/api/{dataset}/{id}?language=en` for details.
+```
+
+Discord response rules:
+
+- Keep responses concise enough for Discord message limits.
+- Show at most 10 compact search results unless the user asks for more.
+- For detailed records, prefer the most useful 5 to 8 fields.
+- Do not dump the full `raw` object.
+- Omit empty, null, unknown, or noisy fields.
+- Include a Dune API link for single-record answers.
+- Prefer singular datasets: `item`, `skill`, `recipe`, `placeable`, `npc`.
+
+Dataset field ideas:
+
+- `item`: grade, category, subcategory, weapon stats, armor stats, fillable stats.
+- `skill`: category, subcategory, max skill level, level bonuses.
+- `recipe`: output items, input items, crafting time, required stations.
+- `placeable`: category, power, water, supported production types.
+- `npc`: category, tags, description.
+
 ## Repository Map
 
 Look here when changing behavior: