agentsclimarketplace

Subagent

Skill alessiomarcone/agent-fieldbook/plugins/knowledge-pack/skills/subagent

Source-backed skills that turn official Claude and Codex training into reliable daily workflows.

Install
npx -y skills add alessiomarcone/agent-fieldbook --skill subagent

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Decides whether selected delegated work needs agents and designs a strict, product-correct subagent contract with isolated context, bounded tools, authority, deliverables, and tests. Use when the user asks to create, configure, delegate to, or troubleshoot Claude or Codex subagents, parallel agents, custom agents, or managed-agent workflows; not for open mechanism comparisons.

SKILL.md

2.7 KB, as published. Nobody here has run it

Subagent

Design the smallest delegated unit that can return a decision-ready handoff.

References

Resolve the product first, then read only its branch:

  • Claude Code: references/claude-code-subagents.md.
  • Anthropic Managed Agents: also read references/managed-agents.md.
  • Codex: references/codex-subagents.md.

Never transfer fields, commands, models, tools, or permission semantics between branches. For a cross-product migration, read both the source and target official references, map intent and constraints, and never map fields by analogy.

Decision gate

Use a subagent only when at least one is true:

  • independent work can proceed in parallel;
  • a separate context prevents noise or context pollution;
  • a specialist needs a different model, tool, or sandbox boundary;
  • the parent needs a compact result rather than the full exploration.

Otherwise return only Verdict and Simpler route, then stop.

Procedure

  1. Identify the exact surface and current supported configuration format.
  2. Define objective, inputs, exclusions, allowed tools, authority, deliverable, and success test.
  3. Default investigations to read-only. Require explicit authority for edits, external messages, publication, or destructive effects.
  4. State what context the child receives, must discover, and must not assume.
  5. Prefer read-heavy parallelism; coordinate agents that share writable state.
  6. Require a handoff with evidence, changes, unresolved risks, and a concise conclusion.
  7. When implementation is requested, verify time-sensitive configuration against current official documentation and validate the file.

Output contract

When the verdict is yes, return:

  1. Verdict — why delegation is warranted.
  2. Contract — objective, inputs, exclusions, tools, and authority.
  3. Prompt/configuration — ready to use for the selected product.
  4. Handoff — exact required return shape.
  5. Tests — normal, boundary, and failure case.

Boundaries

  • Do not invent configuration fields or availability.
  • Do not activate for an open comparison such as “custom agent or skill?”; route mechanism comparisons to navigate.
  • Do not accept “research this” without a decision-ready deliverable.
  • Do not permit silent external side effects.
  • Answer in the user's language.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.