Content Repurposing Skills

中文版本 ｜ Content Repurposing Skills Review

Reusable Agent Skills for turning long-form blog articles into platform-native social posts. Give it a real article - get a sharp Twitter/X or LinkedIn post, source-grounded angle, current trend adaptation, and a primary visual concept or generated image.

Built for content repurposing, not generic summarization. The skills extract one strong idea from a full article and package it for reach, saves, replies, reposts, and professional discussion.

---

Example Output

Each run produces a structured social post package with:

Use $blog-to-twitter-post.
Target language: English
Style: Founder
Audience: Indie Hacker

---

Skills

Both skills require a real blog/article input of at least 500 words. For CJK articles without whitespace, use an equivalent long-form article, usually 800+ CJK characters after removing navigation, boilerplate, author bio, comments, and CTA blocks.

---

Repurposing Coverage

Source Handling

Strategy Layer

Output Layer

---

Structure

content-repurposing-skills/
|-- blog-to-twitter-post/
|   |-- SKILL.md
|   `-- references/
|       `-- platform-rules.md
|-- blog-to-linkedin-post/
|   |-- SKILL.md
|   `-- references/
|       `-- platform-rules.md
|-- assets/
|   |-- demo-1.jpg
|   |-- demo-2.jpg
|   |-- demo-3.jpg
|   |-- demo-4.jpg
|   `-- demo-5.jpg
|-- skills-lock.json
|-- README.md
`-- README.zh.md

---

Architecture: Source + Trend + Platform

Blog article / URL
        |
        v
+----------------------------------------------+
| Layer 1 - Source Grounding                   |
| Validate length, clean boilerplate, preserve |
| claims, quotes, examples, numbers, and risk  |
+-----------------------+----------------------+
                        |
                        v
+----------------------------------------------+
| Layer 2 - Editorial Strategy                 |
| Article spine, soul quote, audience pain,    |
| best social angle, and platform fit          |
+-----------------------+----------------------+
                        |
                        v
+----------------------------------------------+
| Layer 3 - Runtime Adaptation                 |
| Current platform rules + last-30-day trends  |
| only when the semantic bridge is real        |
+-----------------------+----------------------+
                        |
                        v
+----------------------------------------------+
| Layer 4 - Publishable Package                |
| Post copy, CTA, hashtags, visual brief or    |
| generated image, alt text, and source notes  |
+----------------------------------------------+

Why this architecture? Source grounding keeps the post faithful to the article. Editorial strategy prevents generic summaries. Runtime adaptation keeps platform rules and trend hooks current without forcing weak trends into the copy.

---

Installation

Option 1: Install from GitHub

npx skills add JeffLi1993/content-repurposing-skills --skill blog-to-twitter-post
npx skills add JeffLi1993/content-repurposing-skills --skill blog-to-linkedin-post

Option 2: Install from a local checkout

npx skills add /Users/jeff/JeffPage/creations/code-skill/content-repurposing-skills/blog-to-twitter-post
npx skills add /Users/jeff/JeffPage/creations/code-skill/content-repurposing-skills/blog-to-linkedin-post

Restart your agent after installing or updating a skill.

---

Usage

Use $blog-to-twitter-post.
Target language: English
Style: Founder
Audience: Indie Hacker

Use $blog-to-linkedin-post.
Target language: Chinese
Style: Growth Expert
Audience: SaaS Team

You can also provide optional context:

Source URL:
Brand/Product:
Publishing account:
Tone constraints:
Do not mention:

---

Output Discipline

These skills are intentionally strict:

• They do not draft from a topic brief or a short outline.
• They do not invent quotes, data, screenshots, customer stories, or product results.
• They do not force trend hooks when the bridge to the article is weak.
• They do not turn a blog into a full summary.
• They do not publish or schedule posts unless explicitly asked and proper tools are available.

---

License

MIT