analyze-artist

What this skill does

# /analyze-artist

## Purpose

The `/analyze-artist` command performs comprehensive discography research for a musical artist, producing a structured YAML profile that identifies creative eras, recommends catalog organization, and guides collection development. This command is the entry point for the Media Curator framework's artist-centric workflow.

## Parameters

### Required

**`<artist_name>`**
- The artist or band name to analyze
- Supports aliases and common alternate names
- Example: `"Twenty One Pilots"`, `"Radiohead"`, `"Kendrick Lamar"`

### Optional

**`--scope <scope_type>`**
- Controls the breadth of analysis
- Default: `complete`
- Options:
  - `complete` - Full discography across all eras
  - `era:<era_name>` - Focus on specific creative period (e.g., `era:Blurryface`)
  - `style:<style_name>` - Focus on releases matching style tag (e.g., `style:acoustic`)

**`--depth <depth_level>`**
- Controls research thoroughness and time investment
- Default: `thorough`
- Options:
  - `quick` - MusicBrainz canonical releases only, basic era detection (2-5 min)
  - `moderate` - MusicBrainz + Discogs cross-reference, standard era analysis (5-15 min)
  - `thorough` - Full multi-source research, narrative analysis, gap identification (15-45 min)

**`--output <file_path>`**
- Specify custom output location for YAML profile
- Default: `.aiwg/media-curator/profiles/<artist-slug>.yaml`
- Example: `--output ~/music/analysis/radiohead.yaml`

**`--format <format_type>`**
- Output format for artist profile
- Default: `yaml`
- Options:
  - `yaml` - Structured YAML profile (default, machine-readable)
  - `markdown` - Human-readable Markdown report with embedded YAML
  - `json` - JSON format for programmatic integration

**`--include-unofficial`**
- Include bootlegs, demos, and unofficial releases in analysis
- Default: `false` (official releases only)
- When enabled, adds `unofficial` section to YAML output

**`--interactive`**
- Enable interactive mode for era boundary decisions
- Default: `false` (automated analysis)
- Prompts user at ambiguous era transitions for input

## Workflow

### Phase 1: Artist Identification

1. Query MusicBrainz for artist MBID using provided name
2. Resolve aliases and display disambiguation options if multiple matches
3. Retrieve artist metadata (active years, genres, relationships)

**Example Query**:
```bash
curl "https://musicbrainz.org/ws/2/artist/?query=artist:Twenty%20One%20Pilots&fmt=json"
```

### Phase 2: Release Discovery

1. Fetch complete release groups from MusicBrainz
2. Cross-reference Discogs for variant pressings and bootlegs (if `--include-unofficial`)
3. Filter by release type (album, EP, single, live, compilation)
4. Sort chronologically by earliest release date

**Data Points Collected**:
- Release title and MBID
- Release date (year-month-day)
- Release type and status (official, promotion, bootleg)
- Label and catalog number
- Track count and total duration
- Associated credits (producers, featured artists)

### Phase 3: Era Detection

1. Analyze temporal clustering of releases
2. Identify lineup changes, label transitions, genre shifts
3. Review Wikipedia and AllMusic for contextual markers
4. Detect narrative arcs and concept album sequences
5. Establish era boundaries with supporting evidence

**Detection Signals** (see @$AIWG_ROOT/agentic/code/frameworks/media-curator/agents/discography-analyst.md for complete signal taxonomy):
- Musical evolution (genre tags, production style)
- Contextual changes (label, location, collaborators)
- Narrative markers (artist statements, concept albums)
- Temporal patterns (recording gaps, intensive output periods)

### Phase 4: Special Collections Identification

1. Identify narrative arcs (concept album sequences, trilogy structures)
2. Detect acoustic sessions, live recordings, remix projects
3. Map collaborations and featuring appearances
4. Highlight demo collections and pre-label material

### Phase 5: Catalog Structure Recommendation

1. Design directory hierarchy reflecting eras and special collections
2. Define organization principles (chronological, thematic, hybrid)
3. Recommend segregation of unofficial material
4. Provide implementation-ready file system structure

### Phase 6: Gap Analysis

1. Compare collection against canonical discography
2. Identify missing releases by priority (essential, recommended, optional)
3. Note availability status (in-print, out-of-print, digital-only, unreleased)
4. Flag high-value acquisitions for collection completion

### Phase 7: Output Generation

1. Structure findings into YAML schema (see Output Format section)
2. Write to specified output location or default path
3. Display summary report with key findings
4. Provide next-step recommendations

## Output Format

### YAML Artist Profile

```yaml
artist:
  name: "Artist Name"
  mbid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
  discogs_id: "123456"
  active_years: "YYYY-YYYY"
  genres:
    - "Primary Genre"
    - "Secondary Genre"

analysis_metadata:
  generated: "YYYY-MM-DD HH:MM:SS"
  depth: "thorough"
  scope: "complete"
  sources:
    - "MusicBrainz"
    - "Discogs"
    - "Wikipedia"
    - "AllMusic"

eras:
  - name: "Era Name"
    period: "YYYY-YYYY"
    description: |
      Multi-line narrative description of the creative period,
      including key characteristics, influences, and significance.
    key_characteristics:
      - "Musical trait or innovation"
      - "Thematic or lyrical focus"
      - "Production or collaboration pattern"
    boundary_markers:
      start: "Event or release marking era beginning"
      end: "Event or release marking era conclusion"
    releases:
      - title: "Release Title"
        year: YYYY
        type: "studio" | "live" | "compilation" | "ep" | "single"
        mbid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
        discogs_id: "123456"
        label: "Label Name"
        significance: "Major album" | "Transitional work" | "Definitive statement" | "Minor release"
        tracks: 12
        duration: "45:30"

special_collections:
  - name: "Collection Name"
    type: "narrative_arc" | "acoustic_sessions" | "live_recordings" | "remixes" | "demos" | "collaborations"
    description: |
      Purpose and scope of the special collection,
      including curatorial rationale.
    releases:
      - "Release Title (Year)"
    recommended_location: "catalog/special/collection-slug/"
    curation_notes: |
      Additional context for organizing this collection,
      such as playback order or thematic grouping.

collaborations:
  - artist: "Collaborator Name"
    mbid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
    releases:
      - title: "Release Title"
        year: YYYY
        nature: "featuring" | "production" | "side_project" | "remix" | "tribute"

related_content:
  - type: "solo_projects"
    description: "Band member solo work or side projects"
    items:
      - name: "Project Name"
        artist: "Artist Name"
        mbid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
  - type: "affiliated_artists"
    description: "Frequent collaborators or label mates"
    items:
      - name: "Artist Name"
        mbid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

catalog_structure:
  recommended_hierarchy: |
    artist-name/
      01-early-era/
        YYYY-release-title/
      02-breakthrough-era/
        YYYY-release-title/
      03-mature-era/
        YYYY-release-title/
      special/
        narrative-projects/
          trilogy-name/
            part-1/
            part-2/
            part-3/
        acoustic-sessions/
        live-recordings/
      collaborations/
        artist-name/
      unofficial/
        demos/
        bootlegs/

  organization_principles:
    - "Primary hierarchy: chronological eras"
    - "Secondary hierarchy: release type and significance"
    - "Special collections isolated for thematic coherence"
    - "Unofficial material clearly segregated"
    - "Directory names: YYYY-kebab-case-title"

  implementation_notes: |
    Sp