blog-repurpose

Name: blog-repurpose
Author: AgriciDaniel

1.3kinstalls251forks

How to install blog-repurpose?

agricidaniel/claude-blog/blog-repurpose

$npx -y skills add AgriciDaniel/claude-blog --skill blog-repurpose

Installs into the current project.

Summary

Repurpose blog posts for social media, email, YouTube, Reddit, and LinkedIn. Generates Twitter/X threads, LinkedIn articles, YouTube scripts, Reddit discussion posts, email newsletter excerpts. Adapts tone for each platform. Use when user says "repurpose", "blog repurpose", "shar

Files · 1

View on GitHub

SKILL.md

1	# Blog Repurpose: Cross-Platform Content Adaptation
2
3	Transforms blog posts into platform-optimized content for social media, email,
4	video, and community channels. Each output adapts tone, format, and length to
5	match platform conventions and audience expectations.
6
7	FLOW dual-surface thinking (when applicable). When the original blog post targets a query that also surfaces in a community (Reddit thread, YouTube comment, LinkedIn discussion), repurpose for the community in a way that reinforces the blog. Cross-link both directions: the blog references the community discussion as social proof; the community post references the blog as the canonical long-form answer. This is FLOW surface 5 in action. See `skills/blog/references/flow-alignment.md` and `/blog flow win` for the dual-surface scorecard.
8
9	## Workflow
10
11	### Step 1: Read & Analyze
12
13	Read the blog post and extract the core content elements:
14
15	- Title - Original blog post title
16	- Key insights (5-7) - The most important takeaways, each as a standalone statement
17	- Statistics - All sourced data points with attribution
18	- Quotes - Any notable quotations or expert statements
19	- Main argument - The central thesis in 1-2 sentences
20	- TL;DR - A 2-3 sentence summary that delivers standalone value
21	- Target audience - Who the blog was written for
22	- Topic category - For subreddit and hashtag selection
23
24	### Step 2: Ask User
25
26	Prompt the user to select which platforms to generate content for:
27
28	1. Twitter/X thread
29	2. LinkedIn article
30	3. YouTube video script
31	4. Reddit discussion post
32	5. Email newsletter excerpt
33	6. All of the above
34
35	If the user specifies a platform directly (e.g., "repurpose for Twitter"),
36	skip this step and generate for that platform only.
37
38	### Step 3: Twitter/X Thread
39
40	Generate a complete thread optimized for Twitter/X engagement:
41
42	Hook tweet (tweet 1):
43	- Open with a curiosity gap or bold statistic
44	- Must be under 280 characters
45	- Should make someone stop scrolling
46	- Pattern: "[Surprising stat or contrarian take]. Here's what [audience] needs to know:"
47
48	Insight tweets (tweets 2-6):
49	- One key point per tweet, each delivering standalone value
50	- Include a statistic with source where possible
51	- Use line breaks for readability
52	- Each tweet should work even if read in isolation
53
54	Closing tweet (final):
55	- Summarize the main takeaway in one sentence
56	- Include a clear CTA linking to the full post
57	- Add relevant hashtags (maximum 2 per tweet)
58	- Pattern: "Read the full breakdown: [link]\n\n#hashtag1 #hashtag2"
59
60	Thread formatting rules:
61	- Number tweets as 1/, 2/, etc. for clarity
62	- No tweet exceeds 280 characters
63	- Thread length: 7-9 tweets total
64	- Tone: conversational, direct, insight-dense
65
66	### Step 4: LinkedIn Article
67
68	Adapt the blog for LinkedIn's professional audience and format:
69
70	Length: 800-1,200 words (shorter than the blog post)
71
72	Opening (first 2-3 lines visible before "See more"):
73	- Start with a personal story, observation, or contrarian take
74	- This is the hook - it must compel clicking "See more"
75	- Never start with "I'm excited to share..." or similar cliches
76
77	Body structure:
78	- Use LinkedIn-native formatting: bold text for emphasis, single-line paragraphs,
79	generous line breaks between points
80	- Numbered lists for key takeaways
81	- Short paragraphs (1-3 sentences each)
82	- Include 2-3 key statistics with sources
83	- More personal and opinion-led than the original blog
84
85	Closing:
86	- End with an engagement question that invites comments
87	- Pattern: "What's your experience with [topic]? I'd love to hear in the comments."
88	- Do NOT include external links in the body (LinkedIn deprioritizes them)
89	- Add the blog link in the first comment instead (note this in the output)
90
91	Tone: Professional but conversational. First-person perspective. Share
92	what you learned or observed, not just what the data says.
93
94	### Step 5: YouTube Script
95
96	Generate a complete video script structured for retention:
97
98	Hook (0-15 seconds):
99	- Bold statement or surprising question drawn from the blog's strongest insight
100	- Pattern: "Did you know that [shocking stat]? Today I'm going to show you [promise]."
101	- Must grab attention before viewers click away
102
103	Intro (15-60 seconds):
104	- What viewers will learn (3 bullet points)
105	- Why it matters right now
106	- Brief credibility statement
107	- "[SHOW TITLE CARD]"
108
109	Main content (3-5 talking points):
110	- Derived from the blog's H2 sections
111	- Each section: key point, supporting data, practical example
112	- Include visual c

