Imported from Guoen0/xiaoduiyou-public (plugins/xiaoduiyou-runtime-skills/skills/xiaoduiyou-im/SKILL.md). Install upstream with npx skills add Guoen0/xiaoduiyou-public --skill xiaoduiyou-im. Copyright stays with the author.

Xiaoduiyou IM

This skill is the first stop for Xiaoduiyou Agent chat-box intent. It owns chat-only delivery and all cases that can be answered inside the conversation UI without creating a document or writing Growth Diary records.

Trigger

Load this when:

• Current session/source is Xiaoduiyou or the screen is Agent 对话页.
• The user asks for visual cards, product/source cards, clickable images, Xiaoduiyou message delivery, or chat result UI.
• Keywords handled here: 视觉卡片, 卡片, 点图, 点图片打开, 商品候选, 参考帖, 淘宝, 小红书, 找一下, 给我几个, 候选.
• If the user asks for 旅游规划, 旅行规划, itinerary/travel result UI, 内容包, 文档产物, 发布稿, ui_templates, or publish tabs, load xiaoduiyou-doc-content-package instead.
• If the user asks for 成长日记, baby diary records, or diary photos/schema/views, load xiaoduiyou-growth-diary instead.
• If the user asks to view or update child basic info or development progress such as baby name/nickname, birthday, gender, allergy, height, weight, child photo, four development dimensions, skill nodes, 点亮/熄灭, or 已掌握/未掌握, load xiaoduiyou-child-profile instead.
• If runtime/session context explicitly has session_purpose: feedback, or the current Hermes profile is the configured Xiaoduiyou public feedback handler, load xiaoduiyou-feedback-issues instead. Do not route ordinary chat just because the user says 反馈, bug, 问题, or issue.
• If the user asks for baby/toddler psychology, behavior, routines, feeding cooperation, sleep/meal cooperation, discipline, emotion coaching, attachment, autonomy, play, or family caregiving decisions without asking to write diary data, answer in chat here.

Non-negotiables

