You (the agent) run the WHOLE flow yourself with your tools, then POST the result to the current Lark chat. Do NOT refuse, do NOT just describe. If a data source or sink is unavailable, SKIP it and still post what you have.
Tech Digest Aggregator
Use this when someone asks for an AI / tech news digest, RSS roundup, GitHub trend digest, Hacker News tech digest, or "AI资讯小报 / AI干货小报 / 推特价值小报".
How to run it
COLLECT via tools, using ONLY bound connectors:
- GitHub →
nyxid_proxy slug api-github (bound ✓).
- Public web / RSS / Hacker News, and any other public endpoint →
web_fetch (no credential, ✓).
- ⚠
api-reddit and api-twitter are NOT bound for this bot. Do NOT depend on them. Use web_fetch on public endpoints instead where possible; otherwise SKIP that source and note (<source> skipped — connector not bound) in the message. NEVER fail the run because one source is unavailable.
- Normalize collected rows into
rssItems / tweetItems-compatible objects with 标题, 内容, 日期, 链接, 来源, 板块, 分类, and optional 分类理由.
ANALYZE with your own model. Summarize, score, classify, dedupe, rank, and choose any Top10 items yourself. Keep categories compatible with the builder contract where practical: 产品发布/更新, 博客/研究/评论/深度报道, or 其他(融资/社会舆论/人事变动等).
BUILD the message body by running scripts/build_tech_digest_payload.js via code_execute with language "javascript". code_execute has NO stdin, so inline your collected/analyzed data into the code: paste the whole script, then append a call to its exported buildPayload and print the result. The script exports module.exports = { buildPayload }, so end the code with:
// ...full contents of scripts/build_tech_digest_payload.js above...
console.log(JSON.stringify(buildPayload({
mode: "build_messages",
date: "<YYYY-MM-DD>",
rssItems: [/* normalized rows */],
tweetItems: [],
top10: []
})));
Use the returned messages[*].markdown, messages[*].card, or lark.sendMessages[*].content as the digest body. If you cannot run code or the script needs clarification, fall back to references/tech-digest-contract.md field-for-field.
POST it to the CURRENT chat via lark_messages_send, lark_messages_reply, or reply_with_interaction. THIS STEP ALWAYS HAPPENS — it is the demo output. If the builder returns multiple digest messages, post the useful digest set in order or combine their Markdown into one current-chat summary. If no source produced items, post a short "no items found" digest plus any skipped-source notes.
OPTIONAL: writing a Lark Bitable record is best-effort ONLY. Do it only if a target base app_token plus table id is actually provided; if not, SKIP and still post the chat message. Never block on a missing Bitable.
Payload builder reference
Run scripts/build_tech_digest_payload.js with mode: "build_messages" for chat output, or mode: "build_all" when a real Bitable target is also available. Inputs may be at the root or under body; aliases and exact output shapes are in references/tech-digest-contract.md.
The script can emit needs_more_information, skip, messages, records, and Lark-shaped request payloads. For the active playbook, the final visible result is always a Lark chat post, using the best digest body available from the script output or contract fallback.
Guardrails
- Never invent fetched articles, GitHub records, public endpoint results, or connector credentials.
- Never wait for
api-reddit, api-twitter, or Bitable availability before posting the chat digest.
- Prefer the bundled builder for final message structure; use your model for collection cleanup, summarization, scoring, and ranking.
1---2name: tech-digest-aggregator-payload-builder3version: "2.2"4description: Runs the tech-digest aggregator flow end to end and posts a digest to the chat.5metadata:6 source: https://skillmd.com/skills/chronoaiproject/tech-digest-aggregator-payload-builder7 category: plain8 tag:9 - aevatar10 - s-capability11 - tech-digest12 - lark13 - payload-builder14 clawdbot:15 emoji: "newspaper"16 files:17 - "references/*"18 - "scripts/*"19---2021You (the agent) run the WHOLE flow yourself with your tools, then POST the result to the current Lark chat. Do NOT refuse, do NOT just describe. If a data source or sink is unavailable, SKIP it and still post what you have.2223# Tech Digest Aggregator2425Use this when someone asks for an AI / tech news digest, RSS roundup, GitHub trend digest, Hacker News tech digest, or "AI资讯小报 / AI干货小报 / 推特价值小报".2627## How to run it28291. **COLLECT via tools, using ONLY bound connectors:**30 - GitHub → `nyxid_proxy` slug `api-github` (bound ✓).31 - Public web / RSS / Hacker News, and any other public endpoint → `web_fetch` (no credential, ✓).32 - ⚠ `api-reddit` and `api-twitter` are NOT bound for this bot. Do NOT depend on them. Use `web_fetch` on public endpoints instead where possible; otherwise SKIP that source and note `(<source> skipped — connector not bound)` in the message. NEVER fail the run because one source is unavailable.33 - Normalize collected rows into `rssItems` / `tweetItems`-compatible objects with `标题`, `内容`, `日期`, `链接`, `来源`, `板块`, `分类`, and optional `分类理由`.34352. **ANALYZE with your own model.** Summarize, score, classify, dedupe, rank, and choose any Top10 items yourself. Keep categories compatible with the builder contract where practical: `产品发布/更新`, `博客/研究/评论/深度报道`, or `其他(融资/社会舆论/人事变动等)`.36373. **BUILD the message body** by running `scripts/build_tech_digest_payload.js` via `code_execute` with language `"javascript"`. `code_execute` has NO stdin, so inline your collected/analyzed data into the code: paste the whole script, then append a call to its exported `buildPayload` and print the result. The script exports `module.exports = { buildPayload }`, so end the code with:38 ```javascript39 // ...full contents of scripts/build_tech_digest_payload.js above...40 console.log(JSON.stringify(buildPayload({41 mode: "build_messages",42 date: "<YYYY-MM-DD>",43 rssItems: [/* normalized rows */],44 tweetItems: [],45 top10: []46 })));47 ```48 Use the returned `messages[*].markdown`, `messages[*].card`, or `lark.sendMessages[*].content` as the digest body. If you cannot run code or the script needs clarification, fall back to `references/tech-digest-contract.md` field-for-field.49504. **POST it to the CURRENT chat** via `lark_messages_send`, `lark_messages_reply`, or `reply_with_interaction`. THIS STEP ALWAYS HAPPENS — it is the demo output. If the builder returns multiple digest messages, post the useful digest set in order or combine their Markdown into one current-chat summary. If no source produced items, post a short "no items found" digest plus any skipped-source notes.51525. **OPTIONAL:** writing a Lark Bitable record is best-effort ONLY. Do it only if a target base `app_token` plus table id is actually provided; if not, SKIP and still post the chat message. Never block on a missing Bitable.5354## Payload builder reference5556Run `scripts/build_tech_digest_payload.js` with `mode: "build_messages"` for chat output, or `mode: "build_all"` when a real Bitable target is also available. Inputs may be at the root or under `body`; aliases and exact output shapes are in `references/tech-digest-contract.md`.5758The script can emit `needs_more_information`, `skip`, `messages`, `records`, and Lark-shaped request payloads. For the active playbook, the final visible result is always a Lark chat post, using the best digest body available from the script output or contract fallback.5960## Guardrails6162- Never invent fetched articles, GitHub records, public endpoint results, or connector credentials.63- Never wait for `api-reddit`, `api-twitter`, or Bitable availability before posting the chat digest.64- Prefer the bundled builder for final message structure; use your model for collection cleanup, summarization, scoring, and ranking.