5 Underrated Claude Plugins (Part 3)

A plugin turns Claude into a specific kind of worker. It bundles skills, commands and connections to your tools, so instead of a blank chat you get a helper that knows one job well.

Plugins are on every paid plan (Pro, Max, Ultra, Team and Enterprise) and work in regular chat, Claude Desktop and Cowork. Install steps are at the bottom. This is Part 3, so here are five more that most people never touch.

Connect your workspace and Claude reads the channels and conversations you have access to, so "what did I miss" takes seconds instead of an hour of scrolling. It hands back the decisions, the action items and anything with your name on it, and it can draft standups and announcements too.

Best for:

Monday catch-up: everything you were tagged in, with decisions and action items pulled out.
Decision hunting: find where a call was made and who signed off, without scrolling weeks back.
Meeting prep: a week of a busy channel turned into a one-screen brief.

Pro Move

Pair it with Enterprise Search (number 04), which can search Slack alongside your email and docs, so one question covers every tool. On a work account, your Slack admin may need to approve the connection first.

Slack Catch-Up

You are my chief of staff inside Slack. Use the Slack connection to review the channels and conversations I have access to from the last [7] days. Focus on: [list the channels or projects that matter most, or say "everything I'm in"]. 1. Summarize what I missed, grouped by project, not by channel. 2. Pull out every decision that was made, who made it, and a link to the message. 3. List every action item assigned to me or mentioning me, with the channel and a link, sorted by urgency. 4. Flag anywhere someone asked me a direct question and I never replied. 5. End with the 3 things I should handle first today and why. FORMAT: Short bullets under clear headers, no long paragraphs. RULES: Only report what's actually in the messages. If something is unclear, say so instead of guessing. Do not post, reply, or react to anything in Slack. Draft any replies here for me to review.

The Data plugin turns numbers into something you can act on. Upload a spreadsheet or CSV and it explores the data, builds charts and interactive dashboards, and explains what changed. If your company has a data warehouse like Snowflake, BigQuery or Databricks, it can connect and write the SQL for you.

Best for:

Monthly numbers: drop in sales or expenses and get a dashboard plus a plain-English read on what changed.
The why question: what’s driving the numbers and what to do next.
Board and investor updates: one clean chart and a three-line takeaway.

Pro Move

Stop asking for "insights," which gets you a generic recap. Ask it to rank what changed most versus last period and why, and to flag anything that looks like an error in your data first. Before you share anything, run its /validate command to sanity-check the analysis.

Data Analyst

You are my data analyst. Here is my data: [upload the file, paste the export, or name the connected source and table]. It covers [what it is, like monthly sales by product], and the question I care about is [your question]. 1. Sanity-check it first. Flag rows that look like errors, duplicates, missing values, or odd gaps, and tell me before you analyze. Ask me how to handle them if it matters. 2. Build a clean dashboard of the 4 to 6 metrics that matter most for this kind of data. 3. Rank the top 3 things that changed most versus the last period. For each, give the number, the likely driver, and how confident you are. 4. Tell me one thing in here I probably haven't noticed but should. 5. End with 3 specific actions, in priority order. FORMAT: The dashboard as a file I can open, then a summary someone with zero context could follow in under a minute. RULES: Show your math for every number you quote. Label anything that's a guess about cause as a guess, not a fact.

Install the Design plugin and connect Figma, and Claude reads the actual design file instead of a screenshot. Its /handoff command writes developer-ready specs (measurements, spacing, tokens and every component state), and /critique and /accessibility catch problems before anyone builds.

Best for:

Clean handoff: exact tokens, spacing and states instead of a screenshot and a paragraph.
Catching problems early: missing states, inconsistent spacing and contrast issues.
UX copy: error messages, empty states and button text that sound like your brand.

Pro Move

Want starter code too? Figma makes its own Figma plugin for Claude Code that turns a frame into front-end code. Then feed the handoff into Product Management (number 05) so the PRD and the design come from the same spec.

Design Handoff

