Skills, not a swarm of agents

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 the Croft 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 the Croft 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.

Add Croft to Cursor →  ·  About the plugin →

More from the blog