rhapsody

v0.2.1

Skills for Rhapsody Teams — how named agent teammates get work done (routing, the room, memory, the two review models), how to compose a roster and write a teammate profile, and how to operate a running installation.

Claude Code2 Skills

By makewhatisLicense: MIT1 GitHub starsUpdated yesterday

Directory evidence

Runtimes: Claude Code
Parsed components: 2 skill or MCP entries
Source updated: Sep 22, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install rhapsody for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install rhapsody@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/makewhatis/rhapsody

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugin/.

Plugin files

plugin/

├── .claude-plugin/plugin.json
├── skills/rhapsody-team-setup/SKILL.md
└── skills/rhapsody-teams/SKILL.md

Included Skills2

rhapsody-team-setupskills/rhapsody-team-setup/SKILL.md

Interactively set up or extend a Rhapsody team — choose the teammates a codebase needs, write the profile that gives a specialist its initial context, and land a valid teams.yaml. Use when someone wants a team for a specific repo or app, wants to add a teammate, wants a review-only or specialist teammate rather than a generalist, or asks "what context should this agent have". Triggers on setting up Rhapsody Teams, creating a roster, writing or forking a profile, extends: swe, ~/.rhapsody/teams/profiles/, and onboarding a team onto a new codebase.

rhapsody-teamsskills/rhapsody-teams/SKILL.md

How work gets done through Rhapsody Teams — named agent teammates with profiles, memory, a shared room, and label-based assignment. Use when planning, filing, or routing work that Rhapsody will execute; when deciding which teammate should take a ticket; when leaving context for teammates; or when inspecting what the team is doing or remembers. Triggers on Rhapsody tickets, teams.yaml, the team room, teammate assignment, rhapsody:@ labels, triage/quorum questions, and "who should build this" planning for the Rhapsody pipeline. ALSO use when operating a running installation — where a review verdict lives, cutting an RC or release, or diagnosing why nothing is dispatching (see operating.md).

Plugin manifests1

plugin/.claude-plugin/plugin.json

{
  "name": "rhapsody",
  "version": "0.2.1",
  "description": "Skills for Rhapsody Teams — how named agent teammates get work done (routing, the room, memory, the two review models), how to compose a roster and write a teammate profile, and how to operate a running installation.",
  "author": {
    "name": "makewhatis",
    "url": "https://github.com/makewhatis"
  },
  "homepage": "https://github.com/makewhatis/rhapsody",
  "repository": "https://github.com/makewhatis/rhapsody",
  "license": "MIT",
  "keywords": [
    "rhapsody",
    "teams",
    "agents",
    "linear",
    "orchestration",
    "code-review"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[rhapsody on Agent Plugins Marketplace](https://pluginsmp.com/plugins/rhapsody)