cd /news/ai-agents/skills-not-a-swarm-of-agents · home topics ai-agents article
[ARTICLE · art-138795] src=oncroft.net ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

Skills, not a swarm of agents

Croft published a blog post on September 5, 2026 arguing that a single AI assistant with tools and loadable skills outperforms a swarm of specialist subagents for building internal apps, citing Claude's platform team's recommendation for commerce. Croft's approach pairs its MCP server, which gives Cursor and Claude tools to create apps, write files, deploy, read logs and roll back, with an optional plugin that supplies house rules as skills loaded on demand. Croft offers the service at $24/month after a 7-day free trial with no card required.

by read2 min views1 publishedSep 4, 2026
Skills, not a swarm of agents
Image: source

Blog · September 5, 2026 · Rich Chetwynd One assistant with tools and a bit of know-how beats a pile of specialist agents handing a roster between them. That is how Croft talks to Cursor and Claude.

When an assistant has to cover a lot of ground, the tempting design is one subagent per job: a “data” agent, a “UI” agent, a “deploy” agent. Each handoff drops context. Each handoff costs a turn. A conversation about a roster is one session, not a relay race.

The better shape is the one Claude’s platform team has been recommending for commerce: one agent, with skills for the long tail, and tools that call the systems you already run. Croft is that shape for internal apps.

What Cursor actually needs #

You do not want five bots arguing about a stocktake. You want the editor you already live in, pointed at your croft, with two things loaded:

  1. Tools - create the app, write files, deploy, read logs, roll back. That is theCroft MCP server .

  2. Skills - the know-how so the first message builds the right way (private by default, one login, a real database). That is theCroft plugin . The tools are how it acts. The skills are how it remembers the house rules without stuffing them into every prompt. Load a skill when you need it; keep the session in one head.

Subagents still have a place #

A narrow, self-contained job can be a subagent: “go read these logs and come back with the error.” That is delegation. The moment the specialist takes over the conversation, you have handed the user to something that no longer sees the roster, the last deploy, or why you asked.

Croft does not insert an orchestrator in front of you. You talk to Cursor, Claude, ChatGPT, or Grok. They talk to your croft. One loop.

Put the frequent stuff in the prompt #

Anything the assistant needs on most turns belongs up front: this is a private app, behind company login, on this server. The long tail - a particular connector, a particular template - can live in a skill and load when you go there.

That is why Connect Cursor is one click for the tools, and the plugin is optional for the know-how. Start with the tools if you already know what you are building. Add the skills when you want the assistant to build the Croft way from the first message.

Stake out your croft. #

Your team's first app could be live before lunch.

Get your croft 7 days free, no card to start. From $24/month - cancel anytime and take everything with you.

── more in #ai-agents 4 stories · sorted by recency
── more on @croft 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/skills-not-a-swarm-o…] indexed:0 read:2min 2026-09-04 ·