Crystal Knows — Claude Code Plugin

DISC personality intelligence for your calls, emails, and meetings, powered by the Crystal Knows MCP server.

What's inside

• Crystal MCP server (crystal) — resolve anyone's Crystal profile (DISC / archetype / traits) by email or LinkedIn URL, plus tools for sales playbooks, email revision, and personality-tuned prompts. Connects to https://api.crystalknows.com/_mcp over OAuth2.
• premeeting skill — before a call, resolve your and each attendee's DISC type, pin down the goal, and get a DISC-tailored prep note (approach, pacing, agenda). Uses a Google Calendar/Outlook connector to pull invite details if you have one connected; otherwise just asks.
• transcript-analysis skill — paste a call/meeting transcript and get a debrief of what went well and what didn't, grounded in each participant's DISC type. Pairs with premeeting: prep before the call, debrief against that plan after.

Install

The plugin is distributed through its own marketplace (this repo).

# 1. Add the marketplace
/plugin marketplace add crystal-project-inc/crystal-knows-plugin

# 2. Install the plugin
/plugin install crystal-knows@crystal-knows-marketplace

Or run /plugin, open Discover, and pick Crystal Knows.

On first use of a Crystal tool, Claude Code runs the OAuth login flow in your browser to authenticate you against Crystal. No API key to paste.

Using the premeeting skill

Just ask, e.g. "help me prep for my call with..." or "I've got a meeting with [name] tomorrow", or invoke it directly:

/crystal-knows:premeeting

The skill will:

1. Check whether you have a calendar connector available (Google Calendar, Outlook) and offer to pull the invite; otherwise ask who you're meeting and what it's about.
2. Split attendees into internal teammates vs. external attendees, and for external meetings, ask what the account needs (industry/size/stage).
3. Ask for an email or LinkedIn URL for each attendee to resolve DISC types — weighted toward the external, decision-making side of the room.
4. Tag the meeting type (demo / discovery / negotiation / relationship check-in), then propose a few tailored goal options to pick from, tweak, or override with your own — rather than a blank "what's your goal?" prompt.
5. Derive what that goal actually requires from the room, then return a prep note curated around it: adaptation plan, pacing/structure (DISC + meeting type), a draft agenda when it's warranted, a prep checklist, and watch-outs — each tied back to the goal, not just generic DISC/meeting-type advice.

Using the transcript skill

Just ask, e.g. "analyze this call transcript" or "why did this meeting go badly?", or invoke it directly:

/crystal-knows:transcript-analysis

The skill will:

1. Prompt you to paste the transcript.
2. Ask for an email or LinkedIn URL for each participant (needed to resolve DISC types — names alone can only match people already in Crystal).
3. Resolve DISC types via the Crystal MCP multi_search / search tools.
4. Analyze the transcript and report what landed, what didn't, and what to do differently next time — each point tied to transcript evidence and DISC.

If you ran premeeting earlier in the same chat, ask Claude to weigh the debrief against that plan and goal.

Layout

crystal-knows-plugin/
├── .claude-plugin/
│   ├── plugin.json          # plugin manifest
│   └── marketplace.json     # single-plugin marketplace catalog
├── .mcp.json                # Crystal remote MCP server (http + OAuth2)
├── skills/
│   ├── premeeting/
│   │   └── SKILL.md
│   └── transcript-analysis/
│       └── SKILL.md
└── README.md

Pre-configured OAuth (optional, for teams)

The default config lets Claude Code discover Crystal's OAuth server and register dynamically. If you provision a Crystal OAuth client for your org, you can pin it in .mcp.json:

{
  "mcpServers": {
    "crystal": {
      "type": "http",
      "url": "https://api.crystalknows.com/_mcp",
      "oauth": {
        "clientId": "your-client-id",
        "callbackPort": 8080,
        "scopes": ""
      }
    }
  }
}