Newsletter
16 business operations skills for Claude Code, Cursor, Codex and AI agents. Finance, sales, strategy, customer success, product, procurement plus 13 task profiles. Built by Veltrix Collective.
npx -y skills add LukeJMadden/Veltrix-skills --skill newsletterAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Newsletter pipeline skill — drafting, quality assurance, approval flow, scheduling. Use when creating, reviewing, or managing email newsletters.
SKILL.md
1.8 KB, as published. Nobody here has run it
Manage the full newsletter lifecycle from draft to send.
Draft Pipeline
- Source — Pull top content from the week (news, blog posts, tool updates)
- Curate — Select 3-5 stories, ranked by relevance to audience
- Write — TLDR format: headline → 2-sentence summary → "why it matters"
- Weekly Kit — Include a recurring section (stat of the week, editor's pick, featured prompt)
- Quality gate — Score the draft 0-100. Below 85? Regenerate, max 3 attempts, use best score
Quality Scoring Criteria
- Relevance (25%) — stories matter to the audience right now
- Voice (25%) — consistent brand voice throughout
- Actionability (20%) — reader can do something with this information
- Structure (15%) — clear hierarchy, scannable, not a wall of text
- CTA (15%) — clear call to action that isn't forced
QA Review
After draft, before approval:
- Fact-check each story against its source URL
- Check all links work
- Review tone against brand voice guidelines
- Verify no duplicate content from previous issues
- Set
qa_reviewed_attimestamp
Approval Flow
Draft generated → QA reviewed → Reminders sent → Human approves → Auto-send
Reminder schedule (configurable):
- Reminder 1: 30 min after draft
- Reminder 2: Next morning
- Reminder 3: Afternoon
- Reminder 4: Evening
If not approved by send deadline → skip this week, don't send stale content.
Send Rules
- Only send if
status = 'approved' - Update status to
sentwith timestamp after successful send - Send confirmation to operator
- Never send the same newsletter twice