agentsclimarketplace
Sign in

Newsletter production cadence

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

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.From its SKILL.md

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.

SKILL.md

1.5 KB, 255 tokens by cl100k_base, 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.

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 255 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

  • use the connected workspace for issue state
  • map the issue cycle from research to publish
  • identify the bottleneck that risks cadence
  • create a compact production calendar with owners
  • add checklists for sources and sponsor copy
  • save reusable workflow notes for the workspace

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.

Keep looking

Skills are one crate of 325,949. 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.