Act as the bridge between my designer and my developer. Here is the Figma frame: [paste the Figma link, or attach a screenshot if Figma isn't connected]. It's for [what the screen is and who uses it], built in [our stack, like React and Tailwind]. 1. Audit the design first. Flag anything inconsistent, any missing states (hover, empty, error, loading, disabled), and anything that drifts from the rest of our design system. 2. Write a full developer handoff: layout and measurements, spacing, color and type tokens, every component and its states, interactions, and responsive behavior. 3. Check accessibility: color contrast, tap target sizes, and anything a screen reader would trip on. 4. List the open questions a developer would hit mid-build, so we answer them now. FORMAT: Sections I can paste straight into a ticket, with tokens and values in tables. RULES: Only use values you can actually read from the file. If something isn't specified in the design, list it under open questions instead of inventing it.

When your work is scattered across a dozen apps, this one finds anything in a single question. Enterprise Search searches all your connected tools at once (email, Slack, docs, wikis, project trackers) and pulls the answer together with the source for each part. Its /digest command gives you a daily or weekly roundup across everything.

Best for:

"Where did we land on this?" The final answer plus where it was decided.
Handovers: everything about a client or project pulled into one brief.
The lost doc: the thread or email you know exists but can’t find.

Pro Move

Always make it cite the source for every claim so you can click straight to it. Then hand what it found to Data to chart it, or to Product Management to turn it into a doc. The more tools you connect, the more complete the answers get.

Search Everything

Search every tool I have connected (email, Slack, docs, wikis, trackers) and answer this: [your question]. The time range that matters is [for example, the last 3 months]. 1. Give me the single current answer, not a pile of snippets. 2. For every claim, cite where it came from (which tool, which doc or thread, and the date) with a link I can click. 3. If sources disagree or something looks outdated, tell me which is most recent and flag the conflict. 4. List anything important that seems missing or undocumented, so I know the gaps. 5. End with a short summary I can drop into a message or a doc. RULES: Only use what you find in my connected tools. If you can't find something, say "not found" and tell me which tools you searched. Don't fill gaps with general knowledge.

This handles the writing-heavy parts of the PM job, like specs and PRDs, roadmaps, stakeholder updates, competitive briefs and user research synthesis. It connects to the tools PMs already use (Linear, Jira, Asana, Notion, Figma, Amplitude and more), so the work is grounded in your real context.

Best for:

The blank-page PRD: a rough problem turned into goals, user stories and success metrics.
Research synthesis: a pile of interview notes collapsed into the themes that matter.
Stakeholder updates: the weekly status note, pulled from your connected tools.

Pro Move

Run the front of the job in one pass. Have it synthesize the research first, then write the PRD from those themes, so the spec traces back to what users actually said. Use Enterprise Search to gather the context and Design to keep the spec matched to the file.

Research To PRD

Act as my senior product manager. Here is the problem: [describe it in a few sentences]. Here is my raw user research: [paste interview notes, survey results or support tickets, or point to the connected docs]. My assumption going in is [what you think the answer is]. 1. Synthesize the research first. Give me the top 3 themes, each with a real quote or data point behind it, and call out anything that contradicts my assumption. 2. Write a PRD from those themes: problem, goals, user stories, scope, out of scope, success metrics, and open questions. 3. Pressure-test it. What's the riskiest assumption, and what's the smallest thing we could ship to learn fast? 4. Suggest a priority order and tell me what to cut if I only had half the time. FORMAT: Clear headers, short sections, ready to drop into a planning doc. RULES: Every theme must trace back to something in the research I gave you. Don't invent quotes, users, or numbers. If the research is too thin to support a conclusion, say so.

Open Customize

In Claude, click Customize in the left sidebar. It’s being renamed Plugins, so look for either name.

Find the plugin

Open the Plugins tab, then Discover, and search for the plugin by name.

Add and connect

Click Add. If it uses a tool like Slack, Figma or a data warehouse, connect that account once, then start asking. Typing / in a chat shows the plugin’s commands.

(Claude’s plugin help page · browse the plugin directory)

Where To Start

Pick the one that matches where your work piles up. Drowning in messages, start with Slack. Buried in tabs, try Enterprise Search. Living in spreadsheets, go with Data. You can add the rest later.

5 UnderratedClaude Plugins

5 Underrated
Claude Plugins