SkillAgentSearch skills...

device-performance-split

Analyzes how your campaigns perform across mobile, desktop, and tablet. Identifies where device performance diverges significantly and recommends bid adjustments, campaign splits, or creative/landing page changes to capture the gap. Platform: Google and Meta.

Install / Use

npx skills add irinabuht12-oss/marketing-skills --skill device-performance-split

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

80/100

Supported Platforms

Universal

Tags

Our assessment of device-performance-split

device-performance-split scores 80/100 on our quality scale, 2291st of 3,680 Development & Engineering skills we index.

Its SKILL.md is 2.7 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 1,836 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 6 days ago, so device-performance-split is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

device-performance-split compared with similar skills

All 4 of these similar skills score higher than device-performance-split; compare them before choosing.

SkillScoreStarsUpdatedFormat
device-performance-split (this skill)by irinabuht12-oss801.8k6d agoSKILL.md
ai-job-searchby MadsLorentzen10044.5k1d agoCLAUDE.md
claude-howtoby luongnv8910041.7k3d agoCLAUDE.md
algorithmic-artby anthropics100177.9k7d agoSKILL.md
pptxby anthropics100177.9k7d agoSKILL.md

Frequently asked questions

How do I install device-performance-split?
Run npx skills add irinabuht12-oss/marketing-skills --skill device-performance-split. The install tabs above show the steps for each supported agent.
Which AI agents does device-performance-split work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is device-performance-split safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is device-performance-split still maintained?
The repository was last updated 6 days ago, so device-performance-split is actively maintained.

name: device-performance-split description: Analyzes how your campaigns perform across mobile, desktop, and tablet. Identifies where device performance diverges significantly and recommends bid adjustments, campaign splits, or creative/landing page changes to capture the gap. Platform: Google and Meta. metadata: platform: Google and Meta

25/ Device Performance Split — Google + Meta

What it does

Analyzes how your campaigns perform across mobile, desktop, and tablet. Identifies where device performance diverges significantly and recommends bid adjustments, campaign splits, or creative/landing page changes to capture the gap.

How it works

Claude segments all your campaign data by device type and compares CPA, CVR, CTR, bounce rate, and average order value. It identifies campaigns where one device significantly outperforms or underperforms others, then determines whether the issue is ad-side (creative not working on mobile), landing-page-side (poor mobile experience), or audience-side (different intent by device).

Practical example

Your B2B lead gen campaigns show desktop CPA at $41 with 3.8% CVR and mobile CPA at $78 with 1.6% CVR. But mobile accounts for 58% of clicks because that's where the impressions are. Claude digs deeper and finds the landing page form has 9 fields that are painful on mobile, and the page load time on mobile is 4.2 seconds vs 1.8 on desktop. Recommendation: create a simplified mobile form (3 fields), fix mobile page speed, and reduce mobile bid adjustments by 25% until the fixes are live to stop the bleeding.

What you get back

  • Device performance comparison across all campaigns with key metrics
  • Campaigns with the largest device performance gaps flagged
  • Root cause analysis: is the gap from creative, landing page, or audience differences
  • Bid adjustment recommendations by device per campaign
  • Campaign split recommendations for cases where devices need completely different strategies

When to use it

  • When CPA is higher than expected and you haven't checked device splits
  • After landing page redesigns to verify mobile experience didn't break
  • When mobile traffic share increases but conversions don't follow
  • For ecommerce accounts where mobile browsing vs desktop purchasing creates attribution confusion

Data access (Ryze MCP)

This skill works best with live account data. Connect the free Ryze MCP once and Claude reads your Google Ads, Meta Ads, GA4 and Search Console directly:

  • claude.ai / Claude Desktop: Settings → Connectors → Add custom connector → https://connector.get-ryze.ai/mcp
  • Claude Code: claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp
  • Cursor: Settings → MCP → add the same URL

Setup guide: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp

Related Skills

View on GitHub
GitHub Stars1.8k
CategoryDevelopment
Updated6d ago
Forks537

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium