spotify
- 48 skills
- 0 followers
- 1 day ago last updated
- ▌ Deploy To Maven Central · spotifyDeploys the library to OSSRH staging and creates a pre-release, but publishing must be done manually via the Sonatype web UI.
- ▌ Save To Spotify · spotify bundleCreate polished audio content and save to Spotify. Produces episodes with TTS narration, a rich timeline (chapters plus in-player images, external links, and Spotify entity cards), and a cover image. Also use for raw media saves, show/episode management, and timeline navigation.
- ▌ Configure Chapter Skip · spotifyConfigure chapter-skip playback on a Save to Spotify show — the player's skip buttons jump between chapters instead of seeking 15 seconds. Must be explicitly invoked; use ONLY when the user explicitly says skip-to-topic, skip-to-chapter, chapter skipping, chapter skip, or an equivalent phrase. Never trigger proactively.
- ▌
- ▌
- ▌ Testing · spotifyLoad before writing, modifying, or adding any test file (unit, integration, or e2e). Covers testing philosophy, conventions, shared test scaffolds (__tests__/shared/), test framework structure (__tests__/e2e/testing-framework/, __tests__/ui/testing-framework/), and the named-key press() API for e2e tests.
- ▌
- ▌ Architecture · spotifyArchitecture guidelines and constraints for the Confidence Wizard CLI project
- ▌ Integrations · spotifyIDE integration strategy pattern and guidelines for the Confidence Wizard CLI project
- ▌
- ▌ Search · spotifySearch Spotify Portal's software catalog and technical documentation using natural language. Use when the user asks to find services, APIs, systems, components, owners, or Portal documentation and does not already know the exact entity reference.
- ▌ Actions · spotifyDiscover, inspect, and invoke Spotify Portal actions through the Portal CLI. Use when the user asks what Portal can do, names an action ID, or wants to run a Portal operation.
- ▌ Service · spotifyInspect a Spotify Portal service's owner, team, on-call contact, Slack channel, runbook, build, deployment, runtime, incidents, or documentation. Use when the user asks who owns a service, whether a service is healthy, where its runbook or docs are, or requests a service briefing.
- ▌ Feedback · spotifySubmit feedback about the Spotify Portal CLI to the Portal team. Use when the user explicitly asks to send CLI feedback, or voices an impression, complaint, suggestion, or praise about the Portal CLI or these Portal workflows and confirms they want it submitted.
- ▌ Bulk Reader · spotifyDelegate bulk file reading to AiKA. Use when you need to read files >350 lines, answer questions across 3+ files, or summarize large diffs.
- ▌ Code Writer · spotifyDelegate boilerplate code generation to AiKA. Use for tests, config, docstrings, type stubs, or any generation where >80% is predictable from reference files.
- ▌ Setup · spotifySet up, authenticate, and verify Spotify Portal for the current coding agent. Use when the user asks to install or connect Portal, authenticate the Portal CLI, select a Portal instance, or verify CLI access.
- ▌ Doctor · spotifyDiagnose Spotify Portal plugin, CLI, authentication, and action access without changing state. Use when setup is failing, commands are missing, authentication is unclear, a plugin update looks stale, or the user asks whether Portal is ready.
- ▌ Explore Metric · spotifyExplore and preview metrics for any event or fact table. Generates a pre-filled Metric Explorer URL with fact table, entity, exposure table, metric kind, and aggregation — so the user can click through to the UI, hit Calculate, and create the metric. Use when the user asks to explore a metric, preview a metric, create a metric from an event, or says /explore-metric.
- ▌ Analyze Project · spotifyAnalyze a user's project and propose a meaningful feature flag change using Confidence. Use when the user says /analyze-project, asks what to flag, wants flag suggestions, or asks "what should I feature-flag in my project?"
- ▌ Migrate Posthog · spotifyMigrate feature flags from PostHog to Confidence SDK. Use when the user says /migrate-posthog, asks to migrate PostHog flags, or transform SDK code to Confidence.
- ▌ Setup Warehouse · spotifySet up a data warehouse for Confidence experimentation analytics. Use when the user asks to connect a warehouse, set up BigQuery/Snowflake/Databricks/Redshift, or configure data connectors.
- ▌ Instrument Events · spotifyAnalyze a project's codebase, identify what events to track alongside the metrics they'd power, create event definitions in Confidence with entity references (so fact tables are auto-created), add SDK track() calls, and verify the pipeline. Use when the user asks to instrument events, add tracking, set up event tracking, analyze what to track, or wants to measure experiment impact. For metric preview and creation, see the explore-metric skill.
- ▌ Onboard Confidence · spotify bundleCreate Confidence accounts and onboard users. Use when the user asks to create an account, invite users, onboard to Confidence, or check account status.
- ▌ Setup Warehouse Bigquery · spotifySet up BigQuery as a data warehouse for Confidence. Use when the user chose BigQuery for warehouse setup.
- ▌ Setup Warehouse Redshift · spotifySet up Redshift as a data warehouse for Confidence. Use when the user chose Redshift for warehouse setup.
- ▌ Setup Warehouse Snowflake · spotifySet up Snowflake as a data warehouse for Confidence. Use when the user chose Snowflake for warehouse setup.
- ▌ Onboard Confidence Dry Run · spotifyDry-run the Confidence onboarding flow to test UX without real API calls. Use when the user says "dry run", "test onboarding", "demo onboarding", or wants to preview the onboarding experience.
- ▌ Setup Warehouse Databricks · spotifySet up Databricks as a data warehouse for Confidence. Use when the user chose Databricks for warehouse setup.
- ▌ Ads · spotifyList or get Spotify Ads API ad sets and ads, and stage their creation or updates through drafts by default. Use direct live writes only when explicitly requested.
- ▌ Bulk · spotifyStage batch changes to Spotify Ads API campaigns, ad sets, and ads through drafts by default — pause, resume, budgets, delivery, archive, creative, and tracking changes. Use direct live writes only when explicitly requested.
- ▌ Clone · spotifyClone an existing Spotify Ads API campaign or ad set as a validated draft hierarchy by default, with optional modifications to name, dates, budget, or targeting.
- ▌ Assets · spotifyUpload, list, and manage Spotify Ads API creative assets — audio, video, and images for ad campaigns.
- ▌ Drafts · spotifyDefault 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 · spotifyExport 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.
- ▌ Report · spotifyPull Spotify Ads API reporting data — aggregate metrics, audience insights, or async CSV reports.
- ▌ Monitor · spotifyCheck 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.
- ▌ Audiences · spotify bundleManage Spotify Ads API audiences: upload or replace customer lists, create custom web-event or ad-engagement audiences, create lookalikes, list/get/edit audiences, inspect eligible datasets, and delete audiences. Use when a user asks to onboard first-party data, retarget people who saw or clicked ads, build an event-based audience, create a lookalike, replace an audience file, check audience status, or remove an audience.
- ▌ Campaigns · spotifyList or get Spotify Ads API campaigns, and stage campaign creation or updates through drafts by default. Use direct live writes only when explicitly requested.
- ▌ Configure · spotify bundleConfigure Spotify Ads API credentials via OAuth 2.0 or direct token. Sets up authentication, ad account, and execution preferences.
- ▌ Dashboard · spotifyQuick performance overview of all active Spotify ad campaigns — impressions, spend, reach, clicks, and pacing at a glance.
- ▌ Account Admin · spotify bundleAdminister Spotify Ads API businesses and ad accounts: discover businesses and accounts, inspect or update supported profile and billing fields, create businesses or ad accounts, list members and roles, invite users, assign ad-account access, update roles, cancel invitations, and remove access. Use when a user asks to find an ad account by ID, audit access, onboard an agency or teammate, manage business/ad-account membership, or update supported account identity details.
- ▌ Spotify Ads API Reference · spotify bundleThis skill should be used when the user asks to "call the Spotify Ads API", "create a Spotify ad campaign", "manage Spotify ads", "pull Spotify ad reports", "set up ad sets or ads", "upload ad assets", "target audiences on Spotify", "check campaign status", "get ad account info", "look up API schema or fields", "check what targeting options exist", or asks about Spotify advertising endpoints, request/response formats, enum values, or authentication.
- ▌ Build Campaign · spotifyCreate a full campaign (campaign + ad sets + ads) from a plain-text description. Parses natural language into structured API calls. Prefers the draft workflow for safer creation with batch validation.
- ▌ Change History · spotifyView a timeline of changes made to campaigns, ad sets, creatives, and other entities in an ad account — who changed what, when, and how.
- ▌ Campaign Strategy · spotify bundleGenerate Spotify Ads campaign strategy from a landing page, product or business page, brand brief, location page, uploaded creative assets, existing Spotify Ads assets, or a natural-language business goal. Use when the user asks for the best campaign structure, targeting plan, audience plan, budget split, creative rotation, API-ready campaign plan, or pre-build recommendations before creating Spotify campaigns.
- ▌ Measurement Debug · spotify bundleDiagnose 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.
- ▌ Measurement Setup · spotify bundlePlan and configure Spotify Ads conversion measurement with Spotify Pixel, direct or Google Tag Manager-based Conversions API (CAPI), datasets, advanced matching, mobile apps, event mapping, parameters, ad-account sharing, and CAPI credentials. Use when a user asks to design or implement measurement, install Pixel, integrate CAPI, combine browser and server events, register an app, create a dataset, or prepare a measurement implementation plan. For broken or inconsistent existing implementations, use measurement-debug.