People who liked this also viewed

6 picks

Type

blog-repurpose

1.3kinstalls251forks

View on GitHub

How to install blog-repurpose?

agricidaniel/claude-blog/blog-repurpose

$npx -y skills add AgriciDaniel/claude-blog --skill blog-repurpose

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Blog Repurpose: Cross-Platform Content Adaptation
2
3	Transforms blog posts into platform-optimized content for social media, email,
4	video, and community channels. Each output adapts tone, format, and length to
5	match platform conventions and audience expectations.
6
7	FLOW dual-surface thinking (when applicable). When the original blog post targets a query that also surfaces in a community (Reddit thread, YouTube comment, LinkedIn discussion), repurpose for the community in a way that reinforces the blog. Cross-link both directions: the blog references the community discussion as social proof; the community post references the blog as the canonical long-form answer. This is FLOW surface 5 in action. See `skills/blog/references/flow-alignment.md` and `/blog flow win` for the dual-surface scorecard.
8
9	## Workflow
10
11	### Step 1: Read & Analyze
12
13	Read the blog post and extract the core content elements:
14
15	- Title - Original blog post title
16	- Key insights (5-7) - The most important takeaways, each as a standalone statement
17	- Statistics - All sourced data points with attribution
18	- Quotes - Any notable quotations or expert statements
19	- Main argument - The central thesis in 1-2 sentences
20	- TL;DR - A 2-3 sentence summary that delivers standalone value
21	- Target audience - Who the blog was written for
22	- Topic category - For subreddit and hashtag selection
23
24	### Step 2: Ask User
25
26	Prompt the user to select which platforms to generate content for:
27
28	1. Twitter/X thread
29	2. LinkedIn article
30	3. YouTube video script
31	4. Reddit discussion post
32	5. Email newsletter excerpt
33	6. All of the above
34
35	If the user specifies a platform directly (e.g., "repurpose for Twitter"),
36	skip this step and generate for that platform only.
37
38	### Step 3: Twitter/X Thread
39
40	Generate a complete thread optimized for Twitter/X engagement:
41
42	Hook tweet (tweet 1):
43	- Open with a curiosity gap or bold statistic
44	- Must be under 280 characters
45	- Should make someone stop scrolling
46	- Pattern: "[Surprising stat or contrarian take]. Here's what [audience] needs to know:"
47
48	Insight tweets (tweets 2-6):
49	- One key point per tweet, each delivering standalone value
50	- Include a statistic with source where possible
51	- Use line breaks for readability
52	- Each tweet should work even if read in isolation
53
54	Closing tweet (final):
55	- Summarize the main takeaway in one sentence
56	- Include a clear CTA linking to the full post
57	- Add relevant hashtags (maximum 2 per tweet)
58	- Pattern: "Read the full breakdown: [link]\n\n#hashtag1 #hashtag2"
59
60	Thread formatting rules:
61	- Number tweets as 1/, 2/, etc. for clarity
62	- No tweet exceeds 280 characters
63	- Thread length: 7-9 tweets total
64	- Tone: conversational, direct, insight-dense
65
66	### Step 4: LinkedIn Article
67
68	Adapt the blog for LinkedIn's professional audience and format:
69
70	Length: 800-1,200 words (shorter than the blog post)
71
72	Opening (first 2-3 lines visible before "See more"):
73	- Start with a personal story, observation, or contrarian take
74	- This is the hook - it must compel clicking "See more"
75	- Never start with "I'm excited to share..." or similar cliches
76
77	Body structure:
78	- Use LinkedIn-native formatting: bold text for emphasis, single-line paragraphs,
79	generous line breaks between points
80	- Numbered lists for key takeaways
81	- Short paragraphs (1-3 sentences each)
82	- Include 2-3 key statistics with sources
83	- More personal and opinion-led than the original blog
84
85	Closing:
86	- End with an engagement question that invites comments
87	- Pattern: "What's your experience with [topic]? I'd love to hear in the comments."
88	- Do NOT include external links in the body (LinkedIn deprioritizes them)
89	- Add the blog link in the first comment instead (note this in the output)
90
91	Tone: Professional but conversational. First-person perspective. Share
92	what you learned or observed, not just what the data says.
93
94	### Step 5: YouTube Script
95
96	Generate a complete video script structured for retention:
97
98	Hook (0-15 seconds):
99	- Bold statement or surprising question drawn from the blog's strongest insight
100	- Pattern: "Did you know that [shocking stat]? Today I'm going to show you [promise]."
101	- Must grab attention before viewers click away
102
103	Intro (15-60 seconds):
104	- What viewers will learn (3 bullet points)
105	- Why it matters right now
106	- Brief credibility statement
107	- "[SHOW TITLE CARD]"
108
109	Main content (3-5 talking points):
110	- Derived from the blog's H2 sections
111	- Each section: key point, supporting data, practical example
112	- Include visual c

People who liked this also viewed

6 picks

Type