LearnFor sellers4 min read · November 18, 2026

Sigrix basics 3: build an assistant from building blocks

Turn a prompt you already sell into an assistant: connect a skill and MCP servers, yours or another seller's, and see the page your buyers get, filmed in Sigrix itself.

3:43 · captions Download the video
Transcript

What an assistant connects

Sigrix basics, lesson three. You'll see what an assistant connects, attach your building blocks, and see what your buyer gets. In lesson one, Sam listed a prompt that writes cold email openers. Now he'll build it into an assistant that also looks the prospect up and books the call. Prompts and skills are building blocks. Each one sells on its own. An assistant is built from them: it connects them into one listing that a buyer installs once. Sigrix says what it links: prompts, personas, skills and MCP servers. You pick which ones in the editor. Give it a title and a short description, as for any listing. Then price the assistant as a whole: Sam asks $19. Create the draft. Nothing is public yet.

Attach your building blocks

The draft opens in the editor, with its category picked from the description. This box is for a prompt written just for this assistant. Sam doesn't need one: he'll use the prompt he already sells. So he goes on to Building blocks. This diagram shows how it works: a buyer asks, and the assistant calls on its skills, MCP servers and documents only when the job needs them. First, its task. Under your own listings, Sam picks his cold email prompt. Its words become what the assistant does, and it keeps selling on its own page. Next, skills. This list holds every seller's published skills, and your own. Sam adds his invite writer. Your own skills ship inside the assistant. A skill from another seller is sold separately, and your page shows its price. Then MCP servers, for live tools and data. Sam adds his Google Calendar server, to find a free time, and a HubSpot server another seller lists, to look the prospect up. MCP servers run on the buyer's own machine, signed in with their own accounts, and the download carries their setup. Back at the top, the diagram shows the whole assistant: his prompt as its task, his skill, and the two MCP servers. The checklist is complete, so Sam sends it for review. A person at Sigrix reads every listing before it goes live, and every block an assistant links with it.

See what your buyer gets

To see what a buyer will get, open Your page, as a buyer sees it. It's a preview until the assistant is approved. Because it ships a skill and MCP servers, it's built for Claude Code. Further down, buyers see what it's built from: Sam's prompt, his skill, and both MCP servers. Sam's own skill comes with the assistant. And each MCP server links to its own page, with its price and what a buyer needs to set it up. To recap: an assistant connects building blocks into one listing. Use a prompt you already sell as its task, add skills and MCP servers, yours or another seller's, and your page shows buyers what it's built from. That's it: connect the blocks you already have, and sell them as one assistant.

What you will see

  • What an assistant connects. Publish: prompts, skills and MCP servers are building blocks, and an assistant connects them into one listing that a buyer installs once.
  • Attach your building blocks. The editor's Building blocks step: a prompt you already sell as the assistant's task, a skill of your own, and two MCP servers, one of them another seller's.
  • See what your buyer gets. Your page as a buyer sees it: what the assistant is built from, which skills come with it, and what each MCP server costs and asks of the buyer.

Good to know

  • Skills and MCP servers can come from any seller: the lists hold every published one, and yours. A prompt or a persona must be one of your own listings.
  • Your own skills ship inside the assistant's download. A skill from another seller is sold separately, and your page shows its price.
  • MCP servers run on the buyer's own machine, signed in with the buyer's own accounts, and the download carries their setup.
  • A person at Sigrix reviews the assistant, and every block it links, before it goes live.

Start from the publishing page, or read how an assistant is built and sold.

What is real, and what is scripted

The sellers, listings, reviews and sales in these lessons are made for the recording, on a copy of Sigrix running on one computer. Where a lesson pays, it pays on real Stripe Checkout in Stripe's test mode, with Stripe's test card, so no money moves. Every page, button and figure on screen is Sigrix's own.

Written by
Sigrix Editorial
Editorial · Marketplace & foundations

We write the playbooks we wish we'd had—field notes from building Sigrix and what the best creators do differently. Reach us at hello@sigrix.io.

0 Comments

Join the discussion. Be kind and stay on topic.

  1. No comments yet — be the first to share what you think.

Keep reading

More from the library

All articles →

Stay in the loop

Sigrix product updates, in your inbox.

  • One email each time a major update to Sigrix goes live
  • A link to read it on the Hub
  • One-click unsubscribe, no noise