Skip to content
cccskills
FreePublished on GitHubEnglish overview

music-connect

Connect a Cognitum Music account to Claude Code through the cogmusic MCP server, a bridge that exposes music tools. The skill guides token creation, local registration, connection checks, and replacement of expired or revoked credentials.

OriginalShow the original description

One-time setup — mint a Cognitum Music personal access token and register the cogmusic MCP server with Claude Code

ruvnet/ruflo
AI rating100/ 100See how to install

Good for

  • Set up a connection before using music skills
  • Check a missing or unhealthy cogmusic connection
  • Replace an expired or revoked access token
  • Check whether to start a new Claude Code session

Overview

What it does

This skill guides the initial setup for using a Cognitum Music account from Claude Code. It checks whether cogmusic, the MCP server connecting the external service to the agent, is registered, then guides token creation, registration, and connection verification. If an existing registration has connection problems, it covers removing and registering it again.

When it helps

Use it before starting with music-* skills or when music tools do not appear. It also covers replacing expired or revoked tokens. Setup is performed for each machine and project.

Example requests

  • “Guide me through connecting Cognitum Music to Claude Code.”
  • “Check the connection status of cogmusic.”
  • “Explain how to replace a revoked token.”

Notes

You must sign in to Cognitum Music and create the token yourself. The token is a secret displayed only once. Do not paste it into chat; run the registration command locally yourself. The setup uses Claude Code and npx, and the supplied instructions specify cogmusic@0.1.1. If tools remain unavailable after a successful connection, you may need a new Claude Code session.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodIt explicitly identifies missing music tools, unhealthy connections, and token replacement as situations for using the skill.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
AGoodIt provides status checks, token creation, registration and re-registration steps, and the expected successful connection output.
SafetyAre sending data, deleting files, and running commands disclosed?
AGoodThe user registers the token locally without placing it in chat, and the executed package version is pinned.
Easy setupDoes it need few tools or API keys, and are they documented?
AGoodIt supplies the login destination, token creation steps, and a registration command using Claude Code and npx.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Music Connect

Wires this session up to the user's own Cognitum Music account (music.cognitum.one) via the cogmusic MCP bridge. This is a one-time, per-machine/per-project setup — run it before any other music-* skill if mcp__cogmusic__* tools aren't already loaded.

When to use

  • The user asks to generate/produce music and no mcp__cogmusic__* tools are visible yet.
  • claude mcp get cogmusic reports the server missing, disconnected, or unhealthy.
  • The user is rotating or replacing an expired/revoked token.

Steps

  1. Check for an existing, working registration first:

    claude mcp get cogmusic

    If it reports ✔ Connected, you're already set up — stop here.

  2. If no token was provided, tell the user exactly how to mint one (this step requires their own browser login — you cannot do it for them):

    • Sign in at https://music.cognitum.one/mcp
    • Click "Generate connection token" (label it something recognizable, e.g. "Claude Code")
    • Copy the raw token — it starts with cogmcp_ and is shown exactly once

  3. Register the MCP server once you have the token. Do not paste the token into the chat or have the model type it into a command: ask the user to run the registration themselves (in Claude Code, !claude mcp add ... runs it in this session) so the token never enters the conversation transcript. Never echo it back. Treat it as a secret; it's fine as a one-time argument to claude mcp add, which stores it in local config, not in conversation history):

    claude mcp add cogmusic --env COGMUSIC_TOKEN=cogmcp_... -- npx -y cogmusic@0.1.1

    Pin an exact version (0.1.1 is the current release) instead of @latest, so a later publish cannot change what runs with your token. Versions before 0.1.1 have no fetch timeout and fail create_production calls that run past Node's ~5-minute default (see ADR-0001).

  4. Verify:

    claude mcp get cogmusic

    Expect ✔ Connected. If it shows CONNECTION_CLOSED or a 404, the cogmusic npm package version pinned in the command may be stale or unpublished — check npm view cogmusic version and retry with an explicit version.

  5. If registration already exists but is unhealthy, remove and re-add rather than editing config by hand:

    claude mcp remove cogmusic -s local
claude mcp add cogmusic --env COGMUSIC_TOKEN=cogmcp_... -- npx -y cogmusic@0.1.1

  6. Once connected, the mcp__cogmusic__* tools (list_productions, get_production, create_production, separate_stems, extract_midi, master) become available — proceed to music-generate or music-list.

Notes

  • The token is a personal access token (PAT) scoped to one Cognitum account, minted and revoked by the user themselves at music.cognitum.one/mcp — this plugin has no way to mint or revoke one programmatically, and should never attempt to guess, cache elsewhere, or transmit it anywhere other than the local claude mcp add registration.
  • A newly-registered MCP server's tools may not appear until the next Claude Code session — if mcp__cogmusic__* tools still aren't listed after a successful claude mcp get cogmusic, tell the user to start a fresh session.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

add-model-descriptions

FreeSummaryAI rating 80

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo78.5KUpdated Oct 22, 2026

adr-create

FreeSummaryAI rating 80

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo78.5KUpdated Oct 22, 2026

adr-index

FreeSummaryAI rating 90

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo78.5KUpdated Oct 22, 2026

adr-reindex

FreeSummaryAI rating 70

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo78.5KUpdated Oct 22, 2026

adr-review

FreeSummaryAI rating 80

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo78.5KUpdated Oct 22, 2026

adr-verify

FreeSummaryAI rating 90

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo78.5KUpdated Oct 22, 2026

See all skills by ruvnet

Report a problem with this skill