// Use when the user wants to repurpose a draft, article, transcript, research dump, or outline into multiple platform-specific outputs across Substack, LinkedIn, Threads, Instagram carousel, and Substack Notes.
Use when the user wants to turn an idea into a fully formed design or spec before writing any code or building anything. Triggers on requests to build a feature, create a component, add functionality, modify behavior, or any creative work that requires clarifying intent, requirements, and design first.
Use when the user asks for captions, emails, sales copy, launch copy, website copy, DMs, scripts, posts, content rewrites, or nurture sequences in a specific brand voice. Also use when the user says things like "write this in my voice", "make this sound like me", "rewrite this", "does this sound on-brand", "too formal", "too robotic", or any request where the output needs to match a specific tone, style, or personality. Also trigger when the user pastes their own draft and wants it improved or adjusted.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use when the assistant needs to synthesize multiple rough inputs — messy notes, scattered emails, transcript excerpts, meeting context, or uploaded documents — into a concise executive briefing. Especially relevant for founder prep, leadership updates, weekly operating briefs, post-meeting readouts, launch status briefs, partnership updates, hiring or finance summaries, and any situation where conflicting or incomplete inputs must be turned into decision-ready output.
Use when the assistant needs to locate files, inspect folders, summarize drive contents, create or rename folders, move or delete files, manage sharing, detect inherited or external access, clean duplicates, or run organization workflows through connected Google Drive. Connector-first operator for searching, reading, organizing, sharing, auditing, and automating Drive files and folders.
Use when the assistant needs to search, inspect, summarize, create, update, restructure, or maintain Notion pages, databases, tasks, docs, wikis, project trackers, meeting notes, content calendars, or operating systems through the Notion connector. Trigger for requests involving Notion read/write workflows, database updates, page creation, workspace search, status reporting, documentation generation, task management, content planning, or converting messy context into Notion-ready structures.
| name | content-repurposer |
| description | Use when the user wants to repurpose a draft, article, transcript, research dump, or outline into multiple platform-specific outputs across Substack, LinkedIn, Threads, Instagram carousel, and Substack Notes. |
Convert one source into a coordinated set of channel-ready outputs.
Follow this sequence:
Accept any starting material: rough notes, web research, transcripts, long drafts, finished essays, newsletters, outlines, articles, or mixed inputs.
When the source is messy, do not complain. Infer a usable structure by extracting:
When facts are uncertain or unsupported in the source, do not harden them into confident claims. Soften the language or flag the uncertainty.
Use this default voice:
Write with tension and point of view. Avoid bland agreeability. Prefer:
Do not use empty inspiration, corporate filler, or fake urgency.
For every output:
Produce all of these by default in this order:
Use section headings exactly as above unless the user asks for a different format.
Write a complete newsletter version, not just an outline.
Target shape:
Newsletter goals:
Default CTA style:
Write a single post optimized for readability.
Rules:
Preferred structure:
Write as one compact threads post unless the source obviously needs a thread.
Rules:
If a thread is clearly better, use 3-5 short posts.
Create carousel copy for 2 to 6 slides.
Rules:
Use this exact format:
Slide 1: [hook] Slide 2: [point] ... Slide N: [closing insight or minimal CTA]
Write a short note version that feels like a distilled thought, not an ad for the newsletter.
Rules:
Before finalizing, quietly check that:
When useful, also include:
Only include these extras when they improve reuse or the user asks for options.
Use this default structure:
[one sentence]
[full draft]
[full draft]
[full draft]
[2-6 slides]
[full draft]
Do not:
