Skill LukeJMadden/Veltrix-skills/skills/content/newsletter

Newsletter pipeline skill — drafting, quality assurance, approval flow, scheduling. Use when creating, reviewing, or managing email newsletters.From its SKILL.md

Install

npx -y skills add LukeJMadden/Veltrix-skills --skill newsletter

Assembled 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.

SKILL.md

1.8 KB, 407 tokens by cl100k_base, 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_at timestamp

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 sent with timestamp after successful send
Send confirmation to operator
Never send the same newsletter twice

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most marketing audience skills give in 407 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

Apply Poppins font to headingsin 41 of 690, across 6 files
Apply Lora font to body textin 41 of 690, across 6 files
Use Arial fallback for headingsin 39 of 690, across 4 files
Use Georgia fallback for body textin 39 of 690, across 4 files
Maintain text hierarchy and formattingin 39 of 690, across 4 files
Use accent colors for non-text shapesin 38 of 690, across 3 files
Use RGB values for precise color matchingin 38 of 690, across 3 files
Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
Use active voice instead of passive voicein 26 of 690, across 10 files
Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

pull top weekly content
curate three to five ranked stories
write TLDR-format story summaries
include a recurring weekly kit section
score the draft on a zero to hundred scale
regenerate drafts scoring below eighty-five

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.