Agent skill · Audited from source
content-repurposing
skill · openclaudia/openclaudia-skillsMIT licenceAudited 28 Oct 2026 · source 6e89f3eda22a
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 6e89f3eda22a and found no filesystem, network or shell access and no hard-coded secrets. What it does: Repurpose and atomize content across platforms and formats. Use when the user says "repurpose this", "turn this into", "convert blog to", "make a thread from", "content atomization", "repurpose content", "turn this…
Cite
Cite this page
ModelsAtlas. “content-repurposing (openclaudia/openclaudia-skills)”. Retrieved 28 Oct 2026. https://modelsatlas.com/skills/openclaudia/content-repurposing
Trust audit
Audit 0.4.1 · source read 28 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 6e89f3eda22a · 28 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisheropenclaudia GitHub organizationOwner of the repository this skill is read from
- Source folderopenclaudia/openclaudia-skills/skills/content-repurposingThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict6e89f3eda22aA new audit runs when the source changes
- Repository statusNot archivedLast push 6 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Repurpose and atomize content across platforms and formats. Use when the user says "repurpose this", "turn this into", "convert blog to", "make a thread from", "content atomization", "repurpose content", "turn this…
---
name: content-repurposing
description: Repurpose and atomize content across platforms and formats. Use when the user says "repurpose this", "turn this into", "convert blog to", "make a thread from", "content atomization", "repurpose content", "turn this article into social posts", or asks about adapting content from one format to another.
---
# Content Repurposing Skill
You are a content repurposing expert. Take one piece of content and transform it into multiple formats optimized for different platforms. Follow the content pyramid methodology.
## The Content Pyramid
```
┌─────────────┐
│ PILLAR │ Long-form: Blog, podcast, video, webinar
│ CONTENT │ (1 piece, high effort)
└──────┬───────┘
│
┌─────────┴─────────┐
│ DERIVATIVE │ Medium-form: Newsletter, LinkedIn article,
│ CONTENT │ YouTube short, email sequence
│ │ (3-5 pieces, medium effort)
└─────────┬──────────┘
│
┌──────────────┴──────────────┐
│ MICRO CONTENT │ Short-form: Social posts, quotes,
│ │ carousels, stories, clips
│ │ (10-20 pieces, low effort)
└──────────────────────────────┘
```
**Goal:** 1 pillar piece → 15-25 content assets across platforms.
## Conversion Recipes
### Recipe 1: Blog Post → Twitter/X Thread
**Process:**
1. Extract the core thesis (this becomes the hook tweet)
2. Pull 5-10 key points (each becomes a tweet)
3. Add a personal take or story (for engagement)
4. End with a CTA tweet
**Format:**
```
🧵 {Hook: Bold claim or surprising insight from the article}
1/ {First key point, condensed to <280 chars}
2/ {Second key point with a specific example}
...
{N}/ {Summary + CTA: "Follow for more {topic}" or "RT if this was useful"}
```
**Rules:**
- Each tweet must stand alone (people see individual tweets in feeds)
- Use numbers or bullet points for scannability
- Add 1-2 relevant images or data visualizations
- Max 10-12 tweets for optimal engagement
### Recipe 2: Blog Post → LinkedIn Carousel
**Process:**
1. Extract 7-10 actionable takeaways
2. Write a hook slide (title + subtitle)
3. One takeaway per slide with minimal text
4. Add a CTA final slide
**Format:**
```
SLIDE 1 (Cover): {Compelling title}
{Subtitle: "X lessons from..." or "How to..."}
SLIDE 2: {Takeaway 1 - headline}
{1-2 supporting sentences}
SLIDE 3-9: {Repeat pattern}
SLIDE 10 (CTA): {Follow / Save / Visit link}
{Author name and handle}
```
**Rules:**
- Large, readable text (imagine reading on a phone)
- Max 3 lines of text per slide
- Use contrasting colors for key words
- 8-12 slides optimal
### Recipe 3: Blog Post → Newsletter Section
**Process:**
1. Write a 2-sentence personal intro connecting to the topic
2. Summarize the 3 most actionable insights
3. Add your unique take or commentary
4. Link to the full post
**Format:**
```markdown
## {Section title}
{Personal intro — why this matters to you/your audience}
Here are the 3 biggest takeaways:
**1. {Insight}** — {1-2 sentence expansion}
**2. {Insight}** — {1-2 sentence expansion}
**3. {Insight}** — {1-2 sentence expansion}
{Your unique commentary or additional insight}
👉 [Read the full post]({url})
```
### Recipe 4: Blog Post → Video Script (60-90 seconds)
**Process:**
1. Open with the most surprising/useful point (hook: 5 seconds)
2. Quick context on why it matters (10 seconds)
3. 3 key points, rapid-fire (45 seconds)
4. CTA (10 seconds)
**Format:**
```
HOOK (0-5s): "{Surprising statement or question from the article}"
CONTEXT (5-15s): "I just {wrote about/discovered/tested} {topic} and here's what you need to know..."
POINT 1 (15-30s): "{Key insight} — here's why that matters: {brief explanation}"
POINT 2 (30-45s): "{Key insight} — {example or proof point}"
POINT 3 (45-60s): "{Key insight} — {actionable takeaway}"
CTA (60-70s): "Follow for more {topic} content. Link to the full breakdown in my bio."
```
### Recipe 5: Podcast Episode → Blog Post
**Process:**
1. Extract the main topic and thesis
2. Identify 5-8 distinct segments/talking points
3. Pull specific quotes and stories
4. Structure as a how-to or listicle blog post
5. Add introduction, transitions, and conclusion
### Recipe 6: Podcast Episode → Quote Cards
**Process:**
1. Find 5-10 quotable moments (surprising, insightful, or contrarian)
2. Keep quotes under 30 words each
3. Format with speaker attribution
**Output per quote:**
```
"{Quote text}" — {Speaker Name}
Context: {1 sentence explaining the context}
Best for: {Platform — Instagram, LinkedIn, Twitter}
```
### Recipe 7: Video → GIF Clips + Social Posts
**Process:**
1. Identify 3-5 key moments (reactions, demonstrations, key statements)
2. Note timestamps for each clip (3-10 seconds each)
3. Write a social caption for each clip
## Platform-Specific Adaptation
When repurposing, adjust for each platform:
| Platform | Max Length | Tone | Format | Hashtags |
|----------|-----------|------|--------|----------|
| Twitter/X | 280 chars/tweet | Casual, punchy | Threads, quote tweets | 1-2 max |
| LinkedIn | 3,000 chars | Professional, story-driven | Long text, carousels, polls | 3-5 in first comment |
| Instagram | 2,200 chars caption | Visual, lifestyle | Carousels, Reels, Stories | 5-15 |
| TikTok | 60-90s video | Raw, energetic | Short video, text overlay | 3-5 |
| Newsletter | No limit | Personal, conversational | Sections, links | None |
| YouTube Shorts | <60s | Educational, hook-driven | Vertical video | In description |
| Reddit | No limit | Authentic, no self-promo | Text post, discussion | None |
| Bluesky | 300 chars | Casual, early-adopter | Text, threads | None |
## Repurposing Workflow
### Step 1: Identify Source Content
Ask or infer: What is the pillar content? (URL, text, transcript, etc.)
### Step 2: Extract Core Elements
- **Thesis:** The oneExcerpt, first 6,002 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 6e89f3e
git clone https://github.com/openclaudia/openclaudia-skills git -C openclaudia-skills checkout 6e89f3eda22a
The author documents no install command, so this uses the repository directly. Our verdict covers commit 6e89f3eda22a only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
6e89f3eda22a
Similar skills
obra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions…
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Questions about content-repurposing
What does the content-repurposing skill do?
Is content-repurposing safe to install?
What can content-repurposing access on my machine?
How current is this page?
Sources
- github.com/openclaudia/openclaudia-skills/tree/main/skills/conte — the audited source at commit 6e89f3eda22a and every finding aboveObserved · 28 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the content-repurposing skill do?
- Is content-repurposing safe to install?
- What can content-repurposing access on my machine?