home / skills / aster110 / mycc / tell-me

tell-me skill

safe

This skill summarizes the current conversation and sends a Lark Feishu notification across platforms, keeping you informed and guiding next steps.

npx playbooks add skill aster110/mycc --skill tell-me

Review the files below or copy the command above to add this skill to your agents.

Files (3)

SKILL.md

1.2 KB

---
name: tell-me
description: 飞书通知（全平台）。总结当前对话要点并发送到飞书群。触发词："/tell-me"、"通知我"、"飞书通知"、"告诉我"
---

# Tell Me - 飞书通知（全平台版）

将当前对话的关键信息发送到飞书群。支持 macOS / Linux / Windows。

## 触发词

- "/tell-me"
- "通知我"
- "飞书通知"
- "告诉我"

## 执行步骤

1. **总结对话**（3-5 句话）
   - 做了什么
   - 结论/结果
   - 下一步（如有）

2. **发送飞书**

## 发送命令

```bash
node /Users/aster/AIproject/mylife/.claude/skills/tell-me/send.js "标题" "内容" [颜色]
```

**参数说明**：
- 标题：卡片标题
- 内容：支持 lark_md 格式，用 `\n` 换行，`**粗体**`、`*斜体*`
- 颜色（可选）：blue（默认）、green、orange、red

**示例**：
```bash
node /Users/aster/AIproject/mylife/.claude/skills/tell-me/send.js "任务完成" "• 完成了 xxx\n• 下一步 yyy" green
```

## 卡片颜色

根据内容性质选择：
- **green**：完成/成功
- **blue**：普通信息
- **orange**：提醒/警告
- **red**：紧急/错误

## 跨平台说明

使用 Node.js 原生 `fetch`（Node 18+），无需额外依赖，三平台通用。

Overview

This skill sends concise summaries of the current chat to a Feishu group across macOS, Linux, and Windows. It captures the key points, outcomes, and next steps, then posts them as a Feishu card with configurable title, content, and color. Use simple triggers to generate and deliver notifications quickly.

How this skill works

When invoked, the skill summarizes the active conversation in 3–5 sentences covering what was done, conclusions or results, and any next steps. It then calls a Node.js script that posts a lark_md-formatted card to a Feishu group using native fetch (Node 18+). You can set the card title, body content with markdown, and an optional color flag to indicate severity or status.

When to use it

Notify a team channel after a discussion or decision.
Record quick meeting outcomes and assigned next steps.
Alert stakeholders about a completed task or milestone.
Send reminders or warnings that need visibility.
Provide an executive summary for asynchronous updates.

Best practices

Keep the generated summary to 3–5 clear sentences: what, result, next step.
Use lark_md formatting for readable bullets and emphasis (\n for new lines, **bold** for highlights).
Choose card color deliberately: green for success, blue for info, orange for warnings, red for urgent issues.
Run with Node.js 18+ to use native fetch without extra dependencies.
Include concrete next steps and owners when possible to reduce follow-up questions.

Example use cases

Post a short summary to the product channel after a decision: title 'Feature decision', content with summary and next sprint tasks, color blue.
Notify ops on a fix deployment: title 'Deploy complete', list fixes and verification steps, color green.
Send a warning about a blocker to the team: title 'Blocker', description of impact and required actions, color orange.
Alert leadership about a critical incident: concise incident summary, current status, owners, color red.

FAQ

What triggers invoke the skill?

Use the trigger phrases like "/tell-me", "通知我", "飞书通知", or "告诉我" to generate the summary and send the card.

How do I customize the card content and color?

Call the provided Node.js script with arguments: title, content in lark_md format (use \n for line breaks), and an optional color (blue, green, orange, red). Example: node send.js "Title" "• item1\n• item2" green