Draft a week of newsletter Notes from analytics and a personal voice profile
At a glance
The author describes a Claude Code workflow that reads seven days of Substack performance, proposes topics, drafts Notes from voice files, and exports a scheduling CSV for review. This workflow is listed under life, newsletter-production, content-planning.
Show HN: Statewright's Rust engine enforces plan/implement/test states for Claude Code (and other CLIs) via MCP hooks—wrong tools are blocked structurally, shrinking death spirals for both small and frontier models.
An on-demand research agent finds recent industry articles, organizes sections on trends, event strategy, and ticketing technology, and appends source links to an archive.
Adam keeps HA automations in git; Claude Code uses an MCP server to search entities, read traces, edit YAML, scp to the hub, reload, and commit—fixing a noisy camera automation in under two minutes.
Show HN (Oct 17): RugSnare pins each MCP tool's {name, description, inputSchema} by canonicalized SHA-256 at install, then diffs upgrades across 24 popular servers (~3.6M weekly installs)—336 contract changes found; grades BREAKING/LOOSENED/EXPANDED/NOTATION/COSMETIC and exits 1 for CI. Apache-2.0, zero npm deps; OWASP MCP Security Cheat Sheet now recommends contract pinning.