Skills vs Subagents: Why I Decided Against the Upgrade

I almost converted my AI task manager into a “subagent.” Then I thought through the tradeoffs and decided against it.

Here’s my reasoning.

The setup: I have a task-helper that runs every 2 hours. It scans my active task list, picks the highest priority item, does research, writes drafts, and posts updates. Fully autonomous. I figured making it a proper isolated subagent would be an upgrade.

That same task-helper later became one of my favorite examples of an assistant that knows when the work is already done.

So I asked Claude to reason through it.

Its response:

“When task-helper runs as a skill, it inherits your full vault context. A formal subagent starts with a blank context window. It would need all of that explicitly passed in, or it wouldn’t know your vault folder structure, safety rules about outbound comms, which Discord channels to use.”

Then:

“Skills are playbooks an employee has memorized. Subagents are delegating to a specialist in another room.”

And the kicker:

“Converting task-helper to a subagent would be a lateral move with added complexity. The right use for subagents is inside a skill, when you need to do research and drafting in parallel.”

So I kept it as a skill. The skill now spawns subagents internally for parallel work. The skill orchestrates. The subagents execute. Context stays intact.

I’d be curious to hear how you’d have approached it.