plugins/octave/skills/repurpose/SKILL.md
Repurpose existing content (text, file, URL) for a different audience, persona, or context using your Octave library. Use when user says "repurpose this", "adapt for [persona]", "convert this blog to email", "rewrite for a different audience", or provides existing content to transform.
npx skillsauth add octavehq/lfgtm repurposeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Transform existing content for a different audience, persona, channel, or context—grounded in your Octave library.
/octave:repurpose <source>
Where <source> can be:
/octave:repurpose "Our platform reduces deployment time by 80%..."
/octave:repurpose ./content/enterprise-whitepaper.md
/octave:repurpose https://blog.company.com/our-product-launch
/octave:repurpose --from "CTO audience" --to "CFO audience"
When the user runs /octave:repurpose:
Identify the source type and extract content:
If text provided directly:
Got it! I've captured your content:
---
[Preview first 200 chars]...
---
[X words total]
If file path provided:
If URL provided:
If no source provided, ask:
What content would you like to repurpose?
1. Paste text directly
2. Provide a file path
3. Provide a URL
4. Upload a document
(Paste your content or provide a path/URL):
Ask clarifying questions to understand the transformation:
Great! Now let's define how to repurpose this content.
WHO is this for?
(Select a persona, segment, or describe the audience)
1. [List personas from library via list_entities]
2. [List segments from library]
3. Describe a custom audience
Your choice:
After persona/audience selection:
WHAT transformation do you need?
1. Adjust tone/voice for [selected persona]
2. Change format (e.g., blog → email, whitepaper → one-pager)
3. Shift focus/angle (e.g., technical → business value)
4. Adapt for different channel (LinkedIn, email, presentation)
5. Condense/expand length
6. Multiple transformations
Your choice:
Optional follow-up:
Any specific instructions or changes?
Examples:
- "Focus more on ROI and cost savings"
- "Make it more conversational"
- "Remove technical jargon"
- "Add a stronger CTA"
- "Keep the same structure but change examples"
(Enter instructions or press Enter to skip):
Based on the repurposing goal, fetch relevant context:
For Persona-Based Repurposing:
# Get persona details
get_entity({ oId: "<selected_persona_oId>" })
# Find the Motion ICP cell for this persona × segment for messaging guidance
list_motions()
list_motion_icps({ motionOId: "<motion_oId>" })
find_motion_icp({ motionIcpOId: "<motion_icp_oId>", includeLearnings: true })
# Get brand voice if adjusting tone
list_entities(entityType: "brand_voice")
# Get writing style if specified
list_writing_styles()
For Segment-Based Repurposing:
# Get segment details
get_entity({ oId: "<selected_segment_oId>" })
# Find personas in this segment
search_knowledge_base({
query: "<segment name> persona buyer",
entityTypes: ["persona"]
})
# Find Motion ICP cells that cover this segment
list_motions()
list_motion_icps({ motionOId: "<motion_oId>" })
find_motion_icp({ motionIcpOId: "<motion_icp_oId>", includeLearnings: true })
For Format/Channel Changes:
# Get brand voice guidelines
list_entities(entityType: "brand_voice")
# Get writing style for target format
search_knowledge_base({
query: "<target format> writing style",
entityTypes: ["writing_style"]
})
Present the transformation plan before executing:
REPURPOSING PLAN
================
Source Content:
- Type: [Blog post / Email / Document / etc.]
- Length: [X words]
- Original audience: [Inferred or stated]
Target:
- Audience: [Selected persona/segment]
- Format: [Same / Changed to X]
- Tone: [Based on brand voice / persona]
Key Changes:
1. [Change 1 - e.g., "Shift from technical features to business outcomes"]
2. [Change 2 - e.g., "Add CFO-relevant proof points"]
3. [Change 3 - e.g., "Shorten to 300 words for email"]
Context I'll Use:
- Persona: [Name] - [Key pain points to address]
- Motion ICP: [Persona × Segment] - [Strategic narrative angle]
- Brand Voice: [Name] - [Tone characteristics]
Proceed with repurposing? (yes / adjust plan):
Use the generate_content MCP tool with gathered context:
generate_content({
instructions: `
Repurpose the following content for [persona/audience].
ORIGINAL CONTENT:
${originalContent}
TARGET PERSONA: [Persona details from library]
- Pain points: [List]
- Priorities: [List]
- Communication preferences: [Details]
TARGET FORMAT: [Format]
TONE/VOICE: [Brand voice guidelines]
SPECIFIC INSTRUCTIONS:
${userInstructions}
KEY CHANGES TO MAKE:
1. [Change 1]
2. [Change 2]
3. [Change 3]
Maintain the core message while adapting language, examples, and emphasis
to resonate with the target audience.
`,
customContext: "[Relevant Motion ICP narrative, proof points, etc.]"
})
REPURPOSED CONTENT
==================
[Generated content]
---
CHANGES MADE
------------
✓ [Change 1 description]
✓ [Change 2 description]
✓ [Change 3 description]
CONTEXT APPLIED
---------------
- Persona pain points addressed: [List]
- Messaging angle: [From Motion ICP narrative]
- Tone: [From brand voice]
---
What would you like to do?
1. Refine further (provide feedback)
2. Try a different angle
3. Repurpose for another audience
4. Save to library as a template
5. Done - copy to clipboard
If the user wants refinement:
What would you like me to adjust?
1. Make it more [formal/casual/urgent/etc.]
2. Focus more on [specific topic]
3. Add [specific element]
4. Remove [specific element]
5. Change the CTA
6. Other (describe)
Your feedback:
Then regenerate with updated instructions.
See common-scenarios.md for the four common repurposing scenario templates (Blog → Email Sequence, Technical Doc → Executive Summary, Internal → External, One Persona → Another).
list_entities - Get available personas and segmentslist_entities (entityType: "brand_voice") - Get available brand voice configurationslist_writing_styles - Get available writing style configurationsget_entity - Get full details for persona and segment entities by oIdlist_motions - List Motions in the workspacelist_motion_icps - List Motion ICP cells (persona × segment) for a Motionfind_motion_icp - Fetch a Motion ICP narrative + Learning Loop learningssearch_knowledge_base - Find relevant proof points, messaging, examplesgenerate_content - Generate the repurposed content with contextAccept text directly in the command or pasted in follow-up:
/octave:repurpose "Your content here..."
Accept local file paths:
/octave:repurpose ./path/to/content.md
/octave:repurpose /absolute/path/to/document.txt
Supported file types: .md, .txt, .doc, .docx, .pdf, .html
Accept web URLs:
/octave:repurpose https://example.com/blog-post
Use WebFetch to extract content, then proceed with repurposing.
No Source Content:
I need content to repurpose. Please provide:
- Text (paste directly)
- File path (e.g., ./content/blog.md)
- URL (e.g., https://blog.example.com/post)
File Not Found:
I couldn't find the file at [path]. Please check the path and try again, or paste the content directly.
URL Fetch Failed:
I couldn't fetch content from [URL].
This might be because:
- The page requires authentication
- The URL is incorrect
- The site blocks automated access
Try: Paste the content directly, or provide a different URL.
No Personas/Context in Library:
Your library doesn't have personas defined yet.
I can still repurpose content, but it will be more generic.
Options:
- Describe your target audience manually
- Create a persona first (/octave:library create persona)
- Proceed without persona context
Content Too Long:
The source content is quite long ([X words]).
Options:
- Repurpose the full content (may take longer)
- Select a section to repurpose
- Let me summarize first, then repurpose the summary
/octave:generate - Generate new content from scratch/octave:library - Manage personas, Motions, Motion Playbooks, and other context/octave:brainstorm - Brainstorm content ideas/octave:pmm - Create marketing collateral/octave:campaign - Multi-channel campaign contentdevelopment
Turn one or more Octave GTM Explorer / Beats reports into a branded, shareable digest with selectable insight scope, evidence depth, and output format. Use when the user asks for a report digest, weekly or monthly insight recap, executive intelligence brief, magazine-style insight story, report deck, or a recurring published summary of Octave insights.
content-media
Product and feature launch planning with full content kit generation across channels and audiences. Use when user says "launch plan", "product launch", "feature announcement", "GTM plan for launch", "launch content kit", or mentions launching something new.
development
A dense internal deal room a rep hands to a champion so they can run the buying-committee sell without you in the room. Quantified business case, stakeholder map with per-seat ammo, objection handling, and a path to yes, rendered as self-contained HTML. Use when user says "champion deal room", "arm my champion", "help my champion sell internally", "internal business case for [deal]", or wants a champion enablement doc. For a customer-facing top-of-funnel page use /octave:microsite; for the formal closing proposal use /octave:proposal.
data-ai
Analyze email threads, call transcripts, and conversations for resonance, adherence to messaging, and competitive differentiation. Use when user says "analyze this call", "how did the email land", "score this thread", "conversation analysis", or pastes conversation content to evaluate.