원클릭으로 Manus에서 모든 스킬 실행

newsletter-variant

스타0

포크0

업데이트2026년 3월 19일 09:22

Use when the user wants to convert a blog article into a newsletter email. Triggers: "newsletter from article", "email version", "convert to newsletter", "article to email", "newsletter variant".

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

heurema

heurema/content-ops

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Purpose

Convert a finished blog article into a newsletter email. One article — one focused email under 500 words, stripped of SEO scaffolding, written in first person.

Format rules

Plain text only — no HTML templates, no designed layouts. White background, black text outperforms designed templates for developer audiences.
Under 500 words total.
First-person voice throughout ("I found that..." not "This article covers...").
No keyword headers, no "In this article we'll cover", no SEO intros.
One CTA only — a single link to the full article at the end.

Structure

Personal hook (2-3 sentences) — what prompted you to write this, a surprising result, or a concrete observation. Not a summary of what the article contains.
Core insight — either 3-5 tight bullets or 2 short paragraphs. Each bullet/paragraph carries standalone value; not a table of contents.
One actionable takeaway — a single thing the reader can do or think about differently right now.
Link — "Full article: [title] → [URL]" (or placeholder if URL unknown).

Subject line

40-50 characters.
Specific benefit or concrete outcome — not a topic label.
Examples of the pattern: "How I cut deploy time by 40%" not "Deploy optimization tips".

What to strip from the article

Keyword-stuffed headers ("Best practices for X in Y")
Meta-commentary ("In this post I'll walk you through...")
Lengthy background sections written for search ranking
Repeated CTAs, sidebar promos, related-posts links

Process

Ask for the article (file path, URL, or paste).
Read the article.
Draft subject line — show it first, ask for approval or alternative.
Draft email body following the four-section structure above.
Count words. If over 500: trim core insight section first.
Show full draft. Ask for edits.
Output final as newsletter-[slug].md in the article's directory (or current directory if no article path).

Scope

Text output only. No sending, no provider API. For sending: Mailchimp, ConvertKit, Resend, or Beehiiv require separate setup outside content-ops.

이 저장소의 다른 Skills

같은 저장소

content-context

heurema/content-ops

Use when the user wants to set up or update their content profile. Also use when the user says "my blog is about", "content profile", "set up content context", or "who am I writing for". Stores context as .agents/content-context.md — read by all other content-ops skills first.

2026-03-190

content-ideas

heurema/content-ops

Use when the user wants content ideas or a backlog. Triggers: "content ideas", "what to write next", "build backlog", "ideas from changelog", "what should I post about", "content calendar".

2026-03-190

content-qa

heurema/content-ops

Use before publishing any article. Triggers: "check article", "preflight", "validate post", "is this ready to publish", "QA my post", "pre-publish check". Run this before distribute or any publish command.

2026-03-190

copy-review

heurema/content-ops

Use when the user wants feedback on marketing copy, headlines, or landing page text. Triggers: "edit landing page", "improve headline", "copy feedback", "review this copy", "is this headline good", "landing page copy review".

2026-03-190

distribute

heurema/content-ops

Use when the user wants to publish an article to multiple platforms at once. Triggers: "publish article", "distribute to platforms", "send to devto and hashnode", "cross-post", "publish everywhere", "distribute my post".

2026-03-190

email-drip

heurema/content-ops

Use when the user wants to write a welcome sequence or email drip campaign. Triggers: "welcome sequence", "newsletter drip", "onboarding emails", "email series", "welcome email". Note: generates drafts only — no sending, no API.

2026-03-190

name	newsletter-variant
description	Use when the user wants to convert a blog article into a newsletter email. Triggers: "newsletter from article", "email version", "convert to newsletter", "article to email", "newsletter variant".

Read .agents/content-context.md first (if it exists).

Purpose

Convert a finished blog article into a newsletter email. One article — one focused email under 500 words, stripped of SEO scaffolding, written in first person.

Format rules

Plain text only — no HTML templates, no designed layouts. White background, black text outperforms designed templates for developer audiences.
Under 500 words total.
First-person voice throughout ("I found that..." not "This article covers...").
No keyword headers, no "In this article we'll cover", no SEO intros.
One CTA only — a single link to the full article at the end.

Structure

Personal hook (2-3 sentences) — what prompted you to write this, a surprising result, or a concrete observation. Not a summary of what the article contains.
Core insight — either 3-5 tight bullets or 2 short paragraphs. Each bullet/paragraph carries standalone value; not a table of contents.
One actionable takeaway — a single thing the reader can do or think about differently right now.
Link — "Full article: [title] → [URL]" (or placeholder if URL unknown).

Subject line

40-50 characters.
Specific benefit or concrete outcome — not a topic label.
Examples of the pattern: "How I cut deploy time by 40%" not "Deploy optimization tips".

What to strip from the article

Keyword-stuffed headers ("Best practices for X in Y")
Meta-commentary ("In this post I'll walk you through...")
Lengthy background sections written for search ranking
Repeated CTAs, sidebar promos, related-posts links

Process

Ask for the article (file path, URL, or paste).
Read the article.
Draft subject line — show it first, ask for approval or alternative.
Draft email body following the four-section structure above.
Count words. If over 500: trim core insight section first.
Show full draft. Ask for edits.
Output final as newsletter-[slug].md in the article's directory (or current directory if no article path).

Scope

Text output only. No sending, no provider API. For sending: Mailchimp, ConvertKit, Resend, or Beehiiv require separate setup outside content-ops.