Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 30571–30600 of 36007 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| tiktok-ads-creative-fatigue-and-refresh-cadencecoupler-io/skillsUse for "is my TikTok creative burning out", "my hook rate is dropping", "my CPMs keep rising", "how long before I need new videos", "which ads should I refresh", "how much new creative do I need a month", "how many videos should we shoot", or "this video used to work" — even when the user never says "fatigue". This is the how-long-has-it-left read and the production-cadence number; for which videos win in the first place, use the creative analysis skill. TikTok Ads only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| tiktok-ads-creative-performance-analysiscoupler-io/skillsUse for "which creative is working on TikTok", "which videos should I put money behind", "what should the next round of creative look like", "is my hook working", "which video is holding attention", "why do people scroll past my ad", or "what do my winners have in common" — even when the user never says "creative". This is the which-videos-win read; for which winning videos are dying, use the fatigue skill instead. TikTok Ads only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| tiktok-ads-performance-reportcoupler-io/skillsUse for "how are my TikTok ads doing", "why did my cost per result go up", "what changed on TikTok this month", "which campaigns improved", "my CPMs are climbing", "my video views dropped", or a weekly or monthly account check — even when the user never says "review". Also use when someone wants the baseline read before deciding anything else in the account. TikTok Ads only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| tiktok-ads-placement-location-and-device-breakdowncoupler-io/skillsUse for "is Pangle wasting my money", "should I turn off automatic placement", "how is Search Feed doing", "which countries are working on TikTok", "is iOS or Android converting", "what time of day should I be running", or "where is my budget actually going" — even when the user never says "placement". Covers where and when the ads are shown, and what each of those is worth. TikTok Ads only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| tiktok-ads-wasted-spend-and-scalingcoupler-io/skillsUse for "where am I wasting money on TikTok", "which ad groups should I pause", "what should I turn off", "which campaigns should I scale", "clean up my TikTok account", "find me negative keywords for Search Ads", or "what do I cut and where does the money go" — even without the words "waste" or "scale". Also use when someone wants a budget-neutral reallocation proposal for the account. TikTok Ads only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| tiktok-shop-and-gmv-max-reviewcoupler-io/skillsUse for "how is GMV Max doing", "should I use GMV Max or run campaigns manually", "is GMV Max cannibalising my other campaigns", "which products are selling on TikTok Shop", "my GMV Max ROI dropped", "I can't see anything inside GMV Max", or "is TikTok Shop worth the spend" — even when the user only says "Shop ads" or "my TikTok black box". TikTok Ads only, and only for accounts running TikTok Shop. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| sales-analyticscoupler-io/skillsUse this skill when the user wants to analyze sales pipeline, review win rates, investigate sales velocity or cycle length, build a sales report, evaluate rep performance, look at lead source quality, or answer questions about their CRM data. Triggers include 'how is the pipeline', 'win rate by segment', 'sales cycle', 'pipeline coverage', 'rep performance', 'forecast accuracy', 'why are deals stalling', 'lead source quality', 'stage conversion', 'pull my Salesforce numbers', 'HubSpot deals report', 'sales report'. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| ai-search-citations-to-revenuecoupler-io/skillsUse for "which of our pages do ChatGPT, Perplexity or Gemini cite", "does our AI search visibility bring traffic, signups or sales", "is our Peec visibility worth anything", "which AI-cited pages or products make us money", "GEO funnel", "AI search to revenue", or when someone uploads Peec AI (or Profound, Otterly, Scrunch and similar) citation exports and wants them tied to results — even when they never say "funnel". Follows your cited URLs to AI-referred, organic, referral and direct sessions in GA4, Search Console clicks and impressions, the GA4 key events you choose, and the business outcome — orders, won deals or payments from Shopify, WooCommerce, HubSpot, Pipedrive, Salesforce, Stripe and similar — and names the stage where the chain breaks. Runs on Coupler.io; missing sources are offered and connected. For AI-referral traffic against organic with no citation data, use ai-traffic-vs-organic-search-report. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| ai-traffic-vs-organic-search-reportcoupler-io/skillsShows how much traffic answer engines like ChatGPT, Perplexity, Gemini and Claude send your site, and how it compares to normal organic search, from live GA4 data in your Coupler.io workspace — sessions, engagement, key events and revenue from AI referrals against organic, and whether AI is growing or replacing search. Use for "how much traffic does my site get from ChatGPT", "are AI answer engines sending me visitors", "AI referral vs organic search traffic", "am I getting AEO traffic to my site", "how is answer engine optimization doing for us", "should I invest in GEO", "are my AI referrals converting" — even when the user says "ranking in AI answers" or "GEO check". Important: this measures traffic AI engines already send you, not whether you appear in their answers — citation data isn't in Coupler's GA4 or GSC connectors. GA4 only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| branded-vs-non-branded-search-trafficcoupler-io/skillsSplits your organic search into brand and non-brand and tells you which is really growing, from live Google Search Console data in your Coupler.io workspace — clicks, impressions, CTR and position for people searching your name versus people finding you cold, the non-brand share and its trend, and new non-brand queries coming in. Use for "is my SEO growth real or just brand", "brand vs non-brand organic search", "how much of my search traffic is people searching my name", "is my non-brand search traffic growing", "am I reaching new audiences in organic search", "split my organic search by brand" — even when the user never says "branded". This is the is-it-real-demand view: whether search growth is new reach or just people who already know you. For the full opportunity list use google-search-console-keyword-opportunities. Google Search Console only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| content-decay-analysiscoupler-io/skillsFinds pages that are quietly losing organic traffic over time, from live Google Search Console data in your Coupler.io workspace — which pages are down on clicks, whether it's a ranking slip or fewer people searching, and which are worth updating first. Use for "which of my pages are losing search traffic", "what content is decaying", "which blog posts should I refresh", "why is my organic search traffic sliding", "which pages dropped in Google since last quarter", "find pages that need updating for SEO" — even when the user never says "decay". This is the losing-ground view: pages that used to do better and why. For pages that never ranked well in the first place use google-search-console-keyword-opportunities. A sudden site-wide drop isn't decay — this skill flags it rather than diagnosing it. Google Search Console only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| content-refresh-impactcoupler-io/skillsChecks whether the pages you updated actually won back search traffic, from live Google Search Console data in your Coupler.io workspace with the refresh dates you give it — clicks, impressions and position before and after each update, measured against how the rest of the site moved over the same weeks, so a site-wide lift isn't credited to the refresh. Use for "did our content refresh work", "did updating those blog posts help", "which page updates recovered traffic", "is refreshing old content worth it", "what happened after we rewrote these pages", "should we keep updating old posts" — even when the user never says "refresh". This is the did-it-work view after an update. For which pages need refreshing in the first place use content-decay-analysis. Google Search Console only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| google-business-profile-client-reportcoupler-io/skillsBuilds the monthly Google Business Profile report a client reads, from live Google Business Profile data in your Coupler.io workspace — views on Search and Maps, calls, website clicks and direction requests scored against target, last month and last year, the rating and reviews with the reply record, what people searched to find the listing, a misses section that names problems first, and recommendations someone can be held to. Use when someone asks for a monthly local SEO or Google Business Profile report for a client, wants the local section of a client deck, asks "what do I tell the client about their Google listing", or needs several locations written up for one client — even when they never say "report". For agencies and in-house teams reporting upward. For the operator's own read use google-business-profile-performance-report. Google Business Profile only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| google-business-profile-performance-reportcoupler-io/skillsShows how a Google Business Profile listing is doing, from live Google Business Profile data in your Coupler.io workspace — views on Google Search and Maps by phone and desktop, the calls, website clicks, direction requests and bookings those views turned into, actions per 100 views, and how each location moved against the period before and the same period last year. Use for "how is my Google Business Profile doing", "are we getting more calls from Google Maps", "how many people found us on Google this month", "which of our locations is underperforming on Google", "did our local listing views drop", "GBP performance report", "Google My Business insights" — even when the user never says "performance". This is the operator's read of the listing itself. For what people typed to find it use google-business-profile-search-keywords; for ratings and replies use google-business-profile-reviews-and-replies; for the write-up a client reads use google-business-profile-client-report. Google Business Profile only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| google-business-profile-reviews-and-repliescoupler-io/skillsReads the reviews on a Google Business Profile listing, from live Google Business Profile data in your Coupler.io workspace — rating and review volume over time, the share of one- to three-star reviews, how many reviews got a reply and how fast, which low ratings are still unanswered, and what the written reviews keep complaining about or praising, per location. Use for "how are our Google reviews", "are our ratings going down", "which reviews haven't we replied to", "how fast do we reply to reviews", "what are customers complaining about on Google", "compare ratings across our locations", "Google review report" — even when the user never says "reviews". This is the reputation read. For views, calls and direction requests use google-business-profile-performance-report; for the client write-up use google-business-profile-client-report. Google Business Profile only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| google-business-profile-search-keywordscoupler-io/skillsShows what people typed into Google Search and Maps before your Google Business Profile listing appeared, from live Google Business Profile data in your Coupler.io workspace — searches for your name against searches for what you do, the terms bringing the most people, terms new this month and terms that disappeared, with the terms Google withholds counted honestly instead of as zero. Use for "what do people search to find us on Google Maps", "which keywords show our Google listing", "are people finding us by name or by category", "GBP search terms", "Google My Business search queries", "are we showing up for [service] near me" — even when the user never says "keywords". This is the how-they-found-you view. For views, calls and directions use google-business-profile-performance-report; for what people search before visiting the website use branded-vs-non-branded-search-traffic. Google Business Profile only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| google-search-console-country-and-device-performancecoupler-io/skillsBreaks organic search performance down by country and device, from live Google Search Console data in your Coupler.io workspace — clicks, impressions, click-through rate and average position by market and by phone/desktop/tablet, against the site's own average. Use for "how does my organic search do by country", "which markets underperform in search", "is mobile or desktop better for my search traffic", "where am I losing search clicks by device", "should I localise for SEO", "which countries rank worse than my site average" — even when the user never says "country" or "device". This is the where-and-on-what view: which markets and devices earn their impressions and which lag the site. For query-level opportunities use google-search-console-keyword-opportunities; for what traffic does after landing use seo-landing-page-performance. Google Search Console only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| google-search-console-keyword-opportunitiescoupler-io/skillsFinds the clicks you're leaving on the table in Google Search, from live Search Console data in your Coupler.io workspace — queries ranking just off page one, pages that get seen but not clicked, and pages quietly competing with each other for the same query. Use for "which keywords are close to page one on my site", "striking distance keyword report", "which of my pages get search impressions but no clicks", "find my organic CTR gaps", "are my pages cannibalizing each other in search", "where are my quick SEO wins", "what should I optimize for organic search next" — even when the user never says "opportunity". The earning view: which search positions are worth acting on and what the action is. For pages losing traffic they used to have, use content-decay-analysis. Google Search Console only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| new-page-indexing-trackercoupler-io/skillsTracks how long new pages take to get picked up by Google and start earning traffic, from live Google Search Console data in your Coupler.io workspace — days from publish to first impression, to first click, to a settled ranking, and which pages have gone nowhere. Use for "are my new pages getting indexed by Google", "how long until new content ranks in search", "which of my pages is Google ignoring", "did my new posts get picked up in search", "why isn't my new page showing up in Google", "how fast does my content start ranking" — even when the user never says "indexation". This is the did-it-get-seen view: whether the publishing pipeline is reaching Google and how quickly — and, for pages that went nowhere, Google's own index status for each. For pages that once ranked and are slipping use content-decay-analysis. Google Search Console only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| organic-traffic-drop-diagnosiscoupler-io/skillsWorks out why organic search traffic dropped suddenly, from live Google Search Console data (and GA4 when connected) in your Coupler.io workspace — finds the date it broke, then splits the lost clicks by section, page, country, device and brand to name the most likely cause: tracking, migration, a site-wide ranking fall, one section, lost demand or seasonality. Use for "why did my organic traffic drop", "our SEO traffic fell off a cliff", "did we get hit by a Google update", "traffic dropped after the redesign", "search clicks halved last week", "is it the site or is it tracking" — even when the user never says "diagnosis". This is the sudden-break view: one date, one cause to check first. For a slow slide on individual pages use content-decay-analysis. Needs Google Search Console; GA4 optional. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| paid-vs-organic-search-overlapcoupler-io/skillsLines up Google Ads search terms against your Google Search Console queries, from live data in your Coupler.io workspace, to show where you pay for clicks on searches you already rank well for, where paid covers searches you don't rank for, and which brand terms carry most of the overlap — with the spend on each and a holdout test plan instead of a guess. Use for "are we paying for clicks we'd get for free", "should we stop bidding on our brand", "paid and organic overlap", "do our ads cannibalise SEO", "which keywords can we cut because we rank", "where does SEO need paid support" — even when the user never says "overlap". This is the paid-meets-organic decision: where search spend duplicates rankings. For wasted spend inside Google Ads alone use google-ads-wasted-spend-and-scaling; for brand vs non-brand organic only use branded-vs-non-branded-search-traffic. Needs Google Ads and Google Search Console. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| seo-client-reportcoupler-io/skillsBuilds the monthly SEO report a client reads, from live Google Search Console data (and GA4 when connected) in your Coupler.io workspace — every KPI scored against target and against last month and last year, non-brand growth separated from brand, wins with numbers, a misses section that names the problem first, and recommendations someone can be held to. Use when someone asks for a monthly SEO report for a client, wants the organic section of a client deck, needs last month's search performance written up, asks "what do I tell the client about SEO", or asks how to present an SEO target they missed — even when they never say the word "report". For agencies and in-house teams reporting upward. For the operator's own read use google-search-console-keyword-opportunities or content-decay-analysis. Needs Google Search Console; GA4 optional. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| seo-landing-page-performancecoupler-io/skillsJoins Google Search Console and GA4 to show which landing pages bring organic traffic and what that traffic does once it lands, from live data in your Coupler.io workspace — search clicks and rankings next to engagement, key events and revenue, per page. Use for "does my organic search traffic convert", "which landing pages actually make money from SEO", "which SEO pages are worth the effort", "my rankings are up but sales aren't", "which pages get search clicks but no conversions", "landing page SEO report" — even when the user never says "landing page". This is the search-to-outcome view: the page ranks, gets clicked, then what. For search-side only use google-search-console-keyword-opportunities; for AI-referral traffic use ai-traffic-vs-organic-search-report. Needs GA4 and Search Console. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| topic-cluster-performancecoupler-io/skillsGroups your search traffic by topic instead of by page, from live Google Search Console data in your Coupler.io workspace — each topic's clicks, impressions, CTR and position, its share of clicks against its share of pages, its trend, and how much rests on one page — so you can see which topics earn their place and which take effort without paying back. Topics come from a saved rule, the site's URL folders, or patterns you give it. Use for "which topics perform best in search", "how is our blog doing by category", "which content clusters drive organic traffic", "what topics should we write more about", "which sections of the site are growing in Google", "topic cluster report" — even when the user never says "cluster". This is the topic-level view. For page-level quick wins use google-search-console-keyword-opportunities. Google Search Console only. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| coupler-io-live-dashboardcoupler-io/skillsBuild a live Cowork artifact (persistent HTML widget) backed by a Coupler.io dataflow. Use this skill whenever the user wants a live dashboard, persistent widget, daily-check page, or interactive explorer over Coupler.io data — including phrases like "live artifact for Coupler", "Coupler dashboard widget", "build a widget over a Coupler dataset", "Coupler.io live dashboard", "build a daily dashboard from a Coupler dataflow", or any time they ask to render Coupler data in a re-openable view that auto-refreshes. Triggers even when the user does not say "skill" or "artifact" but describes the same outcome (e.g. "I want a page I can check every morning that pulls my Coupler data"). | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| humanizer-remove-ai-writing-patternscoupler-io/skillsRemove AI writing patterns and add human voice to any text. Use when the user says "humanize this", "make it sound human", "remove AI patterns", "this sounds like AI", "make it natural", "de-slop this", "edit for voice", or when reviewing any drafted text (blog posts, emails, Slack messages, social posts, docs) for AI-sounding language. Also activate after generating any written content when the user has asked for natural or human-sounding output. | Stars: 41 | Updated | Claude CodeCodex | Unverified | Install |
| abuseipdb-apiLiberty91LTD/cti-skillsAbuseIPDB API reference. IP reputation and abuse report lookups. | Stars: 40 | Updated | Claude CodeCodex | Unverified | Install |
| achLiberty91LTD/cti-skillsAnalysis of Competing Hypotheses — structured technique for evaluating multiple explanations against evidence. Use when facing ambiguous attribution or multiple plausible scenarios. Prefers graded evidence items from /quality-of-information-check and runs that skill first when handed raw URLs or text. Runs on ungraded evidence when asked, labelled as such, unweighted, and capped at Moderate confidence. | Stars: 40 | Updated | Claude CodeCodex | Unverified | Install |
| campaign-trackingLiberty91LTD/cti-skillsUse when documenting a named campaign across time and victims, the user asks to start or update a campaign record, or another skill identified a multi-incident cluster that warrants formal tracking. Provides the template (timeline, attribution, victimology, attack chain, Diamond Model mapping, IOC clusters) and the lifecycle from active to historical. | Stars: 40 | Updated | Claude CodeCodex | Unverified | Install |
| carding-financial-fraudLiberty91LTD/cti-skillsUse when the user asks about carding, BIN attacks, payment-card breach markets, fullz/CVV2 trade, autoshops (BidenCash, Brian's Club, Russianmarket, B1ack's Stash), or financial-fraud TTPs. Self-updating knowledge cell. | Stars: 40 | Updated | Claude CodeCodex | Unverified | Install |