Individual skill

ad-angle-research

Pull the ads a competitor is running right now on Meta (Facebook/Instagram) and Google, then extract the hooks, offers, CTAs and landing pages worth modelling. Use when writing ad copy, planning creative tests, choosing a landing page angle, or when the user asks "what is X advertising", "what ads does X run", "find competitor ad hooks". Reads live Ad Library and Ads Transparency data through the Tracetify MCP; falls back to a manual Ad Library walkthrough when the connector is absent.

plugins/all-skills/skills/ad-angle-research/SKILL.md

Read pinned source

Source commit 82ce2112b080810c6b72939201d6a53876116e12

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,733
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Ad Angle Research

Turn a competitor's live ads into a short, sourced list of angles the user can test. The output is a creative brief, not a growth story: what they say, to whom, with what offer, where the click lands, and how long each ad has survived.

## Start with the decision

Confirm the competitor domain and what the user is about to make: ad copy, a landing page, a creative test plan, or a positioning check. If the user's own product and audience are unknown, ask once; otherwise state the assumption and continue. Keep competitor facts separate from the user's context throughout.

## Get the ads

**With the Tracetify connector** (tool names may be prefixed, e.g. `mcp__tracetify__research_competitor_ads`):

1. **Ask before the paid lookup.** A fresh `research_competitor_ads` lookup costs 3 Tracetify credits; the same domain re-queried within a week is free. Before the call, including the first one in a session, tell the user the domain and that price, and wait for an explicit yes. A request to research the competitor is not that yes. If they decline, continue with the manual route below. Do not call it repeatedly for the same domain in one session.
2. Read the response as two independent sources. `meta` and `google` are each an array (checked), an empty array (checked, nothing running) or `null` (could not be checked). Never describe a `null` source as "no ads".