← Back to all free guides
A free guide by Mariah Brunner ↗ INSTAGRAM ↗ TIKTOK

5 Underrated
Claude Plugins

Part 2. Five plugins that quietly do real work for you. Here’s what each one does, what it’s best for, and a copy-paste prompt to run today.

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 chat on the web, Claude Desktop and Cowork. Install steps are at the bottom.

01. Brand Voice

Brand Voice is a partner plugin built by Tribe AI. It searches the places your writing already lives (Google Drive, Notion, Slack, Confluence, call and meeting transcripts) and turns your strongest examples into brand guidelines Claude can follow. Then it checks new drafts against them, so what you put out sounds like you.

Best for:

Pro Move

Its three commands run in order. /brand-voice:discover-brand finds your material, /brand-voice:generate-guidelines writes the guide, and /brand-voice:enforce-voice writes or checks content against it. When your sources disagree, it asks you to confirm or override instead of guessing.

Build My Voice Guide
Use the Brand Voice plugin to build my brand voice guide, then check a draft against it. ABOUT ME - Brand or business: [NAME + one line on what you sell and to whom] - Where my best writing lives: [e.g. Google Drive folder "Newsletters", Notion page "Website copy", Slack #marketing] - 3 pieces that sound MOST like me: [paste links or attach] - 1 piece that does NOT sound like me: [paste or attach, optional] STEPS 1. Search those sources and pull my strongest examples (newsletters, landing pages, emails, posts, call transcripts). List what you used. 2. Write a one-page voice guide with: 3 to 5 voice pillars, a "We are / We are not" table, words and phrases I use, words I never use, and how my tone shifts for a sales email vs a social post vs a customer reply. 3. If my sources contradict each other, list the conflicts as open questions with your recommendation, so I can confirm or override. 4. Check the draft below against the guide. Quote every line that sounds off, say why, and give a rewrite in my voice. DRAFT TO CHECK [PASTE DRAFT] RULES - Build the rules only from my real content. Don't invent a personality I don't have. - Keep the guide to one page so I'll actually use it.
02. PDF Viewer

This one feels illegal. PDF Viewer opens a PDF in a live, interactive viewer inside Claude, so you can work on it instead of only reading it. Mark up a contract, fill a form with a live preview, stamp it APPROVED, place your signature, then download the finished copy.

Best for:

Pro Move

The commands are /pdf-viewer:open, /pdf-viewer:annotate, /pdf-viewer:fill-form and /pdf-viewer:sign. Two catches. It runs a small server on your computer, so use it in Cowork or Claude Code, not web chat. And the signature is a picture on the page, not a legally certified e-signature, so use a real signing service for anything binding.

Fill And Review A PDF
Use the PDF Viewer plugin to open the attached PDF in the interactive viewer and help me finish it. THE DOCUMENT - What it is: [e.g. freelance contract, rental application, vendor form] - My details to fill in: [name, company, address, date, anything else] - What I need: [fill the form / mark up the contract / stamp it APPROVED / place my signature] STEPS 1. Open it in the viewer and give me a 5-line summary: what it is, who the parties are, key dates, money, and anything I'm agreeing to. 2. Walk through it section by section. Highlight anything unusual or one-sided (auto-renewals, cancellation fees, liability, exclusivity, payment terms) and add a short note on each. Let me review each batch before you move on. 3. Fill in the fields with my details and show me the live preview. Leave anything you're unsure of blank and list it. 4. When I approve, help me place my signature or initials, then tell me how to download the finished copy. RULES - Don't change any of the document's own wording. - You're not my lawyer. Flag anything that looks risky and tell me when it's worth a professional review.
03. Design

Design is a second set of expert eyes. It critiques your mockups, writes the UX copy inside a product (buttons, errors, empty states), runs accessibility checks, synthesizes user research, and writes developer handoff specs so the work moves cleanly into build.

Best for:

Pro Move

Ask for problems ranked by how much they hurt the one action the screen must drive. You get a priority list instead of 30 nitpicks. Connect Figma and it reads the real file instead of a screenshot (more on that in Part 3).

Design Review
Use the Design plugin to review the attached screen like a senior product designer. CONTEXT - What this screen is: [e.g. checkout page for my skincare store] - Who uses it: [audience + device, e.g. mostly mobile shoppers, 25 to 45] - The one action it must drive: [e.g. complete purchase] - Brand voice in 3 words: [e.g. warm, simple, confident] DO THIS IN ORDER 1. Critique: the top 5 problems ranked by how much they hurt the main action. For each, what's wrong, why it matters, and the fix. 2. UX copy: rewrite the headline, buttons, form labels, error messages and empty states in plain language and my brand voice. Show a before/after table. 3. Accessibility: check against WCAG 2.1 AA (contrast, text size, tap targets, labels, focus order). List each issue with severity and the fix. 4. Handoff: a short checklist for my developer with every component state (default, hover, error, loading, disabled), spacing and any assets they'll need. RULES - Be specific. Point to the exact element, never "improve the layout." - If you can't see something (like hover states), say so instead of guessing.
04. Operations

Operations runs your back office. It documents processes as clear SOPs with decision points, compares vendor proposals, plans team capacity and hiring needs, and writes runbooks, risk assessments, change plans and status reports.

Best for:

Pro Move

Brain-dump the process the way you actually do it, rough notes and all. Then ask it to find the 3 most likely failure points and which role hits its limit first as you grow. That turns a document into a plan.

SOP Plus Capacity Check
Use the Operations plugin to document one of my processes as an SOP and stress-test it. THE PROCESS - Name: [e.g. client onboarding] - Starts when: [e.g. client signs the contract] - Ends when: [e.g. kickoff call is done] - Who's involved: [roles, e.g. me, my VA, a designer] - Tools used: [e.g. Gmail, Notion, Calendly, Stripe] - How it works today, rough notes are fine: [BRAIN-DUMP THE STEPS] STEPS 1. Write a clear SOP: numbered steps, an owner for each, the tool used, and how long it should take. Mark every decision point as "If X, then Y." 2. Add a "What goes wrong" section: the 3 most likely failure points and how to catch them early. 3. Capacity check: we handle [NUMBER] clients a month now. Tell me where this breaks if we add [NUMBER] more next quarter, which role hits its limit first, and whether that means a hire, a tool, or a process change. 4. Give me the top 3 steps to automate or cut, with the time saved per month. OUTPUT The SOP as a clean document I can hand to a new hire, then the capacity check and quick wins below it. RULES - Use only what I told you. List anything you had to assume.
05. Customer Support

Customer Support keeps your inbox calm. It triages tickets, researches answers across your connected tools, drafts replies, packages escalations for the right person, and turns solved tickets into help-center articles, so the same question stops coming back.

Best for:

Pro Move

Connect your support platform, CRM and help center for the best results, or paste tickets in by hand. Give it your refund and shipping policies up front so drafts never promise something you don’t offer.

Clear The Queue
Use the Customer Support plugin to clear my support queue and stop repeat questions. MY SETUP - Business: [what you sell + who your customers are] - My tone with customers: [e.g. friendly, quick, never corporate] - Policies to follow: [refunds, shipping times, returns window, anything customers ask about] - Who handles escalations: [e.g. me for refunds over $100, my developer for bugs] - Tickets: [connect your support tool, or paste or attach today's open tickets] STEPS 1. Triage: sort every ticket into Urgent, Today, or Can Wait, with a category (billing, shipping, bug, how-to, other) and one line on why. 2. Draft a reply to each one in my tone, using only my policies. Mark any reply where you weren't sure of the answer. 3. Escalate: for anything that needs someone else, write a short brief with the customer, the issue, what's been tried, and what's needed. 4. Find the 3 questions that came up most and write a help-center article for each (title, short answer, step-by-step, related questions). RULES - Never promise refunds, credits or dates my policies don't cover. - Drafts only. I review and send every reply myself.
How To Install A Plugin

01

Open Customize

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

02

Find the plugin

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

03

Add and connect

Click Add. If it uses a tool like Google Drive, Notion or your help desk, connect that account once, then start asking. Typing / in a chat shows the plugin’s commands. Plugins you add also show up in Claude Code when you sign in with the same account.

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

Where To Start

If you only try one, start with Customer Support. It gives you time back on day one and keeps paying off as your help-center articles pile up. Run a creator-heavy business instead? Brand Voice is the one to add first.