AgentStack
SKILL verified CC0-1.0 Self-run

Session Start

skill-bitwize-music-studio-claude-ai-music-skills-session-start · by bitwize-music-studio

Runs the session startup procedure - verifies setup, loads config and state, checks skill models, and reports project status. Use at the beginning of a fresh session.

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-bitwize-music-studio-claude-ai-music-skills-session-start

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Session Start? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Your Task

Run the full session start procedure and report project status to the user.


Session Start Skill

You perform the 8-step session startup procedure that initializes a working session.


Step 1: Verify Setup

Quick dependency check:

~/.bitwize-music/venv/bin/python3 -c "import mcp" 2>&1 >/dev/null && echo "MCP ready" || echo "MCP missing"
  • If MCP missing: Stop immediately and suggest: /bitwize-music:setup mcp
  • If config missing (~/.bitwize-music/config.yaml doesn't exist): suggest /bitwize-music:configure
  • Don't proceed until setup is complete

Step 1.5: Health Check

Use the health_check MCP tool (checks venv packages + skill registration in one call):

Venv results (from result.venv):

  • status: "ok" → continue silently
  • status: "stale" → warn with mismatches and fix command, continue session
  • status: "no_venv"stop and suggest /bitwize-music:setup
  • status: "error" → warn and continue

Skill registration results (from result.skills):

  • status: "ok" → continue silently
  • status: "stale" → warn: list missing and ghost skill names, show fix message
  • status: "no_cache" → warn that plugin cache not found, continue

Step 2: Load Config

Read ~/.bitwize-music/config.yaml.

If missing, tell user to run /bitwize-music:configure.

Step 3: Load Overrides

Read paths.overrides from config (default: {content_root}/overrides):

  • Check for {overrides}/CLAUDE.md — incorporate instructions if found
  • Check for {overrides}/pronunciation-guide.md — note if found
  • Skip silently if missing (overrides are optional)

Step 4: Load State Cache

Read ~/.bitwize-music/cache/state.json:

  • If missing, corrupted, schema mismatch, or config changed: rebuild via MCP

`` rebuild_state() ``

Step 4.5: Check for Plugin Upgrades

Compare plugin_version in state.json against current version in ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json:

  1. If plugin_version is null (first run or pre-upgrade-system): Set to current version, skip migrations
  2. If versions match: No action needed
  3. **If stored `" |

| Overrides loaded | "Custom overrides loaded from {overrides}/" | | Overrides missing | "Customize your workflow with override files — see /reference/overrides/" | | Pending verifications | "Source verification needed before generation can proceed" |

Also show one random general tip (rotate through these):

  • "Ask 'what should I do next?' for workflow guidance"
  • "Use /bitwize-music:resume to quickly jump back into an album"
  • "The researcher skill coordinates 10 specialized sub-skills for deep research"
  • "Check pronunciation before generating — Suno can't infer from context"
  • "Use /bitwize-music:clipboard to copy lyrics/prompts for Suno"
  • "Master your audio with /bitwize-music:mastering-engineer for professional results"

Step 8: Ask

End with: "What would you like to work on?"


Report Format

SESSION START
=============

Setup: MCP ready, config loaded
Health: [venv ok, skills ok | warnings listed]
Overrides: [loaded from {path} | not found (optional)]
State: [loaded | rebuilt | error]

ALBUM IDEAS
  Pending: X | In Progress: Y

IN-PROGRESS ALBUMS
  [album-name] (genre) - Status [X/Y tracks]
  [album-name] (genre) - Status [X/Y tracks]

PENDING VERIFICATIONS
  [album-name]: track-01, track-05

LAST SESSION
  Album: [name] | Phase: [phase]
  Pending: [actions]

TIP: [contextual tip]

What would you like to work on?

Remember

  1. Don't skip steps — Each step matters for session integrity
  2. Rebuild state if needed — Stale state leads to wrong recommendations
  3. Be concise — This is a status report, not a conversation
  4. Warn about verifications — Unverified sources block generation
  5. One tip, not five — Pick the most relevant tip for the current state

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.