agentsclimarketplace

Newsletter production cadence

Skill Get-Maito/newsletter-skills/skills/newsletter/newsletter-production-cadence

Open-source agent skills for newsletter operators.

Install
npx -y skills add Get-Maito/newsletter-skills --skill newsletter-production-cadence

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

  • 0 stars0 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

Use when the user asks to maintain a consistent publishing cadence, plan a content calendar, reduce weekly production bottlenecks, assign newsletter tasks, prevent missed issues, or build a repeatable issue workflow.

SKILL.md

1.5 KB, as published. Nobody here has run it

Newsletter Production Cadence

Keep newsletter production consistent.

Core Rule

Use the connected workspace for issue state, approval status, source history, reusable checklists, and workflow notes when available.

Inputs

  • Newsletter cadence and next send dates
  • Sections, owners, deadlines, and approval preferences
  • Source list, sponsor obligations, and social needs
  • Known bottlenecks: sourcing, writing, proofing, sponsor copy, social, or approvals
  • Connected workspace or issue details, if available

Workflow

  1. Map the issue cycle from research to publish.
  2. Identify the bottleneck that risks cadence.
  3. Create a compact production calendar with owners and deadlines.
  4. Add checklists for sources, links, sponsor copy, proofing, test send, and social follow-up.
  5. Save or hand off reusable workflow notes for the connected workspace.

Output Format

Include:

  • Production calendar
  • Bottleneck summary
  • Issue checklist
  • Owner or role assignments
  • Connected-workspace handoff notes

Guardrails

  • Do not invent owner availability or deadlines.
  • Keep the workflow small enough for a solo operator or small team to follow.
  • Flag any issue that is not ready rather than forcing a send.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.