Reel CTA Writer
CTA Writer — one ask, matched to the reel

Writes the end-of-reel call to action that drives the exact next step — follow, DM a keyword, save, or click. Use when the user says "write my CTA", "how should I end this reel", "what should the call to action be", "keyword CTA".
--- name: cta-writer description: > Writes the end-of-reel call to action that drives the exact next step — follow, DM a keyword, save, or click. Use when the user says "write my CTA", "how should I end this reel", "what should the call to action be", "keyword CTA". user-invokable: true argument-hint: "[the reel, and what you want them to do]" license: MIT metadata: author: Ootto version: "1.0.0" category: content --- # CTA Writer — one ask, matched to the reel Writes the end-of-reel call to action that drives the exact next step — follow, DM a keyword,
Overview
Writes the end-of-reel call to action that drives the exact next step — follow, DM a keyword, save, or click.
Manual install (npx, ZIP)
npx skills add Ootto-AI/claude-content-skills --skill cta-writer -g -a claude-codenpx degit Ootto-AI/claude-content-skills/skills/cta-writer#main ~/.claude/skills/cta-writerConnects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md1.8 KB
Read SKILL.md here
Show the full text50 lines
CTA Writer — one ask, matched to the reel
Writes the end-of-reel call to action that drives the exact next step — follow, DM a keyword, save, or click.
When to use
The reel works but the ending fizzles.
What you'll need
The reel or script, and the one next step you want.
Instructions
Give Claude the input and run this.
You are my CTA writer. Reel: [paste]. I want: [follow / DM keyword / save / click].
1. ONE ASK: if I named more than one, pick the best for this reel and tell me why the other is dropped.
2. THE REASON LINE: the sentence before the ask — why they should. This does more work than the ask.
3. THE ASK: the exact words, spoken and on-screen.
4. KEYWORD (if DM): a word that's easy to spell, hard to autocorrect, and not one I've used recently.
5. PLACEMENT: where in the reel, and whether it belongs in the caption instead.
6. DELIVERY CHECK: state exactly what I must have ready to send. If I can't deliver it, say don't run this CTA.
Honesty: Only promise what actually exists and actually sends. An unwired keyword burns the trust of everyone who comments.
Next: dm-script-writer → comment-responder
Built by Ootto — the AI autopilot that connects your tools once and runs the busywork for you, automatically. Book a demo →
| 1 | |
| 2 | name cta-writer |
| 3 | description > |
| 4 | Writes the end-of-reel call to action that drives the exact next step — follow, DM a keyword, |
| 5 | save, or click. |
| 6 | Use when the user says "write my CTA", "how should I end this reel", "what should the call to action be", "keyword CTA". |
| 7 | user-invokable true |
| 8 | argument-hint "[the reel, and what you want them to do]" |
| 9 | license MIT |
| 10 | metadata |
| 11 | author Ootto |
| 12 | version "1.0.0" |
| 13 | category content |
| 14 | |
| 15 | |
| 16 | # CTA Writer — one ask, matched to the reel |
| 17 | |
| 18 | Writes the end-of-reel call to action that drives the exact next step — follow, DM a keyword, |
| 19 | save, or click. |
| 20 | |
| 21 | |
| 22 | ## When to use |
| 23 | The reel works but the ending fizzles. |
| 24 | |
| 25 | ## What you'll need |
| 26 | The reel or script, and the one next step you want. |
| 27 | |
| 28 | ## Instructions |
| 29 | Give Claude the input and run this. |
| 30 | |
| 31 | |
| 32 | You are my CTA writer. Reel: [paste]. I want: [follow / DM keyword / save / click]. |
| 33 | |
| 34 | 1. ONE ASK: if I named more than one, pick the best for this reel and tell me why the other is dropped. |
| 35 | 2. THE REASON LINE: the sentence before the ask — why they should. This does more work than the ask. |
| 36 | 3. THE ASK: the exact words, spoken and on-screen. |
| 37 | 4. KEYWORD (if DM): a word that's easy to spell, hard to autocorrect, and not one I've used recently. |
| 38 | 5. PLACEMENT: where in the reel, and whether it belongs in the caption instead. |
| 39 | 6. DELIVERY CHECK: state exactly what I must have ready to send. If I can't deliver it, say don't run this CTA. |
| 40 | |
| 41 | |
| 42 | **Honesty:** Only promise what actually exists and actually sends. An unwired keyword burns the trust of |
| 43 | everyone who comments. |
| 44 | |
| 45 | **Next:** [dm-script-writer] → [comment-responder] |
| 46 | |
| 47 | |
| 48 | |
| 49 | Built by **[Ootto]** — the AI autopilot that connects your tools once and runs the busywork for you, automatically. [Book a demo →] |
| 50 |
Details
- License
- MIT
- Stars on the repo
- ★ 139
- Checked
- Source
- Ootto-AI/claude-content-skills ↗
- Creator
- Ootto-AI · 36 listings
Similar skills
See all →
SkillCross-Platform Reverse Engineer
SkillBrainstorm Ideas
SkillCode Review Feedback Analyzer
SkillBug Diagnosis Framework
SkillImplement Spec
SkillPR Description WriterMore from Ootto-AI
SkillHook Variant A/B Generator
SkillInternet Research Router
SkillObsidian Long-Term Memory
SkillAnalytics Readout Translator
SkillSocial Audience Personas
SkillSocial Profile Converter