The 6 Skill Slots: What Goes Where
The hex has six slots. Not five, not eight — six. The previous articles in this series covered why the number matters and what the psychological research says about constraints. This article gets practical. What does each slot represent, what kind of tool fills it, and how do you decide which specific tool earns each position in your hex. This is not a tool recommendation list. It's a structural framework — the slots are universal, the tools you put in them are yours.
The Slot Framework
Every knowledge worker's week — whether you're a writer, a marketer, a consultant, a developer, or a small business owner — runs on the same six categories of work. You think. You write or publish. You communicate with other humans. You automate repetitive tasks. You store and retrieve information. You create media. Not everyone does all six in equal proportion, and your hex should reflect what you actually do, not what a productivity blog says you should do. But these six categories cover the territory.
The slots aren't ranked. Slot 1 is not more important than Slot 6. The numbering is for reference, not priority. Your most important slot might be the creation tool if you're a designer, or the automation tool if you run operations, or the communication tool if you're in sales. The hex adapts to your work. You don't adapt your work to the hex.
Slot 1: The Thinking Tool
This is where you reason, brainstorm, draft, analyze, and make decisions with AI assistance. For most people in 2026, this slot is an LLM — Claude, GPT, Gemini — and the choice comes down to which model you think with best. Not which model benchmarks highest. Which model you personally produce the best work with.
The thinking tool is the center of the hex because it's the one that orchestrates the others. When Claude has MCP access to your other five tools, your thinking tool becomes your command center. You don't switch between six apps — you talk to one, and it reaches into the other five on your behalf. This is the architectural advantage of building a hex on top of MCP rather than just maintaining a list of apps.
The evaluation question for Slot 1 is simple: "When I sit down to work through a hard problem, which tool do I open first?" If the answer is Claude, Claude goes in Slot 1. If the answer is GPT, GPT goes in Slot 1. If the answer is "I open a blank doc and think with my own brain" — that's valid too, but then your thinking tool is your text editor, and this slot functions differently. The hex doesn't prescribe. It asks you to name what you already do and then make it intentional.
Slot 2: The Writing and Publishing Tool
This is where content goes from draft to published. For a blogger, it might be Ghost or WordPress. For a newsletter writer, it might be Substack or Kit. For someone who publishes internal documents, it might be Google Docs or Notion. The key criterion isn't which platform is "best" — it's which platform is the final destination for your work product.
The distinction between "writing tool" and "publishing tool" matters. Many people write in one place and publish in another — drafting in Obsidian, publishing in Ghost, for example. Your hex slot goes to the publishing tool, not the drafting tool, because the publishing tool is where the output happens. If your drafting happens inside your Slot 1 thinking tool (which it probably does if your thinking tool is Claude), then the publishing tool is the only writing-specific slot you need.
The MCP test is especially relevant here. If your publishing platform has an MCP connector — meaning Claude can create posts, update metadata, manage tags, and publish directly — that platform earns the slot more easily than one that requires you to copy-paste from a Claude conversation into a web editor. Ghost, for example, has robust MCP support. Claude can create a draft, set the featured image, add tags, assign it to a newsletter, and publish — without you opening the Ghost admin panel. That integration isn't a nice-to-have. It's the difference between a tool in your hex and a tool in your browser tabs.
Slot 3: The Communication Tool
Email, messaging, or whatever pipe carries your words to other humans. For most people, this is Gmail. For some, it's Slack. For others, it might be a CRM that handles client communication. The communication tool is the slot that connects your hex to the outside world — everything else in the hex is between you and your tools. This slot is between you and people.
The communication slot tends to be the one people underestimate. They think of email as the chore — the thing that interrupts real work. But for many knowledge workers, email is the work. Client responses, project updates, proposals, follow-ups — the output of your week is often measured by what you sent, not just what you published. Making this slot functional means Claude can draft responses, search for specific threads, summarize unread messages, and send emails on your behalf. That's not automation for automation's sake. That's reclaiming hours.
Gmail through MCP works well right now — Claude can search, read, draft, and send. Slack connectors exist but vary in quality depending on the implementation [VERIFY — Slack MCP connector maturity as of early 2026]. If your communication happens primarily on a platform without MCP support, you have a choice: keep it in the hex as a manual-bridge tool (you copy-paste between Claude and the platform), or swap it for a communication channel that does have MCP support. Neither choice is wrong. The hex accommodates manual bridges. It just works better when the pipes are connected.
Slot 4: The Automation Tool
This is where things run without you. Scheduled workflows, triggered actions, background processes — the tool that does work while you're doing other work. For many hex users, this is n8n. For others, it's Zapier or Make. For developers, it might be cron jobs and shell scripts. The automation tool is the slot that turns your hex from "a set of tools I use" into "a system that works on my behalf."
The automation slot is where the hex framework intersects most directly with the MCP architecture. An n8n workflow can trigger Claude via API, and Claude can use its MCP connections to execute multi-tool tasks — checking your email for new client inquiries, drafting a response, adding the client to your CRM, and scheduling a follow-up. That chain runs on a schedule. You don't touch it. The automation tool is the slot that makes the hex a machine rather than a toolkit.
The evaluation criteria for this slot are different from the others. You're not asking "which tool do I enjoy using?" You're asking "which tool runs reliably when I'm not looking?" Reliability matters more than features here. An automation platform with fifty integrations that breaks weekly is worse than one with ten integrations that runs without intervention. The best automation tool is the one you forget about because it just works.
If you don't currently have any automated workflows — nothing running on a schedule, nothing triggered by an event — this slot can stay empty. A hex with five tools and one empty slot is better than a hex with six tools where one is aspirational. Fill this slot when you have a workflow that's genuinely ready to run unattended.
Slot 5: The Data and Knowledge Tool
This is where you store and retrieve what you know. Files, notes, databases, reference material — the tool that holds the information your other tools draw from. For some people, this is their local filesystem. For others, it's Notion or Obsidian. For data-heavy workers, it might be a SQLite database or Airtable.
The knowledge tool is the hex's memory. Without it, every work session starts from scratch — you have to re-explain context, re-find documents, re-locate the information you need. With it, Claude can pull from your stored knowledge without you pointing it to specific files every time. "Check my project notes for the client requirements we agreed on last month" only works if your project notes are in a tool Claude can access through MCP.
File system access through MCP is the simplest and most reliable version of this slot. Claude can read and write files on your machine natively, which means a well-organized folder structure is already a functional knowledge tool. You don't need a fancy knowledge management platform if a folder tree does the job. The question is whether your information is structured enough for Claude to find what it needs, and whether the volume is low enough that file system search is sufficient. For most individual knowledge workers, it is.
Google Drive is the second most common choice for this slot — strong MCP support, familiar interface, built-in collaboration if you work with others. Notion has MCP connectors available but the integration depth varies [VERIFY — Notion MCP connector current state]. SQLite works if your data is structured and you're comfortable with queries. The choice depends on what "knowledge" looks like in your work. If it's documents and notes, filesystem or Drive. If it's structured records, a database. If it's a mix, pick the one that covers the majority and handle the rest manually.
Slot 6: The Creation Tool
This is the media production slot — images, audio, video, design. For content creators, this might be an image generation tool like GPT's image model or Midjourney. For podcasters, it might be ElevenLabs. For video creators, it might be a video generation or editing tool. For people who don't produce media, this slot might stay empty.
The creation slot is the one most likely to be influenced by the demo trap. Image generation demos are spectacular. Video generation demos are mesmerizing. The temptation is to fill this slot with whatever produced the most impressive demo — but the evaluation criterion isn't "which tool makes the coolest output." It's "which tool makes the output I actually need for my work, reliably, at the quality I need."
For most hex users, the creation tool is image generation. You need featured images for blog posts, social media graphics, or presentation visuals — and a tool that can generate those through MCP, triggered by Claude, integrated into your publishing workflow. GPT's image generation through MCP works well for this. Claude can request an image, receive it, and attach it to a post in your publishing tool — all in one conversation. That kind of integration matters more than which model produces the most photorealistic hands.
If you don't produce media as part of your regular work, leave this slot empty or repurpose it. The hex framework says you have six slots. It doesn't say you have to fill all six. A hex with five active skills and one empty slot is honest. A hex with six skills where one is "I'll use this someday" is a collection, not a system.
The Decision Framework
For each slot, run two tests.
The MCP test: "Can Claude use this tool without me copy-pasting between tabs?" If yes, the tool fits the hex architecture. If no, it can still go in a slot, but you're accepting a manual bridge that reduces the system's value. Tools with MCP connectors are worth choosing over marginally better tools without them.
The Monday morning test: "Would I actually use this tool on a Monday morning when I'm behind on work?" If the answer is yes, the tool belongs. If the answer is "I'd use it if I had time" or "I'd use it for fun projects on weekends" — that tool is a hobby, not a hex component. Hobbies are fine. They just don't get a slot.
When you can't decide between two tools for a slot, pick the one you've used more recently. Familiarity compounds. The tool you already know has a two-month head start over the tool you'd have to learn, and two months of fluency is worth more than a 15% feature advantage. You can always swap later. The hex is a living system, not a tattoo.
This is part of CustomClanker's Hex Explained series — you downloaded the hex, here's context.