tl-live-music-data

Resolve cross-provider artist, event, and release ID mappings across live-music APIs.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/toddlevy/tl-agent-skills --skill tl-live-music-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tl-live-music-data
Source: https://github.com/toddlevy/tl-agent-skills/tree/main/skills/tl-live-music-data
Command: npx skills add https://github.com/toddlevy/tl-agent-skills --skill tl-live-music-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill consolidates reference documentation for live music data APIs and their ID mappings, helping developers quickly compare providers and align identifiers across services such as MusicBrainz, Setlist.fm, JamBase, Bandsintown, Ticketmaster, and more.

Core Features & Use Cases

  • Unified API references: centralizes endpoint overviews, auth patterns, rate limits, and data models for major live-music data providers.
  • ID resolution guidance: documents how to map artist, release, and event identifiers across platforms to enable cross-service lookups.
  • Use cases: design data pipelines that join artist metadata with events, sets, and releases across providers for discovery and analytics.

Quick Start

Query the references to identify the best API for your use case and map IDs across services.

Frequently Asked Questions about tl-live-music-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map artist and event IDs across live music data APIs like Setlist.fm and JamBase?

You map artist and event IDs across live music data APIs by querying consolidated reference documentation that details how to align identifiers across providers like Setlist.fm and JamBase for unified lookups.

What is the best way to compare live music data API references for building data pipelines?

Comparing live music data API references is done via a centralized guide documenting endpoint overviews, authentication patterns, rate limits, and data models for major providers to inform pipeline design.

Does this Skill provide API selection guidance for MusicBrainz and Ticketmaster integration?

Yes, centralized API selection guidance and cross-provider ID resolution are provided for integrating live music data across MusicBrainz, Ticketmaster, Bandsintown, nugs.net, and other platforms.

How do I design a workflow to join artist metadata with setlists and releases across providers?

You design workflows to join artist metadata with setlists and releases by applying cross-source ID resolution guidance, enabling data integration and analytics across multiple live music platforms.

Can I use this to centralize documentation for Bandsintown and nugs.net API endpoints?

Yes, endpoint documentation for Bandsintown and nugs.net can be centralized, consolidating API references and ID mappings to support data integration tasks across live music services.

What are the limitations of cross-source ID mapping for live music events and releases?

Limitations of cross-source ID mapping depend on the varying data models and identifier structures of each provider, requiring careful alignment of artist, event, and release IDs across platforms.