write-hooks-from-ads
Skill0 starsChanged 27 days agoMITView on GitHub
Read winning ads in the AdSwipeFile ad library, name the hook and angle each one uses, and write original hooks, headlines or ad copy for the user's product in those patterns. Use for "write hooks for my product", "give me angles from ads that are working", "what hook does this ad use", or ad copy inspired by real ads.
In this repository14 other files it gives its agents.
- audit-ad-creativeSkill
- competitor-adsSkill
- creative-strategySkill
- find-winning-adsSkill
- generate-ad-conceptsSkill
- get-startedSkill
- map-competitorsSkill
- map-personasSkill
- pick-creative-mechanicSkill
- record-creative-learningSkill
- review-saved-adsSkill
- teach-ad-breakdownSkill
- track-competitor-adsSkill
- weekly-competitor-reviewSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Read four to six of them with get_ads when the hooks need the full copy.
- Very specific: line 28
When the user wants the ad in a given visual format, call get_format with its slug once: build from its how_to_build, and check each …
- Very specific: line 33
If get_ads returns an ad without its copy, with a line saying so, pass that line on once.
- Distinctive: line 43
Write new sentences: never reuse an ad's wording, brand names, slogans or testimonials.
- Distinctive: line 45
Use only claims the user gave you.
- Distinctive: line 48
Keep each hook to one line unless the user asked for longer copy.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Write hooks from real ads
Needs the AdSwipeFile connector. This skill reads the AdSwipeFile ad library of Meta ads through its MCP server. If no AdSwipeFile tools (
search_library,list_ads) are available, say so before anything else and give the step for this host. Claude Code:claude mcp add --transport http adswipefile https://adswipefile.com/api/mcp. claude.ai or ChatGPT: addhttps://adswipefile.com/api/mcpas a custom connector. Other clients: https://adswipefile.com/docs/mcp?utm_source=agent-skill&utm_medium=referral&utm_campaign=write-hooks-from-ads. Connecting opens a sign-in to an AdSwipeFile account. Steps that need only the user's own material can go on; never invent ads, brands or links in place of the library.
Gather
- Learn the user's product, audience and the claim they can back. Ask only if the request does not say what the product is.
- Find relevant ads:
list_hooksonce for the hook tactics, thenlist_adswith the product'sniche(resolved as in find-winning-ads), thehooktactic the user wants (or two or three that fit the product when they name none), andsort: "longest_running". Addawarenesswhen the user knows how cold the audience is. Each ad carries itshook_tacticandhook_line, so the list often gives the openings already. - Read four to six of them with
get_adswhen the hooks need the full copy. - When the user wants the ad in a given visual format, call
get_formatwith its slug once: build from itshow_to_build, and check each concept against itshow_to_tell(must_be,quick_test) so it is that format and not one it isconfused_with.
If get_ads returns an ad without its copy, with a line saying so, pass that
line on once. Work from the ads' names, descriptions and formats, and say the hooks
are drawn from those rather than from the full copy.
Write
- First name the pattern each source ad uses (its
hook_tactic, in plain words: a question about a pain, a specific number, a before and after, a customer's words, a myth corrected), each with a link to the ad. - Then write the hooks or copy for the user's product in those patterns. Write new sentences: never reuse an ad's wording, brand names, slogans or testimonials.
- Use only claims the user gave you. Mark any figure, result or guarantee you had to assume as a placeholder for the user to confirm, such as "[X] customers".
- Keep each hook to one line unless the user asked for longer copy.
Keep the sources
Offer, once, to put the source ads on a hooks board (create_board or one
from list_boards, then add_ad_to_board) with a set_ad_note naming the
pattern each one gave, so the next round of hooks starts from them. Only on a
yes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

