test-nested-agents_skill

Overview

This skill verifies the nested-agent packaging pattern by testing agents placed under the agents/ folder. It runs checks that a Task tool can invoke a subagent directly or via a relative prompt file. The skill is implemented in JavaScript as a development harness for Plan→Work→Review cycles.

How this skill works

The skill inspects the agents/ directory for test agents (for example, a test-echo-agent) and reads their prompt files. It then executes two verification patterns: direct subagent invocation via Task tool and loading a prompt file by relative path before invoking a general-purpose agent. The run reports successes, failures, and fallback attempts.

When to use it

• Validate that an agent packaged in agents/ can be called by Task tools
• Test fallbacks when direct subagent invocation fails
• Confirm relative-path prompt loading works in development harnesses
• Automated checks in CI to catch integration regressions
• Local debugging while building nested agent features

Best practices

• Keep test agents small and deterministic (e.g., an echo agent)
• Include a clear prompt file (agents/test-echo-agent.md) for the relative-path test
• Run direct and fallback patterns in sequence and report both outcomes
• Log inputs and outputs for each test step to simplify debugging
• Use this skill in CI and as a local pre-merge check

Example use cases

• Run Pattern A: Task tool invokes subagent_type: "test-echo-agent" with a test prompt
• Run Pattern B: Read ./agents/test-echo-agent.md then start a general-purpose Task using that prompt
• CI job that fails the build if neither invocation pattern returns the expected result
• Developer runs the skill locally to confirm packaging changes didn't break agent discovery