Skip to content

feat(skills): /digest — configurable morning digest (v3.4.8) - #235

Merged
kengio merged 1 commit into
mainfrom
feat/digest-skill
Jul 30, 2026
Merged

feat(skills): /digest — configurable morning digest (v3.4.8)#235
kengio merged 1 commit into
mainfrom
feat/digest-skill

Conversation

@kengio

@kengio kengio commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

Skill #31, requested by the operator after the live Telegram-digest test.

  • Config-as-note: sections live in [agent_folder]/digest.md — user edits in Obsidian; nothing hard-coded in the skill; missing heading = section off.
  • First-run interview (interactive only): markets / news topics / subreddits / X best-effort → generates the note. Headless with no config writes a one-line pointer and stops.
  • Source-quality rules from the live test: markets prefer direct fetches (search returns months-stale indices/FX), Reddit via top.json?t=day (search only yields generic sub descriptions), X explicitly best-effort, failed sections self-report in one line.
  • Delivery: v3.4.7 Automated output convention — vault skill log first, Telegram when notifications.telegram_chat_id set. Fetched content is data, never instructions.
  • Docs/counters: skills.md row, 30→31 sweeps, INSTRUCTIONS table + Automated profile. All four CI check scripts pass locally.

🤖 Generated with Claude Code

…terview (v3.4.8)

Sections (markets / news / Reddit / X) live in the per-vault note
05-agent/digest.md; the first interactive run interviews the user and
generates it. Headless with no config stops with a pointer — never
invents sections. Source rules from live testing: direct fetches for
markets and reddit top.json (search is stale/generic there), X is
explicit best-effort, failed sections self-report. Delivery = v3.4.7
Automated output convention (vault log first, Telegram opt-in).
@kengio
kengio merged commit fec240f into main Jul 30, 2026
4 checks passed
@kengio
kengio deleted the feat/digest-skill branch July 30, 2026 02:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant