From file to useful result
How to ask with this skill installed
Installing the skill gives your AI a method. Your request still has to provide the case-specific facts, constraints and expected output.
1Name the real task
Describe the decision or deliverable, not just the topic.
2Provide the evidence
Add source material, audience, limits and known facts.
3Define done
Set format, quality criteria and checks.
Adaptable starting prompt
Replace the brackets with your case
When to use it
A writer, editor, or content manager has existing content that needs to be transformed rather than created from scratch — either because the content exists but isn't working, needs to reach a different audience, or needs to fit a different format.
Common triggers:
- Repurposing a blog post into a LinkedIn article, email newsletter, or social posts
- Adapting B2B content for a B2C audience (or vice versa)
- Updating outdated content ("refreshed for 2026")
- Converting a podcast transcript into a blog post
- Translating Spanish content to English (or vice versa) while preserving tone
- Simplifying technical content for a general audience
- Elevating rough notes or bullet points into polished prose
- Converting a long-form guide into a series of social posts
- Editing a first draft into publication-ready copy
- Adapting content for different platforms (Twitter thread → blog → newsletter)
What this skill does NOT do:
- This is not original content creation — it works from existing source material
- This is not deep structural revision (rewriting is transformation, not restructuring)
- This is not fact-checking or research — the content is given, facts are assumed
- This is not SEO keyword research — keywords are inputs, not discovered here
- This is not proofreading only (see: light copyedit for grammar/spelling focus)
Mistakes to avoid
- Rewording without transforming — Just swapping synonyms isn't a rewrite. The content needs to feel native to the new format.
- Keeping the same structure — A LinkedIn post with the same H2 headers as a blog post reads like a blog post.
- Losing the original's value — When transforming formats, make sure key data or insights aren't accidentally deleted.
- Inconsistent tone — The first paragraph is conversational but the last is formal? That breaks trust.
- Forgetting the audience swap — Using the same jokes, references, or idioms for a different audience.
- Too many formats from one source — Each adaptation should feel native, not like "here's the Twitter version of the blog post."
- Not adding new value — A rewrite should improve on the original, not just compress it.