How do I install the Subagents skill?

Run npx skillmds@latest add waishnav/subagents in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Subagents safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Subagents?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Subagents free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Subagents?

Waishnav (@waishnav) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Subagents by waishnav — Agent Skill

Name: Subagents
Author: Waishnav

File contents

DevSpace subagents

Subagents are optional. Use the normal workspace tools for routine work; delegate only when a separate worker materially helps through independent context, specialization, or follow-up.

Run the DevSpace CLI through the shell or process tool from the project the subagent should use. Agent commands print compact XML fragments by default. Read that output directly. Do not add --json.

Choose a target

Discover usable targets instead of guessing names:

devspace agents targets

Each line is a <provider name="..."/> or <profile name="..." provider="...">description</profile> fragment. Pass the profile or provider name as <profile-or-provider>. Prefer a matching profile. Use a provider target when no profile fits or the task needs a specific provider. Keep the configured model and effort unless the task requires a supported override.

Start work

Give the subagent a self-contained brief with the objective, relevant paths, constraints, context it cannot infer, and the expected result. The subagent receives this brief and its profile instructions, not the parent conversation.

devspace agents run <profile-or-provider> "<brief>"
devspace agents run <profile-or-provider> --model <model> --effort <effort> "<brief>"

The command returns an <agent id="agt_..." status="running"/> receipt. Keep the DevSpace agent ID for inspection, waiting, or follow-up.

Wait or inspect

Use wait when work must finish before you proceed. One call can wait for several agents:

devspace agents wait <id>
devspace agents wait <id> <id> <id>
devspace agents wait <id> <id> --timeout 60

Without --timeout, the command waits until every named agent's current work finishes. A timeout returns one fragment per unique agent in first-seen order; unfinished work has status="running" wait="timeout". Completed output is the element text. Failures include code and retryable attributes. The command does not stream partial results.

Use show for an immediate snapshot. Do not poll it when wait can express the dependency.

devspace agents show <id>
devspace agents ls

ls lists agents for the current project. Empty targets and ls results print nothing.

Continue related work

Continue an agent when its existing provider context helps. Start another agent for unrelated work.

devspace agents continue <id> "<follow-up brief>"
devspace agents wait <id>

Good uses

Review a change for correctness, security, or missing tests.
Investigate a bounded part of a codebase and report findings.
Implement one isolated change with clear acceptance criteria.
Run a focused verification pass after other work.

---name: subagentsdescription: Delegate focused coding, research, review, or verification work to a bounded DevSpace subagent. Use when a task benefits from separate context, a specialist perspective, or a follow-up with the same worker.---# DevSpace subagentsSubagents are optional. Use the normal workspace tools for routine work; delegate only when a separate worker materially helps through independent context, specialization, or follow-up.Run the DevSpace CLI through the shell or process tool from the project the subagent should use. Agent commands print compact XML fragments by default. Read that output directly. Do not add `--json`.## Choose a targetDiscover usable targets instead of guessing names:```bashdevspace agents targets```Each line is a `<provider name="..."/>` or `<profile name="..." provider="...">description</profile>` fragment. Pass the profile or provider `name` as `<profile-or-provider>`. Prefer a matching profile. Use a provider target when no profile fits or the task needs a specific provider. Keep the configured model and effort unless the task requires a supported override.## Start workGive the subagent a self-contained brief with the objective, relevant paths, constraints, context it cannot infer, and the expected result. The subagent receives this brief and its profile instructions, not the parent conversation.```bashdevspace agents run <profile-or-provider> "<brief>"devspace agents run <profile-or-provider> --model <model> --effort <effort> "<brief>"```The command returns an `<agent id="agt_..." status="running"/>` receipt. Keep the DevSpace agent ID for inspection, waiting, or follow-up.## Wait or inspectUse `wait` when work must finish before you proceed. One call can wait for several agents:```bashdevspace agents wait <id>devspace agents wait <id> <id> <id>devspace agents wait <id> <id> --timeout 60```Without `--timeout`, the command waits until every named agent's current work finishes. A timeout returns one fragment per unique agent in first-seen order; unfinished work has `status="running" wait="timeout"`. Completed output is the element text. Failures include `code` and `retryable` attributes. The command does not stream partial results.Use `show` for an immediate snapshot. Do not poll it when `wait` can express the dependency.```bashdevspace agents show <id>devspace agents ls````ls` lists agents for the current project. Empty `targets` and `ls` results print nothing.## Continue related workContinue an agent when its existing provider context helps. Start another agent for unrelated work.```bashdevspace agents continue <id> "<follow-up brief>"devspace agents wait <id>```## Good uses- Review a change for correctness, security, or missing tests.- Investigate a bounded part of a codebase and report findings.- Implement one isolated change with clear acceptance criteria.- Run a focused verification pass after other work.

Frequently asked questions

Subagents