When the user wants to run paid ads within directories or marketplaces. Also use when the user mentions "Taaft ads," "Shopify App Store ads," "G2 sponsored," "Capterra ads," "directory ads," "marketplace ads," "paid listing," "sponsored listing," or "directory promotion." For organic listings, use directory-submission.
Guides paid promotions within directories and marketplaces: Taaft, Shopify App Store, G2, Capterra. Use when you have a listing and want to boost visibility with paid placements. Listing first: Ensure product is submitted—see directory-submission for listing prep and submission workflow.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
| Platform | Ad type | Model | Best for | |----------|---------|-------|----------| | Taaft | Banners, sponsored listings, campaigns | Paid placements; listing + newsletter + ads + social bundles | AI tools; 80M+ users; 46K+ tools | | Shopify App Store | Search ads, homepage ads, category ads | CPC; daily budget | Shopify app developers; merchant discovery | | G2 | Paid Promotions, G2 Clicks | Quarterly or PPC | B2B SaaS; category/competitor pages | | Capterra | Sponsored listings | PPC | B2B software; 50M+ annual visitors |
utm_source=taaft_feat&utm_medium=referral for PPC adsutm_medium=paid, utm_source=taaft or shopify or g2 or capterra)Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/directory-listing-ads · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/directory-listing-ads"
cp -r "skills/paid-ads/formats/directory-listing-ads" ".claude/skills/directory-listing-ads"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.