Install
npx skills add spotify/ads-claude-plugin --skill change-history
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install spotify-ads-api@spotify-ads-api
This skill is part of the plugin “spotify-ads-api”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the change-history skill do?
Description from the SKILL.md in the source repository.
Questions about change-history
What does the change-history skill do?
View a timeline of changes made to campaigns, ad sets, creatives, and other entities in an ad account — who changed what, when, and how.
How do I install change-history?
In a terminal: npx skills add spotify/ads-claude-plugin --skill change-history. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use change-history?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is change-history safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from spotify/ads-claude-plugin
Diagnose existing Spotify Ads Pixel, Conversions API (CAPI), and dataset implementations when events are missing, stale, duplicated, unexpectedly high or low, not deduplicated, attached to the wrong account, or present in diagnostics but absent from campaign reporting. Use for Pixel/CAPI troubleshooting, event-delivery audits, token/connection mismatches, source comparison, or measurement incident triage. Prefer read-only checks and never create test conversions without explicit confirmation.
Configure Spotify Ads API credentials via OAuth 2.0 with PKCE or a direct token. Sets up authentication, ad account, and execution preferences.
Quick performance overview of all active Spotify ad campaigns — impressions, spend, reach, clicks, and pacing at a glance.
Default write workflow for Spotify Ads API campaigns, ad sets, and ads. Stage new entities or changes to published entities as drafts, validate them, and publish only after explicit confirmation. Use for create, change, update, adjust, fix, pause, resume, archive, creative, tracking, or other campaign-hierarchy writes even when the user does not say draft.
Export Spotify Ads API campaign data to CSV — full campaign hierarchies with ad sets, ads, targeting, budgets, and performance metrics for offline review, campaign analysis, or budget reconciliation.
Turn advertiser or third-party media plans from spreadsheets, CSVs, PDFs, documents, presentations, or text into a source-traceable Spotify Ads implementation plan, enrich and forecast it with live Ads API data when available, resolve or explicitly defer gaps, obtain review approval, and then create a validated draft campaign hierarchy. Use for media plans, planning grids, insertion-order worksheets, or cross-channel plans that need to become Spotify drafts. Never publish.
Pull Spotify Ads API reporting data — aggregate metrics, audience insights, or async CSV reports.
Check Spotify Ads API campaign health — pacing, delivery issues, budget burn rate, stalled campaigns, and underpacing alerts. Use for one-shot health checks or recurring monitoring when the host supports scheduled automations.
Related skills in Other
A relentless interview to sharpen a plan or design.
No description in the SKILL.md.
No description in the SKILL.md.
No description in the SKILL.md.
No description in the SKILL.md.
No description in the SKILL.md.
No description in the SKILL.md.
No description in the SKILL.md.