0. Xiaoduiyou operating knowledge belongs in Xiaoduiyou skills, not Hermes memory. Treat the agent as a Xiaoduiyou developer and earliest user: when a Xiaoduiyou workflow lesson, UI/runtime convention, or caregiver shorthand is discovered, patch the relevant xiaoduiyou-* skill so other agents can inherit it; do not store that experience only in profile memory.
1. If the current screen/source is Xiaoduiyou Agent 对话页 and the user asks to generate or return an image, load this skill before final delivery even if the creative prompt itself is handled by an image-generation skill. The deliverable must be a Xiaoduiyou IM image/card, not a generic Hermes Markdown image.
2. Prefer the xiaoduiyou_im_send tool for visual cards. It accepts OpenAI Responses-style content[] parts and the Xiaoduiyou backend uploads images/assets.
3. Visual cards in Xiaoduiyou render as image_attachments[], not MEDIA:/..., Markdown images, browser screenshots, or link-only text.
4. Local/server-static paths are invalid in final chat cards. Pass public browser-fetchable HTTPS images or data:image/...;base64,... to xiaoduiyou_im_send; never pass /tmp, /Users, file:, blob:, localhost, or private-network URLs.
5. Hard lesson from user correction: If the current source/screen is Xiaoduiyou and the deliverable is an image, do not put MEDIA:/local/path in the final answer. Convert the generated/local image to a deliverable Xiaoduiyou image first. Preferred workflow for generated/local files: QA the local output, remove/crop visible provider watermark if needed, upload the approved local file with xiaoduiyou_assets_upload, HEAD-verify the HTTPS URL returns 200 image/*, then call xiaoduiyou_im_send with an input_image part and verify attachment_count >= 1. Existing public HTTPS image URLs from search/product sources may be sent directly when they are fetchable without cookies, login, or temporary local state. Base64 data:image/<type>;base64,... is an acceptable fallback for small images.
6. Send the Xiaoduiyou IM payload inside the same active turn before the final text reply. Do not first finalize with a local/Markdown path and try to "补发" later; the runtime may close the turn and reject late IM sends.
7. Verify delivery: response event type, attachment count, and at least one image URL HTTP 200 image content-type.
8. If Xiaoduiyou IM delivery fails with a platform/runtime error (for example TURN_ALREADY_CLOSED, missing attachments despite correct xiaoduiyou_im_send, or frontend cannot display supported image payloads), do not keep silently retrying or blame the user. Briefly explain that this looks like a platform issue, encourage the user to keep using the product and to submit feedback when convenient, and provide a concise copy-pasteable bug report with environment/session, repro steps, actual/expected result, and exact error.
9. For product questions: Xiaohongshu provides lived-experience/reference evidence; Taobao/Tmall provides buyable candidates/parameters. 8a. Do not turn a historical preference clue into a repeated gift/product recommendation. Before recommending, separate explicit likes, inferred aesthetic signals, products/actions already used, and unknowns. Anything already done belongs on an exclusion list unless the user explicitly asks to repeat it. 8b. Never describe an imagined product archetype as though a matching SKU has been found. Search and verify the exact listing first. If the market only offers partial matches (for example, plated silver instead of solid 18K gold), say that plainly and recommend from verified candidates rather than inventing precise-sounding series names. 8c. For jewelry sizing, never convert from a vague remembered number or an unrelated size. Inspect the live SKU's available options and declared sizing standard, use inner diameter in millimetres as the cross-system reference, measure a ring from the intended finger, and account for wide/multi-band styles fitting tighter. If the page shows only unexplained size numbers, ask the seller to confirm the system and finished inner diameter. Detailed checklist: references/product-question-workflow.md.
10. For document/content-package artifacts, travel plans, publish tabs, or process docs, load xiaoduiyou-doc-content-package; do not keep that workflow inside IM.
11. For Growth Diary records, load xiaoduiyou-growth-diary; do not send diary-only data as generic chat cards unless the user asks for a chat preview.
12. Keep private family context out of skill files. In a local Hermes environment, treat ${HERMES_HOME:-$HOME/.hermes}/private/xiaoduiyou-family-care-preferences.md as the only durable private-family memory file: read it before using family-specific names, IDs, caregiver labels, Feishu IDs, childcare preferences, or care-history facts; create or update it when the user gives durable private context; and keep only reusable product behavior in this skill. The file lives outside skills/ and plugins/, so skill/plugin upgrades should not overwrite it.

Case map owned by IM

First-pass routing

Parenting Guidance In Chat

Use this section for Xiaoduiyou chat answers about baby/toddler development, parenting decisions, family caregiving patterns, routines, feeding/sleep cooperation, emotion, behavior, discipline, play, and early education when the user is not asking to write records.

• Before relying on family-specific facts such as child nickname, caregiver labels, developmental history, Feishu IDs, or household preferences, check ${HERMES_HOME:-$HOME/.hermes}/private/xiaoduiyou-family-care-preferences.md when running in local Hermes. If it is missing and the user provides durable private context, create it there instead of adding that data to this skill; if it exists and the user corrects a durable preference/fact, update that file rather than repeating private facts in chat-workflow instructions.
• Give modern, evidence-based, non-stereotyped advice. Do not rely on gender scripts such as "mother = naturally sensitive/caretaking" or "father = naturally strong/decision-maker." Infer only from observed behavior, stated context, and explicit uncertainty.
• Explain behavior through several lenses together: developmental stage, attachment, learning/routines, cognition, emotion coaching, environment design, caregiver consistency, and family-system fatigue or conflict.
• Structure substantial advice as: conclusion first, developmental task, what adults should do, what adults should avoid, home implementation, and uncertainty/red flags.
• Use concrete caregiver scripts: name the emotion, validate the wish, hold the boundary, and offer an acceptable alternative. Avoid shame, threats, ridicule, abandonment, inconsistent rules, or unsafe freedom.
• For advanced toddlers or order-sensitive-period signs, reason from actual age plus the near-next stage. If motor ability is ahead, raise the safety bar because reachable hazards increase before impulse control catches up.
• For pediatric symptom or medical-like threads, treat the conversation as a case note: restate timeline/facts, separate facts from inferences, rank likely causes/modifiers, and update the conclusion only when new information changes the evidence. Do not diagnose from photos alone. For current guideline or medication-dose claims, use authoritative live sources or tell the user the claim needs medical confirmation.
• If the user wants to log, correct, summarize, or query care events, switch to xiaoduiyou-growth-diary.

Preferred Tool

Call xiaoduiyou_im_send with OpenAI Responses-style content parts. In an active/recent Xiaoduiyou turn, omit session_id and let the connector inherit the current session_id/turn_id. For background/default Home delivery, pass channel: "default" explicitly. Pass session_id only when replying to a specific active session. If sending after an async delegation callback or a user reports the image landed in 主对话 instead of the current Agent thread, treat it as a routing-risk case: explicitly pass the current session_id and turn_id when available, then verify the returned context. If the tool still reports the right session but the frontend shows the attachment in Home/main chat, stop retrying blindly and report a Xiaoduiyou IM routing bug with session_id, returned mode/context, and expected thread.

For image-generation replies in Xiaoduiyou, the safe delivery sequence is: generate → inspect/QA local output → crop or regenerate if watermark/quality is unacceptable → upload the final local file with xiaoduiyou_assets_upload when a durable HTTPS URL is useful → verify 200 image/* → send the verified URL as an input_image card → only then final-text summarize. For already-public web images, send the original HTTPS URL directly if it is browser-fetchable and not login/cookie-bound. Never use MEDIA: or a local path as the Xiaoduiyou deliverable.

{
  "channel": "default",
  "content": [
    { "type": "input_text", "text": "点图片可以打开来源。" },
    {
      "type": "input_image",
      "image_url": "https://example.com/card.webp",
      "detail": "auto",
      "display": {
        "title": "龙柳鲜枝水培款",
        "subtitle": "淘宝 · 插瓶水培 · 1.2-1.5m 优先",
        "badge": "商品候选",
        "link_url": "https://s.taobao.com/search?q=..."
      }
    }
  ]
}

Use data:image/png;base64,... for generated images when you do not already have an HTTPS URL.

Scheduled Messages

When the user asks to send a Xiaoduiyou message later, create a cron job whose delivery target is in deliver. Do not write a future prompt that calls send_message, because cron runs do not expose the messaging toolset.

For fixed-text reminders, prefer a no-agent cron script so the scheduler delivers the exact text without a future LLM turn. Create a small script under ${HERMES_HOME:-$HOME/.hermes}/scripts/, then call cronjob(action="create", script="<name>", no_agent=true, deliver="xiaoduiyou:<channel>"). The script must print only the user-facing message. Do not print “已发送”, “done”, or delivery status; delivery success comes from the scheduler/platform response, not from the script text.

• Current/default Home channel: deliver: "xiaoduiyou:default" or deliver: "xiaoduiyou:主对话".
• Named sidebar channel: deliver: "xiaoduiyou:<visible channel title>", for example xiaoduiyou:达拉崩吧.
• If a job is LLM-driven, keep the cron prompt to the exact user-facing content, for example 请只回复：测试 cron：1 分钟到了。.
• After creating the job, inspect the returned job object and confirm deliver is the intended Xiaoduiyou target, not local.

Example:

{
  "action": "create",
  "schedule": "1m",
  "script": "xiaoduiyou-reminder-20260611-0209.sh",
  "no_agent": true,
  "deliver": "xiaoduiyou:达拉崩吧"
}

Script content:

#!/usr/bin/env bash
printf '%s\n' '测试 cron：1 分钟到了。'

Legacy Script

• scripts/send_visual_cards.py: fallback for old connectors without xiaoduiyou_im_send; sends structured content parts through /api/agent/im/send, defaulting to the Home default channel (主对话).

Quick use:

HERMES_SKILL_HOME="${HERMES_HOME:-$HOME/.hermes}"
python "$HERMES_SKILL_HOME/skills/xiaoduiyou/xiaoduiyou-im/scripts/send_visual_cards.py" --list-channels
python "$HERMES_SKILL_HOME/skills/xiaoduiyou/xiaoduiyou-im/scripts/send_visual_cards.py" \
  --channel default \
  --text '点图片可以打开来源。' \
  --cards-json /tmp/cards.json

Card JSON shape

[
  {
    "image_path": "/tmp/card.png",
    "title": "龙柳鲜枝水培款",
    "subtitle": "淘宝 · 插瓶水培 · 1.2–1.5m 优先",
    "badge": "商品候选",
    "link_url": "https://s.taobao.com/search?q=..."
  }
]