session-start

Initialize music production sessions by checking dependencies and loading configurations.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/apavanello/claude-ai-music-skills --skill session-start-apavanello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-start
Source: https://github.com/apavanello/claude-ai-music-skills/tree/main/skills/session-start
Command: npx skills add https://github.com/apavanello/claude-ai-music-skills --skill session-start-apavanello

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp, python.

What problem does it solve?

This Skill ensures a music production workflow session is properly initialized, configured, and ready for creation or continuation by verifying setup, loading configurations, checking for updates, and reporting the current state.

Core Features & Use Cases

  • Setup Verification: Checks for the presence of the MCP server and Python environment dependencies.
  • Configuration Loading: Loads user-defined settings from ~/.bitwize-music/config.yaml and optional overrides.
  • State Management: Loads and verifies the session state (state.json), rebuilding it if necessary.
  • Plugin Version Management: Handles plugin migrations by comparing versions and applying required updates.
  • Status Reporting: Provides a comprehensive report on album ideas, in-progress albums, pending source verifications, and last session context.
  • Contextual Tips: Offers relevant tips based on the current state of the session.
  • Use Case: Ideal for starting a new music project or resuming work on an existing one within the Hermes Agent environment, ensuring all prerequisites are met before proceeding with album creation, research, or generation tasks.

Quick Start

Engage the session-start skill at the beginning of each music production session.

Frequently Asked Questions about session-start

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

FAQPage Schema
How do I initialize a music production session and verify dependencies?

Initializing a music production session involves verifying MCP server and Python environment dependencies, loading user-defined settings from config.yaml, and checking the session state to ensure the environment is prepared for album creation.

How does session state management work when resuming a music project?

Session state management loads and verifies the state.json file, automatically rebuilding it if necessary, to report in-progress albums, pending source verifications, and the last session context for accurate project resumption.

Do I need a specific Python environment and config file to start the workflow?

Yes, starting the workflow requires a verified Python environment and MCP server, plus a user-defined configuration file at ~/.bitwize-music/config.yaml to load settings and apply optional overrides.

What is the best way to handle plugin migrations during setup?

Handling plugin migrations involves comparing installed plugin versions against required versions and automatically applying the necessary updates during the session initialization and configuration process.

Why does my session status report show pending source verifications?

The session status report shows pending source verifications because the initialization process identifies incomplete tasks from your previous music production session and flags them in the comprehensive status report for immediate attention.

Can I use the Hermes Agent framework without loading a previous state?

You can use the Hermes Agent framework without a previous state because the initialization skill automatically rebuilds the state.json file from scratch if it is missing or corrupted during the setup and verification process.