What does this skill do, and when should you use it?
Blog Repurpose is a single content-repurposing skill from the claude-blog repository. It reads a blog post and extracts its title, insights, sourced statistics, quotations, thesis, summary, audience, and topic category. It can produce a Twitter/X thread, LinkedIn article, YouTube script, Reddit discussion post, and email newsletter excerpt, adapting tone, format, and length for each channel. It fits creators and marketing teams that already have a source article and need structured multi-channel derivatives.
Reads a specified blog file and extracts core content elements, including key insights, attributed statistics, quotations, the main argument, a TL;DR, target audience, and topic category; generates selected or all supported formats; applies platform-specific length, structure, tone, CTA, visual-cue, and self-promotion rules; and saves generated Markdown files under repurposed/ with platform-specific filenames.
- A solo author has a finished article and wants a Twitter/X thread plus an email excerpt.
- A marketing team needs to adapt a long-form post into a professional LinkedIn article and a YouTube script.
- A community manager wants to turn blog findings into a peer-oriented Reddit discussion rather than a promotional post.
- A content team needs consistent derivatives with different platform limits, tones, and calls to action.
How do you install this skill?
- Statistics, citations, and links require manual verification; the skill does not automatically establish source truth or link validity.
- The save step creates and writes to repurposed/, but overwrite-conflict handling, recovery, and rollback are unspecified.
- Rules for Reddit, LinkedIn, Twitter/X, YouTube, and email may change; outputs should not be published without human review.
- No Chinese-language adaptation, regional-context guidance, or mainland-China platform alternatives are provided.
- Local filesystem
This skill is distributed as part of the claude-blog collection. For the public Claude Code repository, run /plugin marketplace add AgriciDaniel/claude-blog, then /plugin install claude-blog@agricidaniel-claude-blog, and restart Claude Code. The source does not document a standalone installation procedure for this individual skill.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/blog-repurpose" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- repurpose for Twitter.
Run /blog repurpose <file>, for example /blog repurpose posts/launch.md. If no platform is specified, the skill asks you to choose Twitter/X, LinkedIn, YouTube, Reddit, email, or all of them. You can also request a single format directly, such as “repurpose for Twitter.” Outputs are saved under repurposed/.
What are this skill's strengths and limitations?
- Covers five concrete derivative formats across social, video, email, and community channels.
- Defines platform-specific constraints for length, structure, tone, and formatting.
- Extracts statistics and quotations from the source article and preserves attribution requirements.
- Supports reciprocal linking between a blog and a related community discussion when applicable.
- Requires an existing blog post and does not itself serve as the repository’s general research or article-writing workflow.
- The source provides no independent test count or release evidence for this individual skill.
- The workflow mentions subreddit suggestions and rule checks, but does not document an automated network-based checking mechanism.
- Final outputs still need editorial review for links, brand voice, factual accuracy, and platform fit.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Blog Repurpose this page | 50 · Use with care | ★ 2.4k | 14d ago | MIT |
| Market Social — 30-Day Social Media Calendar Generator | 48 · Use with care | ★ 2.8k | 8mo ago | MIT |
| Platform Norm Profiler | 60 · Recommended | ★ 3k | 13d ago | Apache-2.0 |
| Social Creative Builder | 59 · Recommended | ★ 3k | 13d ago | Apache-2.0 |
| Channel Portfolio Planner | 57 · Use with care | ★ 3k | 13d ago | Apache-2.0 |
Compared with manually prompting for each channel, this skill offers one extraction workflow and explicit platform-specific output rules. The source does not provide a direct comparison with dedicated repurposing products.
How did FollowSkills review this skill?
The skill is scoped to user-provided blog content and writes outputs under repurposed/, with no requested credentials, network calls, or destructive operations, and it asks the user to choose platforms first. However, cross-linking, external links, and statistic reuse lack explicit confirmation, sensitive-data guidance, source verification, and rollback instructions, so points are deducted.
The workflow specifies platform formats, character limits, lengths, and output filenames in detail, but abnormal-input handling and failure feedback are thin. The supplied CI and tests mainly cover other repository components and do not cover this skill's key path; under static calibration the score remains below 10.
Trigger phrases, target platforms, and output scope are clear, and direct single-platform requests are supported. However, non-fit scenarios, Chinese or localization guidance, and boundaries for changing platform rules or regional reachability are not defined, so points are deducted.
The skill has frontmatter, an MIT license, an argument hint, structured steps, naming rules, and usage-oriented examples. It lacks skill-specific versioning, changelog, maintenance owner, update path, FAQ, dependency notes, and troubleshooting, and it references FLOW material not expanded within the skill, so points are deducted.
The task, formats, and platform constraints for adapting blog content into social, video, and email drafts are well specified, suggesting directly reviewable outputs. But there are no skill-specific representative outputs or execution evidence, and statistic accuracy, platform compliance, and link validity still require manual review; the static score is therefore capped.
The skill provides inspectable formatting constraints and deterministic output filenames, but no skill-specific tests, sample artifacts, third-party reproduction records, or source-verification results. Repository-level CI and tests do not establish this path's key behavior, so verifiability is limited.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →