plugins/copywriting/skills/copywriting-orchestrator/SKILL.md
Detects content type and routes to the right specialized copywriting skill (ig-orchestrator, email-orchestrator, video-scripting, web-copy, product-copy, storytelling). Use when the user asks for copy but it is unclear which specialist to use, or for multi-channel campaigns spanning several formats. Trigger phrases - "write copy for", "help me with copywriting", "product launch campaign", "I need marketing text", "make it more compelling", "tell a story", "video script", "VSL", "email sequence", "drip campaign". Do NOT use when you already know the exact medium — call the specialist skill directly instead.
npx skillsauth add petrogurcak/skills copywriting-orchestratorInstall 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.
This skill orchestrates copywriting work by detecting content type and calling the appropriate specialized skill. It does NOT implement copywriting itself - it routes to specialists.
Philosophy:
Orchestrator = Conductor
Specialized Skills = Musicians
The conductor doesn't play instruments, but coordinates who plays when.
Announce: "I'm using copywriting-orchestrator to determine the right copywriting approach."
USE this skill:
DON'T use this skill:
| Keywords in Request | Detected Type | Specialist Skill |
| ------------------------------------------------------------------------------------------------ | ------------------- | ----------------------------------------------------------- |
| instagram, ig, reel, stories, post, carousel, social media | IG (any sub-intent) | ig-orchestrator → routes to ig-* |
| napiš IG post, caption, Reel caption, IG copy (writing intent) | IG Writing | ig-content (direct, skip orchestrator) |
| IG strategie, co točit, formát Reelu, engagement plán (planning) | IG Strategy | ig-strategy (direct, skip orchestrator) |
| homepage, web, landing, about us, sales page, website | Web Copy | web-copy |
| produkt, e-shop, product description, e-commerce, popis | Product Copy | product-copy |
| email, newsletter, mailing, campaign, sequence, drip | Email (any) | email-orchestrator → routes to newsletter/email-sequences |
| single email, weekly newsletter, holiday email, kampaň | Email (one-off) | newsletter (direct, skip orchestrator) |
| 5-day sequence, welcome series, drip campaign, tripwire, SOS, indoktrinační sekvence | Email (sequence) | email-sequences (direct) |
| video script, YouTube, VSL, course video, explainer video, scénář videa | Video Scripting | video-scripting |
| story, narrative, compelling, pitch deck, founder story | Storytelling | storytelling |
If keywords unclear, check context:
Is it for social media platform?
├─ YES → instagram-content
│
Is it for a website page?
├─ YES → web-copy
│
Is it describing a product for sale?
├─ YES → product-copy
│
Is it sent to inbox?
├─ YES → newsletter
│
Still unclear?
└─ ASK user (see Step 3)
I need to know what type of copy you're creating:
A) Instagram/Social Media (Reels, Stories, posts)
B) Website (homepage, landing page, about us)
C) Product Description (e-shop, e-commerce)
D) Email/Newsletter (campaigns, sequences)
E) Multi-channel campaign (combination)
copywriting-orchestrator
│
├── ig-orchestrator (IG family router)
│ ├── ig-content — writing (Otto methodology, strict output discipline)
│ ├── ig-strategy — planning (formats, production, engagement, monetizace)
│ └── (future) ig-reels, ig-stories, ig-carousel, ig-ads, ig-analytics
│
├── web-copy
│ └── Blueprint, Triáda, PROTTO, homepage elements
│
├── product-copy
│ └── 7-step framework, Type A/B products
│
├── email-orchestrator (Email family router)
│ ├── newsletter — one-off emails, weekly broadcasts, campaigns
│ ├── email-sequences — multi-day SOS, drip, tripwire, post-purchase
│ └── (future) cold-outreach, partnership-emails
│
├── video-scripting
│ └── Snyder 15-Beat + Heath SUCCESs + retention layer (YouTube, VSL, course)
│
├── storytelling
│ └── ABT, SB7, Strategic Narrative, Sparkline, SUCCESs, 9 SM frameworks
│
├── brand-voice
│ └── Voice attributes, tone adaptation, terminology
│
├── writing-clearly-and-concisely
│ └── Strunk's Elements of Style applied
│
└── knowledge-book
└── Non-fiction knowledge book writing
../core-copywriting-principles.md — Otto Bohuš universal principles (banned words, triáda, <20 word sentences, psychological triggers)../365-copy-triky.md — 365 micro-tipů (Mužíková) — hooks, CTAs, anti-clichés reference bank../core-briefing-process.md — 8 otázek (CO, JAK, ČÍM, KDE, KOMU, KDO, KAM, PROČ)Detect content type using keywords and context (see above).
Before calling specialist, ensure briefing is complete:
Quick Brief (minimum 4 questions):
If briefing incomplete → prompt user for answers before proceeding.
Invoke appropriate skill:
"Using instagram-content for Instagram Reel creation."
The specialist skill handles its own workflow (TDD, checklists, quality controls).
After specialist completes, verify against Core Copywriting Principles:
☐ Headline bez tečky?
☐ Max 3 řádky na odstavec?
☐ Konkrétní čísla místo obecných tvrzení?
☐ Žádné zakázané klišé? (vysoká kvalita, flexibilní, komplexní...)
☐ Jasné CTA?
When request involves multiple channels:
User: "Chystám launch nového produktu"
Orchestrator detects: Multi-channel campaign
Recommended sequence:
1. product-copy → produktová stránka
2. newsletter → launch email sekvence
3. instagram-content → promo Reels/Stories
Execution: Call each skill in sequence OR parallel
User: "Potřebujeme přepsat celý web"
Orchestrator detects: Web copy (multiple pages)
web-copy handles:
- Homepage (9 prvků)
- About Us
- Landing pages
- Blog structure
digraph copywriting_flow {
"Request arrives" [shape=doublecircle];
"Detect content type" [shape=box];
"Type clear?" [shape=diamond];
"Ask user" [shape=box];
"Briefing complete?" [shape=diamond];
"Prompt for brief" [shape=box];
"Call specialist skill" [shape=box];
"Quality gate check" [shape=box];
"Done" [shape=doublecircle];
"Request arrives" -> "Detect content type";
"Detect content type" -> "Type clear?";
"Type clear?" -> "Ask user" [label="no"];
"Type clear?" -> "Briefing complete?" [label="yes"];
"Ask user" -> "Briefing complete?";
"Briefing complete?" -> "Prompt for brief" [label="no"];
"Briefing complete?" -> "Call specialist skill" [label="yes"];
"Prompt for brief" -> "Call specialist skill";
"Call specialist skill" -> "Quality gate check";
"Quality gate check" -> "Done";
}
| Content Type | Specialist Skill | Core Framework |
| ------------------------ | -------------------- | --------------------------------------------- |
| Instagram (any) | ig-orchestrator | Routes to ig-content / ig-strategy |
| IG copy/captions | ig-content | Otto methodology, 3-5 variants, strict output |
| IG planning/production | ig-strategy | 4 idea criteria, 9 formats, technical setup |
| Website/Landing | web-copy | Blueprint, Triáda, PROTTO |
| E-shop Products | product-copy | 7-step, Type A/B |
| Email (any/unclear) | email-orchestrator | Routes to newsletter / email-sequences |
| Email (one-off) | newsletter | 9-step anatomy, subject lines |
| Email (sequence) | email-sequences | 5-day SOS, Schwartz awareness, Hormozi offers |
| Video script (long-form) | video-scripting | Snyder 15-Beat, Heath SUCCESs, VSL canon |
| Story/Narrative | storytelling | ABT, SB7, Sparkline, 9 SM frameworks |
❌ Bypassing briefing: "Let me just start writing..." → STOP. Brief first.
❌ Using wrong specialist:
Product description on landing page → web-copy (sales page section), NOT product-copy
❌ Ignoring quality gate: Specialist done ≠ copy done. Always verify Core Principles.
❌ Not detecting multi-channel: "Launch campaign" = multiple skills, not just one.
From specialists back to orchestrator: If specialist needs input from another (e.g., UVP for web copy), orchestrator coordinates:
uvp-optimization → define positioningweb-copy → write homepage with UVPCross-skill knowledge:
development
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
development
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).