newsletter-from-shipping

Drafts weekly newsletter teardowns from meetings, email, code, docs, tickets, and sessions.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/aspectrr/newsletter-from-shipping --skill newsletter-from-shipping-aspectrr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: newsletter-from-shipping
Source: https://github.com/aspectrr/newsletter-from-shipping/tree/main/skills/newsletter-from-shipping
Command: npx skills add https://github.com/aspectrr/newsletter-from-shipping --skill newsletter-from-shipping-aspectrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a consistent weekly newsletter requires manually reviewing a week of scattered work across meetings, email, GitHub, docs, tickets, and chat sessions, then synthesizing it into a story. This Skill automates that gathering and drafting loop, producing a voice-calibrated newsletter teardown ready for human editing. ## Core Features & Use Cases - Multi-source gathering: Pulls the last 7 days of activity from six sources (meetings CLI, Gmail, GitHub commits across orgs, Google Docs, Linear tickets, pi session JSONL, Slack) in parallel, degrading gracefully when a source is unavailable. - Story filtering and abstraction: Selects the single best teardown candidate using generalizability and business-outcome tests, skipping the week rather than forcing filler content. - Voice-calibrated drafting: Reads accumulated voice lessons from the madcactus MCP server before writing, drafts the six-beat teardown format (tension, what we did, verification, outcome, blueprint, numbers), and lints against voice rules. - Edit-driven learning: After the user edits in the dashboard, reads the draft-to-final diff to derive new voice lessons, and drafts three LinkedIn posts per issue plus a runnable lead-magnet repo folder. - Use Case: A founder asks the agent to draft this week's newsletter; the agent gathers activity from all sources, picks the data-loss-audit story, drafts Issue 02 in the teardown format, pushes it to the dashboard, and the founder edits and schedules it. ## Quick Start Ask the agent to draft this week's newsletter issue from the last seven days of work across all connected sources.

Frequently Asked Questions about newsletter-from-shipping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a weekly newsletter from my work activity?

Run the skill's draft workflow: it gathers the last 7 days from meetings, email, GitHub, docs, tickets, and sessions in parallel, picks the one story worth a teardown, and drafts it into the madcactus dashboard. You then edit and schedule it there.

What data sources does the newsletter gathering support?

It pulls from six sources: meetings via the meetings CLI, email via madcactus_list_emails, code via the gh CLI across GitHub orgs, Google Docs, Linear tickets via orca, and pi session JSONL files, plus optional Slack. Missing sources are skipped gracefully without blocking the run.

Does the agent publish or send the newsletter automatically?

No. The agent only creates drafts in the madcactus dashboard. The user previews both email and web channels, edits, and hits Publish now or Schedule; the agent never touches Resend or sends anything itself.

What happens if no story qualifies for a newsletter issue that week?

The skill applies generalizability and outcome tests to candidate stories. If nothing meets the criteria, it tells the user what it found and skips the week rather than forcing filler content.

How does the newsletter draft improve over time?

After the user edits a draft, the agent reads the version diff from the dashboard and derives voice lessons, which are stored and paired with lint patterns. Future drafts load these lessons before writing, so edits compound into sharper drafts.