メニュー
Send the 减脂档案 mini-program card when the user asks for overall progress/data/trajectory: '减脂档案', '我的数据', '减脂曲线', '体重曲线', 'my progress'. NOT for '今天/今日' single-day queries → personal-data-query; NOT '周报/这周' → weekly-report.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | diet-profile-card |
| version | 1.0.0 |
| description | Send the 减脂档案 mini-program card when the user asks for overall progress/data/trajectory: '减脂档案', '我的数据', '减脂曲线', '体重曲线', 'my progress'. NOT for '今天/今日' single-day queries → personal-data-query; NOT '周报/这周' → weekly-report. |
| metadata | {"openclaw":{"emoji":"chart_with_upwards_trend"}} |
🚨 OUTPUT CONTRACT: 命中即发一张小程序卡片。卡片本身就是回复 —— 成功后回
NO_REPLY,不再补任何文字。发卡失败才回退到一条文字。
用户想看自己的"减脂档案/整体进展/数据/曲线"时,发一张减脂档案小程序卡片(固定底图 +「{Name}的减脂档案」标题,点击进小程序 dashboard)。这是档案级/整体视角,区别于当日查询(personal-data-query)和周级汇总(weekly-report)。
命中(发档案卡):
不归本 skill(交给别人):
personal-data-queryweekly-reportdiet-tracking-analysis / weight-tracking拿不准是"当日"还是"整体"时:提到"档案/曲线/趋势/进展/一直/最近这段"偏整体 → 本 skill;明确"今天/现在" → personal-data-query。
发卡时可附带一句贴合当下对话的短文案,连着卡一起发。不传文案则只发卡片、不发文字(无任何兜底文案)——自然语言场景建议显式传一句,让回复更自然。
文案要求:1-2 句,口语、轻松,承接用户刚才的话,引导点开卡片看档案。用 USER.md > Name 称呼。示例:
语言按 USER.md > Language(zh/en),不要自行推断。
bash {baseDir}/scripts/send-profile-card.sh "{workspaceDir}" "{Step2 的短文案}"
workspaceDir 目录名读取 account_id,再转调业务统一入口 shared/card/build-and-send-card.sh(反查 robotId、取密钥、生成封面 SVG),底层由 backend send-miniprogram-card.mjs 渲染发送ok = 成功 → 本轮结束,回复 NO_REPLY,不再发任何文字回退文案(仅发卡失败时): 简短告知,不承诺链接(档案卡无独立 H5 URL,失败就纯文字安抚):
{Name}~ 你的减脂档案我这就整理,稍等我一下 🙌
Trigger on emotional signals, negative AND positive: body-image distress, guilt about eating, hopelessness, self-criticism — or pride, milestones, excitement about progress. Takes priority over ALL logging, data collection, and reminders — when a message carries both data (food/weight/exercise) and emotion, emotional presence comes FIRST; log later or briefly after.
Reference companion for expert interventions. Trigger when the prompt carries a 'Pending Expert Intervention (auto-injected)' section — the injected file is the runtime authority; read this skill when you need the full workflow background (intervention kinds, negotiation state machine, logging, file lifecycle).
Creates calorie-controlled diet templates and weekly meal plans from the user's calorie target and preferences (multiple diet modes). Trigger on: meal/diet plan requests, 'what should I eat to lose weight', '帮我做个饮食计划', meal prep and portion-control help, recipe suggestions tied to weight loss. Requires a calorie target (from PLAN.md or user-stated). On-the-spot restaurant/dining decisions → restaurant-meal-finder.
Per-trigger execution logic for daily reminders. Runs pre-send checks, composes meal/weight reminder messages, and manages recall messages. Use this skill when: a cron job fires and needs to decide whether/what to send. Do NOT use for cron management, lifecycle transitions, or reminder settings — that is notification-manager's job.
Cron infrastructure and reminder lifecycle (Active → Recall → Weekly/Monthly → Silent). Use when: onboarding completes (bootstrap meal/weight reminder crons), reminder timing/settings change, or another skill needs cron state verified/fixed. Leave/vacation requests → leave-manager. Composing reminder content → notification-composer. User-requested reminder CRUD → reminder-manager.
Returns meal-logging streak data (current_streak, pending_milestone) — called BY other skills (notification-composer at Stage-1 meal reminders; weekly-report), never a standalone conversation skill. Only user-triggered case: explicit streak questions ('我连续打卡几天了', 'what's my streak'). Never proactively mention streaks; silence after a break.