content repurposer

Writing Community

Skill notes

Overview

Adapt the message to the channel instead of reposting the same copy everywhere.

Core Workflow

Extract the core message, audience, voice, proof points, and call to action from the source. Decide which formats are needed and what each channel rewards: hook, cadence, depth, or brevity. Rewrite for each channel's mechanics rather than merely shortening the original. Vary hooks, openings, and structure so the outputs feel native to the platform. Keep the central message aligned across all variants.

Deliver

Produce channel-ready drafts with clear labels. Preserve the original voice unless a new one is requested. Note any source gaps that weaken credibility or conversion.

Guardrails

Do not fabricate testimonials, metrics, or outcomes. Avoid obvious copy-paste repetition across channels. Keep CTAs realistic and matched to the audience stage.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Writing
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@00PrabalK00 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Content Repurposer

## Overview

Adapt the message to the channel instead of reposting the same copy everywhere.

## Core Workflow

1. Extract the core message, audience, voice, proof points, and call to action from the source.
2. Decide which formats are needed and what each channel rewards: hook, cadence, depth, or brevity.
3. Rewrite for each channel's mechanics rather than merely shortening the original.
4. Vary hooks, openings, and structure so the outputs feel native to the platform.
5. Keep the central message aligned across all variants.

## Deliver

- Produce channel-ready drafts with clear labels.
- Preserve the original voice unless a new one is requested.
- Note any source gaps that weaken credibility or conversion.

## Guardrails

- Do not fabricate testimonials, metrics, or outcomes.
- Avoid obvious copy-paste repetition across channels.
- Keep CTAs realistic and matched to the audience stage.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.