agentleFS
Sign inStart free
LukeJMaddenLukeJMadden/Veltrix-skills/skills/content/newsletter/SKILL.md

newsletter

Skill1 starsChanged 8 months agoMITView on GitHub

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

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use lead-magnet, linkedin and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • robertbstillwellSkill

    lead-magnet

    Create lead magnets and gated content to capture email subscribers and leads. Use when asked to design checklists, templates, calculators, mini-courses, whitepapers, or other downloadable content offers. Trigger phrases: "lead magnet", "gated content", "email capture", "content offer", "free download", "checklist", "template", "whitepaper", "swipe file", "content upgrade", "opt-in offer".

    Also in 4 projects that use this

  • kkoppenhaverSkill

    linkedin

    Write LinkedIn posts in Keanan's voice. Use when drafting LinkedIn content, creating professional posts, or sharing builder-focused insights. Triggers include requests to "write a LinkedIn post", "draft something for LinkedIn", "help me post on LinkedIn", or any LinkedIn content creation. Generates upbeat, builder-centric content mixing practical how-tos with candid humor.

    Also in 3 projects that use this

  • silvainfmSkill

    referral-program

    When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization.

    Also in 3 projects that use this

  • silvainfmSkill

    launch-strategy

    When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

    Also in 3 projects that use this

  • indranilbanerjeeSkill

    keyword-research

    Research keywords via the connected data source: intent, gaps. Grouping → keyword-cluster. \"what keywords should we target\"

    Also in 3 projects that use this

  • +1 more from silvainfm

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After draft, before approval:

    line 26
  2. Distinctive:

    Check all links work

    line 28
  3. Distinctive:

    Verify no duplicate content from previous issues

    line 30
  4. Distinctive:

    If not approved by send deadline → skip this week, don't send stale content.

    line 45
  5. Very specific:

    Only send if status = 'approved'

    line 49
  6. Very specific:

    Update status to sent with timestamp after successful send

    line 50
  7. Distinctive:

    Never send the same newsletter twice

    line 52

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Manage the full newsletter lifecycle from draft to send.

Draft Pipeline

  1. Source — Pull top content from the week (news, blog posts, tool updates)
  2. Curate — Select 3-5 stories, ranked by relevance to audience
  3. Write — TLDR format: headline → 2-sentence summary → "why it matters"
  4. Weekly Kit — Include a recurring section (stat of the week, editor's pick, featured prompt)
  5. 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:

  1. Fact-check each story against its source URL
  2. Check all links work
  3. Review tone against brand voice guidelines
  4. Verify no duplicate content from previous issues
  5. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free