Content Creator Pro
LeoYeAI/openclaw-master-skills
Autonomous content creation engine for agents. An agent skill from LeoYeAI/openclaw-master-skills.
Writes opening hooks and post titles for long-form articles in EN or FR — blog posts, Substack/Medium/dev.to, LinkedIn long-form, newsletters, essays.
$ npx skills add samber/cc-skills --skill copywriting-hooks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install samber/cc-skills copywriting-hooks --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/samber/cc-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/copywriting-hooks .claude/skills/copywriting-hooks && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "copywriting-hooks" agent skill from https://github.com/samber/cc-skills/tree/main/skills/copywriting-hooks into .claude/skills/copywriting-hooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-hooks", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/samber/cc-skills/tree/main/skills/copywriting-hooksType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add samber/cc-skills --skill copywriting-hooks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install samber/cc-skills copywriting-hooks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samber/cc-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/copywriting-hooks .agents/skills/copywriting-hooks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "copywriting-hooks" agent skill from https://github.com/samber/cc-skills/tree/main/skills/copywriting-hooks into .agents/skills/copywriting-hooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-hooks", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add samber/cc-skills --skill copywriting-hooks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install samber/cc-skills copywriting-hooks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samber/cc-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/copywriting-hooks .cursor/skills/copywriting-hooks && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "copywriting-hooks" agent skill from https://github.com/samber/cc-skills/tree/main/skills/copywriting-hooks into .cursor/skills/copywriting-hooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-hooks", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/samber/cc-skills.git --path skills/copywriting-hooks--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add samber/cc-skills --skill copywriting-hooks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install samber/cc-skills copywriting-hooks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samber/cc-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/copywriting-hooks .gemini/skills/copywriting-hooks && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "copywriting-hooks" agent skill from https://github.com/samber/cc-skills/tree/main/skills/copywriting-hooks into .gemini/skills/copywriting-hooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-hooks", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install samber/cc-skills copywriting-hooksInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add samber/cc-skills --skill copywriting-hooks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/samber/cc-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/copywriting-hooks .github/skills/copywriting-hooks && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "copywriting-hooks" agent skill from https://github.com/samber/cc-skills/tree/main/skills/copywriting-hooks into .github/skills/copywriting-hooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-hooks", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add samber/cc-skills --skill copywriting-hooks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install samber/cc-skills copywriting-hooks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samber/cc-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/copywriting-hooks .opencode/skills/copywriting-hooks && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "copywriting-hooks" agent skill from https://github.com/samber/cc-skills/tree/main/skills/copywriting-hooks into .opencode/skills/copywriting-hooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "copywriting-hooks", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
copywriting-hooksWrites opening hooks and post titles for long-form articles in EN or FR — blog posts, Substack/Medium/dev.to, LinkedIn long-form, newsletters, essays.
Copywriting Hooks is an agent skill from samber/cc-skills. Writes opening hooks and post titles for long-form articles in EN or FR — blog posts, Substack/Medium/dev.to, LinkedIn long-form, newsletters, essays. Trigger whenever the user asks for a hook, opening, lede, intro, first sentence/paragraph, opener, accroche, attaque, phrase d'accroche, or première phrase — including punching up a flat intro or draft opening — or for a post title, titre d'article, or headline. Do NOT trigger for social posts (LinkedIn feed, Twitter/X, TikTok, Bluesky), READMEs, taglines, email…
Its SKILL.md is about 6.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/anglophone-vs-francophone.md`, `references/anti-patterns.md` and `references/formulas.md`). Compatibility notes: Designed for Claude Code, Codex or similar harness.
It sits in Writing & Content, covering Copywriting, Blog and article writing and Newsletters. It works with LinkedIn, Bluesky, Substack and TikTok. The repository describes itself as: 🧑🎨 A collection of agentic skills that works. The licence is MIT.
12 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 123cb15. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadEditWriteGlobGrepAgentAskUserQuestionFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code, Codex or similar harness.
From compatibility in the SKILL.md frontmatter.
Copywriting Hooks loads about 6.8k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 176 tokens; SKILL.md has 3,687 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from samber/cc-skills at commit 123cb15, republished under its MIT licence (© samber). 3,687 words, ~6,804 tokens.
.claude/skills/copywriting-hooks/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.A hook's only job is to make the reader want sentence 2. Voice, structure, formatting, all of it, follow from that one job.
What makes a reader want sentence 2 is one of five levers:
A strong hook usually pulls two levers at once. "Frank Sinatra, holding a glass of bourbon..." is scene plus open loop. "Most people think X. They're wrong." is prediction-break plus gap. Single-lever hooks can still work but are easier to ignore.
Three further principles:
When this skill triggers:
Diversification rule. Across your 3 to 4 options include at minimum:
This guarantees real choice. Three flavors of contrarian is not a choice.
Type-fit reference:
| Article type | Strong hooks | Avoid |
|---|---|---|
| Technical deep-dive | concrete detail, statistic, contrarian, direct problem | personal confession, scene opener |
| Personal essay | in medias res, personal confession, time anchor, definition reversal | bold claim, direct problem |
| Opinion / contrarian | bold claim, definition reversal, contrarian, quote + disagreement | gentle setup, dictionary opener |
| Tutorial / how-to | direct problem (PAS), promise, conditional | scene opener, historical analogy |
| Reported / investigative | concrete detail, time anchor, in medias res, statistic | bold claim, definition reversal |
| Listicle | curiosity gap, counted stakes, conditional | personal confession, in medias res |
| Longform analysis | historical analogy, statistic, contrarian | direct problem |
| Newsletter issue | personal confession + open loop, conditional, curiosity gap | dictionary opener |
Always present options exactly like this:
## Hook options for: [working title]
**Option 1: [Hook name]** ([lever])
A. [Candidate 1]
B. [Candidate 2]
**Option 2: [Hook name]** ([lever])
A. [Candidate 1]
B. [Candidate 2]
**Option 3: [Hook name]** ([lever])
A. [Candidate 1]
B. [Candidate 2]
Which? Reply with letter combination (e.g., "1B") or "more" for different techniques.If the user says "more" or "none", produce 3 different hooks (not new candidates for the same hooks). If the user says "blend 1A and 2B", write a combined hook and check in again.
Each hook: what it does, examples (mix EN and FR, real and illustrative), when to use, when to avoid.
Open an information gap the reader wants closed.
Use when: you can honestly close the gap in 2 or 3 sentences. The gap must be one the reader cares about. Avoid: vague gaps ("You won't believe what happened next") that the reader cannot even guess at.
Knock down a consensus belief the reader holds.
Use when: you have a defensible non-consensus view and 200 to 400 words to defend it. Avoid: strawmen, gratuitous edginess, contrarianism for its own sake.
State the outcome upfront, before the proof.
Use when: you can deliver on the promise concretely in the article. Avoid: promises larger than the payoff. Destroys trust permanently.
Drop the reader inside a specific moment, no setup.
Use when: longform, profile, reported piece, essay. Avoid: short technical pieces where the reader has not earned the scene yet.
Lead with a number that violates the prior.
Use when: the number is genuinely surprising and you can cite it accurately. Avoid: vague stats ("studies show 90%..."), stats that confirm the reader's prior (no surprise equals no hook).
Pose a question the reader actually wants answered.
Use when: the reader was implicitly carrying the question. Avoid: "Have you ever wondered...?", "Did you know...?", "What if I told you...?". These presuppose curiosity not yet formed.
Borrow weight, then twist.
Use when: you have a real quote that supports or genuinely contrasts your point. Avoid: misattributed Einstein, Seneca, Confucius, Bouddha platitudes. Cliché.
Admit something vulnerable, then universalize.
Use when: personal byline, essay, newsletter. Avoid: corporate byline, technical articles where the author voice is not personal, performative vulnerability ("I almost didn't write this...").
Replace abstraction with a single vivid detail.
Use when: profile, reported piece, contrarian biographical setup. Avoid: specificity that does not advance the thesis (clutter).
Break expected rhythm with a fragment.
Use when: rhythm-driven content, opinion piece, when the reader expects flow and you want to interrupt it. Avoid: every article. It becomes its own pattern fast.
Name the pain, sharpen it, hint at solution.
Use when: tutorial, how-to, sales-adjacent content. Avoid: manufactured problems. Reads as fear-mongering. The pain must be real and recognizable.
State a specific, bounded outcome.
Use when: tutorial, how-to. Avoid: vague promises ("Learn how to be more productive"). Add a time bound or a number to anchor it.
Open with a vignette from history, pivot to the present.
Use when: longform analysis, opinion piece, idea essay. Avoid: tutorials, news pieces. Reads as indulgent.
"X is not what you think. It's Y."
Use when: opinion piece, contrarian deep dive. Avoid: when your reframe is just a slight angle. Sounds gimmicky.
Lead with a name plus a specific action.
Use when: business piece, profile, analytical essay. Avoid: name-dropping without payoff. The action must be specific and relevant.
Lead with a specific date, hour, or moment.
Use when: reported piece, retrospective, "why now" framing. Avoid: vague time anchors ("recently", "these past few years"). Use a specific date or cut the time framing.
Self-segment the reader. Pre-target the curiosity.
Use when: tutorial, advice piece, segmented audience. Avoid: conditions too broad ("If you've ever felt stuck..."). Segments nobody.
Start something, withhold the resolution.
Use when: longform, pieces where the journey matters as much as the answer. Avoid: unresolved loops. Creates disproportionate betrayal when the article ends without paying off.
Cliché openers that immediately disqualify the writer:
Current AI tells (refresh yearly):
Run every candidate through this list before presenting. If a candidate matches, rewrite.
For the extended anti-pattern list, see references/anti-patterns.md.
If the audience is French: write in French, applying the attaque journalistique register.
If English: default to direct-response register for marketing or tutorial content, longform register for essays and reported pieces.
If bilingual: produce hooks in both languages, label clearly.
For deeper register guidance, see references/anglophone-vs-francophone.md.
A title is what the reader sees before clicking. A hook is what they read after. Both earn attention through different mechanisms: the title competes for clicks in a feed or search result; the hook earns continued reading after the click.
A title must open a gap without closing it — but the gap must feel real, not manufactured. Research on 8,977 A/B experiments (Upworthy, Scientific Reports 2024) found a curvilinear relationship: too vague produces confusion (no foothold for curiosity); too specific removes motivation to click. The sweet spot: name the stakes, withhold the resolution.
The craft test. Does the title open a gap the reader cares about, and does the article genuinely close it? If yes, that's craft. If the content doesn't deliver what the title implied, that's clickbait — it destroys trust for future clicks.
Curiosity / Gap
The [Adjective] Truth About [Topic] — "The Counterintuitive Truth About Go Generics"What [Group] Won't Tell You About [Topic]The Real Reason [Phenomenon] — "The Real Reason Most Content Gets Zero Shares"[Number] Things Every [Audience] Gets Wrong About [Topic]Contrarian / Negative (negative superlatives: +63% CTR vs. positive — Outbrain, 65k titles)
Stop [Doing X]. Here's Why. / Why [Common Belief] Is Wrong[Number] [Myths/Mistakes] That Are Killing Your [Result]Specificity / Data
I Analyzed [Number] [Things] — Here's What I Found[Number]% of [Group] Does This WrongHow I Cut Build Time by 60% [Benchmark]List / Number (numbers: +36% CTR — Conductor; odd numbers: +20% CTR — CMI)
[Number] [Adjective] Ways to [Goal] / [Number] Mistakes to Avoid When [Task]How-To (3× more B2B shares than other formats — BuzzSumo, 10M LinkedIn articles)
How to [Task] Without [Painful Constraint] / How to [Task] Even If [Limiting Belief]Slightly clickbait but honest — maximum tension with a real promise:
[Étude], [Template], [Benchmark] to signal payoff typeFR — putaclic carries stronger pejorative weight. Apply the 70/30 rule: 70% information, 30% mystery.
| Platform | Max display | Key rule |
|---|---|---|
| Blog / SEO | 50–60 chars | Front-load keyword. Power words reduce CTR by ~14% in search. |
| LinkedIn article | 150 chars hard | Under 100 for clean display. |
| LinkedIn feed | 120–140 chars | Opening line = the title. Engineer a "see more" click. |
| Newsletter subject | 30–50 chars | First 30 chars carry the signal. Avoid "Newsletter" (−18.7% opens). |
| X / Twitter | ≤200 chars | First tweet = the title. Must stand alone. |
For the full 58-formula catalog (EN + FR) with data citations, see references/title-formulas.md.
references/anti-patterns.md: extended cliché and AI-tell list.references/anglophone-vs-francophone.md: register conventions, what does not translate.references/formulas.md: 30 reusable templates (EN + FR) for quick template-based hooks.references/title-formulas.md: 58-formula post title catalog (EN + FR), platform constraints table, data summary.The catalog above is sufficient for most invocations. Load references only when the user asks for templates, deeper register guidance, or to sanity-check anti-patterns.
If invoked from inside another skill's workflow (e.g., technical-article-writer reaches the hook step), produce options, ask, wait. Return the chosen hook to the parent skill for the rest of the article.
If the user has already drafted an opening and asks for "a better one", treat that draft as Option 0 (their current version) and propose 3 alternatives across different hooks. Do not silently discard their version.
User: "I'm writing a Substack piece on why most Go developers misuse generics. About 1500 words, intermediate Go devs, English."
Correct skill response:
## Hook options for: "Why Most Go Developers Misuse Generics"
**Option 1: Contrarian** (prediction-break)
A. Most articles on Go generics explain when to use them. This one explains when to delete them.
B. Generics were the most requested Go feature for a decade. Three years in, the people who pushed hardest for them are the ones telling you to stop using them.
**Option 2: Concrete detail** (sensory + specific)
A. samber/lo ships 87 generic helpers. Six of them account for 94 percent of the binary-size complaints. The other 81 are fine.
B. A function called `Map[T, U any]` looks innocent. Compile a project that imports it 40 times and your build time triples. Here is why.
**Option 3: Direct problem (PAS)** (reader-direct)
A. Your Go code compiles slower since you adopted generics. The cause is not what the linter is telling you.
B. If your team adopted generics last year and your build times doubled, you are not alone. The diagnosis is more boring than the fix.
Which? Reply with letter combination (e.g., "1B") or "more" for different techniques.Then wait for the pick. Do not write the rest of the article until the user has chosen.
© samber, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in skills/copywriting-hooks of samber/cc-skills.
Open the folder on GitHubat commit 123cb15
Copywriting Hooks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Copywriting Hooks this skillsamber/cc-skills | 228 | — | ~6.8k | Automated safety check: Pass | MIT | |
| Content Creator ProLeoYeAI/openclaw-master-skills | 2.2k | — | ~7.2k | Automated safety check: Pass | MIT | |
| DropspaceLeoYeAI/openclaw-master-skills | 2.2k | — | ~6.2k | Automated safety check: Pass | MIT | |
| Social Media Pro Maxcriptogus/agent-evolve-network | 288 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Content Remix StudioLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.5k | Automated safety check: Pass | MIT | |
| Content Writer Agentmastra-ai/mastra | 29k | — | ~1.3k | Automated safety check: Pass | Custom licence |
LeoYeAI/openclaw-master-skills
Autonomous content creation engine for agents. An agent skill from LeoYeAI/openclaw-master-skills.
LeoYeAI/openclaw-master-skills
Create and publish social media launches via the Dropspace API.
criptogus/agent-evolve-network
State-of-the-art viral content + social design intelligence.
LeoYeAI/openclaw-master-skills
Transform one piece of content into platform-optimized versions for YouTube, TikTok, Twitter/X, LinkedIn, Instagram, newsletters, and blogs.
mastra-ai/mastra
Authoring playbook for building agents that draft written content — blog posts, marketing copy, social media posts, newsletters, product descriptions, landing pages, or ad copy.
ScrapeCreators/social-media-research-skills
A skill your agent uses when the user wants to find posts, videos, reels, shorts, tweets, or social content that overperformed versus a creator, brand, or competitor baseline.
samber/cc-skills
Interviews you about objective, audience and context, then designs an end-of-article call to action with copy, placement, A/B test plan and accessibility check.
samber/cc-skills
Builds a PROSE.md writing guide that captures how a person or brand writes, such as vocabulary, sentence rhythm and signature moves, separate from emotional tone.
samber/cc-skills
Drafts press releases that fit the release type, target media and region, after collecting the facts and checking that the story has a real news angle.
samber/cc-skills
Produces a training or workshop report as a Word file, with participant feedback and recommendations, drafted in Markdown first and converted once at the end.
samber/cc-skills
Pre-launch checklist for shipping a new website or web app. An agent skill from samber/cc-skills.
samber/cc-skills
Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects.
Works with
Categories
Writes opening hooks and post titles for long-form articles in EN or FR — blog posts, Substack/Medium/dev.to, LinkedIn long-form, newsletters, essays. Copywriting Hooks is an agent skill from samber/cc-skills.to, LinkedIn long-form, newsletters, essays.
Copywriting Hooks fits situations like: ever the user asks for a hook; first sentence/paragraph; phrase daccroche; première phrase — including punching up a flat intro.
Run `npx skills add samber/cc-skills --skill copywriting-hooks -a claude-code`. Or copy the skill folder (skills/copywriting-hooks in samber/cc-skills) into .claude/skills/copywriting-hooks in your project. Claude Code loads it when a task matches its description.
Run `npx skills add samber/cc-skills --skill copywriting-hooks -a codex`. Or copy the skill folder (skills/copywriting-hooks in samber/cc-skills) into .agents/skills/copywriting-hooks in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add samber/cc-skills --skill copywriting-hooks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/copywriting-hooks, .gemini/skills/copywriting-hooks, .github/skills/copywriting-hooks and .opencode/skills/copywriting-hooks in your project.
SKILL.md names no scripts, command-line tools or credentials: Copywriting Hooks is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Edit, Write, Glob, Grep, Agent, AskUserQuestion. Compatibility (from SKILL.md): Designed for Claude Code, Codex or similar harness..
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Copywriting Hooks is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.8k tokens (SKILL.md is roughly 27k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.6k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Copywriting Hooks: Content Creator Pro (LeoYeAI/openclaw-master-skills, 2.2k stars), Dropspace (LeoYeAI/openclaw-master-skills, 2.2k stars), Social Media Pro Max (criptogus/agent-evolve-network, 288 stars) and Content Remix Studio (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
samber (a GitHub user) maintains it in samber/cc-skills, which has 228 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 1, 2026.
Source: samber/cc-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.