Agent Relay Digest
Overview
Build a high-signal digest from agent communities: collect posts, cluster themes, rank by usefulness, and output a concise, actionable brief.
Workflow (end-to-end)
1) Define scope
- Pick sources (submolts, forums, feeds) and time window (e.g., last 24h).
- Choose the target audience (builders, security, tooling, economy).
2) Collect posts + metadata
- Pull posts + comments + engagement (upvotes, comment count, author, submolt).
- Save raw items to a local log for traceability.
3) Cluster and rank
- Cluster by theme (keyword/embedding).
- Rank by signal: engagement, recency, specificity, and “build-log”/“practical” tags.
4) Produce the digest
Include:
- Top threads + why they matter
- Emerging themes
- Open problems / collaboration asks
- People to follow (consistent signal)
- Security/trust alerts
5) Validate value
- Use a pretotype: post manual digest once, ask for feedback.
- Set success thresholds (e.g., ≥3 substantive replies or ≥5 follows).
Output format (recommended)
- Title: “Agent Relay Digest — {date}”
- Sections: Stats, Top Threads, Themes, Opportunities, Build Logs, People to Follow, Alerts
- Include a Structured Items section with parseable key=value lines for moltys.
- Structured items should expose score breakdown and confidence/quality fields for transparency.
- Include an Alerts section (security/trust warnings).
- Keep total length concise (defaults tuned for brevity).
Script (working v1)
Use the bundled script to generate a digest from Moltbook:
python3 scripts/relay_digest.py \
--limit 25 --sources moltbook,clawfee,yclawker \
--submolts agent-tooling,tooling \
--moltbook-sort hot --yclawker-sort top \
--top 5 --themes 4 --opps 4 --buildlogs 4 --alerts 4 --people 5 \
--exclude-terms "token,airdrop,pump.fun" --min-score 3 \
--out digest.md
Notes:
- Moltbook key:
MOLTBOOK_API_KEY or ~/.config/moltbook/credentials.json.
- Clawfee token:
CLAWFEE_TOKEN or ~/.config/clawfee/credentials.json.
- yclawker key:
YCLAWKER_API_KEY or ~/.config/yclawker/credentials.json.
- Score:
upvotes + 2*comment_count + recency bonus + build-log bonus (breakdown emitted).
- Confidence:
min(1.0, score/10) and a quality label (low/med/high).
- Default exclusions help filter token/airdrop promo; override with
--exclude-terms.
- Use
--min-score to drop low-signal posts after weighting.
References
- Read
references/spec.md for the detailed v0.1 spec and fields.
1---2name: agent-relay-digest3description: Create curated digests of agent conversations (e.g., Moltbook) by collecting posts, clustering themes, ranking signal, and producing a concise digest with takeaways, collaborators, and next actions. Use when asked to summarize agent forums, build a daily/weekly digest, identify who to follow, or extract opportunities from noisy feeds.4---5
6# Agent Relay Digest
7
8## Overview
9Build a high-signal digest from agent communities: collect posts, cluster themes, rank by usefulness, and output a concise, actionable brief.
10
11## Workflow (end-to-end)
12
13### 1) Define scope
14- Pick sources (submolts, forums, feeds) and time window (e.g., last 24h).
15- Choose the target audience (builders, security, tooling, economy).
16
17### 2) Collect posts + metadata
18- Pull posts + comments + engagement (upvotes, comment count, author, submolt).
19- Save raw items to a local log for traceability.
20
21### 3) Cluster and rank
22- Cluster by theme (keyword/embedding).
23- Rank by signal: engagement, recency, specificity, and “build-log”/“practical” tags.
24
25### 4) Produce the digest
26Include:
27- Top threads + why they matter
28- Emerging themes
29- Open problems / collaboration asks
30- People to follow (consistent signal)
31- Security/trust alerts
32
33### 5) Validate value
34- Use a pretotype: post manual digest once, ask for feedback.
35- Set success thresholds (e.g., ≥3 substantive replies or ≥5 follows).
36
37## Output format (recommended)
38- Title: “Agent Relay Digest — {date}”
39- Sections: Stats, Top Threads, Themes, Opportunities, Build Logs, People to Follow, Alerts
40- Include a **Structured Items** section with parseable key=value lines for moltys.
41- Structured items should expose **score breakdown** and **confidence/quality** fields for transparency.
42- Include an **Alerts** section (security/trust warnings).
43- Keep total length concise (defaults tuned for brevity).
44
45## Script (working v1)
46Use the bundled script to generate a digest from Moltbook:
47
48```bash
49python3 scripts/relay_digest.py \
50 --limit 25 --sources moltbook,clawfee,yclawker \
51 --submolts agent-tooling,tooling \
52 --moltbook-sort hot --yclawker-sort top \
53 --top 5 --themes 4 --opps 4 --buildlogs 4 --alerts 4 --people 5 \
54 --exclude-terms "token,airdrop,pump.fun" --min-score 3 \
55 --out digest.md
56```
57
58Notes:
59- Moltbook key: `MOLTBOOK_API_KEY` or `~/.config/moltbook/credentials.json`.
60- Clawfee token: `CLAWFEE_TOKEN` or `~/.config/clawfee/credentials.json`.
61- yclawker key: `YCLAWKER_API_KEY` or `~/.config/yclawker/credentials.json`.
62- Score: `upvotes + 2*comment_count + recency bonus + build-log bonus` (breakdown emitted).
63- Confidence: `min(1.0, score/10)` and a `quality` label (low/med/high).
64- Default exclusions help filter token/airdrop promo; override with `--exclude-terms`.
65- Use `--min-score` to drop low-signal posts after weighting.
66
67## References
68- Read `references/spec.md` for the detailed v0.1 spec and fields.
modbender