Teardown No. 19 · Repurposing

How Sharyph repurposes each newsletter issue with five Claude Code skills

Sharyph turned his newsletter repurposing into five Claude Code skills. Each skill is a saved prompt file that runs as a slash command. After an issue is published, two skills turn it into standalone tweets and an X thread. A third pushes both into Typefully as scheduled drafts after he confirms a schedule preview. Two more write long-form authority posts and optimize blog posts for search. He says repurposing one issue used to take 3 to 4 hours and now takes under 30 minutes.

SharyphVerified Oct 16, 2026Markdown copy
Part of playbook: Repurpose each newsletter issue across platforms with agents

The problem

Before he built the skills, Sharyph says, “repurposing one newsletter issue took me 3 to 4 hours.” He adds: “Sometimes I skipped it entirely because I didn’t have the energy after writing the newsletter itself.”

The blueprint (as he describes it)

Setup. He describes a Skill as “a saved prompt file that becomes a slash command.” He gives these steps:

  1. Download Claude Code as a desktop app or VS Code extension.
  2. Open your project folder inside Claude Code.
  3. Create a folder called .claude/commands/ inside the project.
  4. Drop the skill files into that folder.
  5. Restart Claude Code. The commands appear automatically.

The five skills.

  1. /tweet takes a newsletter URL and generates 8-12 tweet variations in different formats, such as contrarian takes, question-answer formats and story nuggets. Each is under 280 characters with no hashtags or emojis. He says it takes under 2 minutes.
  2. /create-thread turns the same newsletter into an X thread. The thread has a hook, separators between tweets, mentions for companies referenced, exact URLs preserved and a CTA back to the newsletter.
  3. /push-to-typefully takes the output of /tweet and /create-thread and pushes it into Typefully as scheduled drafts across your preferred posting days and times. It shows a schedule preview before pushing anything, and you confirm.
  4. /authority-post needs no newsletter URL. It analyzes recent posts from 20+ thought leaders you specify, identifies what’s trending and the gaps, and returns 5 post concepts. You pick one. It runs a quality gate of 8 yes/no questions. If the concept passes, it writes 3 multi-paragraph posts of 100 to 500+ words in your voice.
  5. /seo-optimize optimizes a blog post or article for Google and for AI answer engines like ChatGPT, Perplexity and Claude. He calls it a 10-step process covering title tags, meta descriptions, a TL;DR answer capsule, restructured headings, paragraph optimization, internal links, an FAQ section and key takeaways. It produces 4 output files in an organized folder.

Weekly order. He runs the skills in this sequence after each issue:

  1. Newsletter published.
  2. /tweet and /create-thread.
  3. /push-to-typefully, with one confirmation.
  4. /authority-post for mid-week long-form posts.
  5. /seo-optimize for blog posts.

In his words: “One newsletter. One session.”

Stated results

  • Repurposing one issue went from 3 to 4 hours to under 30 minutes (his estimate).
  • Before the skills, he sometimes skipped repurposing entirely.
  • /tweet produces 8-12 tweets in under 2 minutes (his description).
  • He says output quality is better because he isn’t rewriting prompts from memory, making format decisions when tired or forgetting a CTA. “The system holds all of that. I just review and publish.”
  • No engagement, follower, traffic, ranking or AI-citation figures are stated.

Why this matters for postby.ai

  • One saved command per output format is a simple pattern for a repurposing loop.
  • The schedule preview and confirm step before anything reaches Typefully keeps a human in the loop at the point where content goes live.

Caveats

  • The post sells a paid tier. The skill files are “available exclusively to paid members of The Digital Creator” at $39/month or $150/year. The post doesn’t include the files, so the prompts themselves can’t be checked.
  • This is first-person, written by Sharyph in his own newsletter. It is not a third-party story.
  • The time figures are self-reported. No before/after measurement or engagement data is given.
  • The post doesn’t explain how /push-to-typefully connects to Typefully.
  • The scheduling scope is inconsistent. The text says “An entire week of content”, while the workflow diagram says “Everything scheduled for the weeks and month.”
  • The diagram describes /seo-optimize output as “Blog posts ranked on Google and cited by AI tools”. No evidence of rankings or citations is given.
  • X: @sharyph_ appears in a thread link in the source. Unverified Not checked against his own site.

Sources

Want agents like these working your distribution? See the Agent Stack Teardown. Get new teardowns weekly: subscribe (double opt-in).

Get one teardown a week.

Same format, a new operator every issue. Double opt-in.