Claude, In Concert

If you install more than one Claude plugin, do you have to tell Claude which one to use for a given task? The natural guess is yes, that you pick a plugin by hand for each job. That guess is wrong, and understanding why points at something more interesting than any single plugin on its own.

How the stack actually works

With several plugins active, Claude infers from context rather than waiting for an explicit selection. The whole stack is available at once, and the request itself decides which layers wake up. Ask a marketing question and the marketing skills switch on; ask a sales question next and the sales plugin engages instead. Change the subject and Claude changes tools, with no announcement required. Ask something that spans both domains, and both contribute, with Claude coordinating across them into one coherent answer built behind the scenes by several specialized skill sets working together. For someone working alone, that feels less like software and more like a bench of specialists on call, an entire team's coverage answering in a single voice. And if you want a specific combination, you can simply name it directly.

Handoff one: research into marketing

Say you're launching a new service and want positioning grounded in reality rather than guesswork. The research skills survey the landscape first: who else is out there, how they position themselves, and where the gaps sit. Those findings then hand off to marketing, which builds positioning aimed directly at the gaps the research just found, value propositions and differentiators pointed at open ground rather than blending into a crowded market. Alone, research hands you intelligence and marketing hands you messaging, but messaging with nothing under it. Together, the message is grounded, which is the real difference between something strategic and something generic.

Handoff two: research into a sales meeting

The same handoff pattern applies to meeting prep. Research digs into a prospect's background, what they build, who their customers are, recent signals, while sales turns that raw material into a brief covering your angle, the objections to expect, and what to lead with. A brief without research behind it is just surface prep. Research without sales framing is intelligence you don't know how to act on. Together, you walk in understanding both the prospect's world and your own opening within it.

Data and support closing the loop

Two more handoffs close a feedback loop rather than opening a new project. Data into marketing feeds months of performance, engagement, traffic, and conversions by piece and by channel, into building next quarter's content calendar around what actually moved the needle. Support into product mines support tickets for the pain points hitting the most people the hardest, turning the top few into buildable specs. Both handoffs share the same underlying shape: measurement feeds making. Without the data, a solo operator plans on instinct; with it, the same creative energy points at work that actually performs.

The highest-stakes handoff: a contract

When a contract lands and it's time to prep for negotiation, two plugins stack on it at once. Sales pulls up the whole relationship, prior conversations, and deal context, while legal reviews the terms against its own risk frameworks and flags clauses unusual for a deal of this size. The two merge into a single negotiation brief covering what to push on, what's standard, and where you're strong. Contract review in isolation misses the business context; sales prep with no legal eye misses the risk stacked into the terms. Combined, neither blind spot survives on its own.

Four habits that keep a stack sharp

One rule holds the whole approach together, expressed as four habits: name the domains you want when you need a specific combination, start simple and get fluent with one plugin before orchestrating several, document the combinations that actually work, and notice the gaps. When a two-plugin flow keeps earning its keep, like prospect research feeding directly into outreach, it's worth writing down, or better, capturing as its own custom plugin that runs from a single command. When you find yourself wishing a combination could do something it currently can't, that's not a dead end so much as a signal that the integration points are still being built.

Key takeaways

• With multiple plugins installed, Claude infers which one to use from the request itself, without requiring an explicit selection each time.
• Research-to-marketing and research-to-sales handoffs both work the same way: research supplies grounded intelligence, and the second plugin turns it into something actionable.
• Data-to-marketing and support-to-product handoffs close a feedback loop, turning measurement into what gets built or planned next.
• A contract review pairs sales context with legal risk analysis into one negotiation brief, covering blind spots neither plugin catches alone.
• Four habits keep a plugin stack useful rather than tangled: name domains explicitly when needed, start simple, document what works, and treat unmet needs as signals rather than dead ends.

Try it yourself

This is a good entry point if you're new to Claude and curious how multiple plugins actually interact rather than compete. Try this prompt directly in Claude: name a real move you're about to make, a launch, a pitch, or a build, and ask it to research the landscape first, hand those findings to marketing to build positioning into the gaps found, and then show you exactly where the combined answer beats either angle working alone. The code for this walkthrough is available in the Humanitarians AI YouTube GitHub repository.