How do I install the Test Workflow Multi skill?

Run npx skillmds@latest add majiayu000/test-workflow-multi 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.

What does the Test Workflow Multi skill do?

Tests workflow continuation with MULTIPLE sequential child skill calls It is listed under Productivity on SkillMD.

Is Test Workflow Multi safe to use?

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

Which AI agents work with Test Workflow Multi?

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 Test Workflow Multi free to use?

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

Who published Test Workflow Multi?

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

Test Workflow Multi by majiayu000 — Agent Skill

Name: Test Workflow Multi
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Multi-Child Workflow Continuation Test

RIGOROUS TEST: Parent calls multiple children in sequence, with work between each.

Steps (Execute ALL in strict sequence)

Step 1: Initial marker

Write to earnings-analysis/test-outputs/workflow-multi-step1.txt:

MULTI_STEP1
Timestamp: [ISO timestamp]
Starting multi-child workflow test

Step 2: Call FIRST child

Invoke: /test-workflow-child Store return value as CHILD1_RESULT.

Step 3: Post-first-child marker (CRITICAL TEST 1)

Write to earnings-analysis/test-outputs/workflow-multi-step3.txt:

MULTI_STEP3_AFTER_CHILD1
Timestamp: [ISO timestamp]
First child returned: [CHILD1_RESULT]
Continuing to second child...

Step 4: Call SECOND child

Invoke: /test-workflow-child again Store return value as CHILD2_RESULT.

Step 5: Post-second-child marker (CRITICAL TEST 2)

Write to earnings-analysis/test-outputs/workflow-multi-step5.txt:

MULTI_STEP5_AFTER_CHILD2
Timestamp: [ISO timestamp]
Second child returned: [CHILD2_RESULT]
Both children completed, workflow still running!

Step 6: Read child's file and do computation

Read: earnings-analysis/test-outputs/workflow-child.txt Count characters in the file.

Step 7: Final summary

Write to earnings-analysis/test-outputs/workflow-multi-final.txt:

MULTI_WORKFLOW_COMPLETE
Timestamp: [ISO timestamp]

=== MULTI-CHILD WORKFLOW TEST RESULTS ===

Step 1 (before any child): EXECUTED
Step 2 (call child 1): EXECUTED
Step 3 (after child 1): EXECUTED - proves continuation after 1st child
Step 4 (call child 2): EXECUTED
Step 5 (after child 2): EXECUTED - proves continuation after 2nd child
Step 6 (read & compute): EXECUTED
Step 7 (this file): EXECUTED

Child 1 return value: [CHILD1_RESULT]
Child 2 return value: [CHILD2_RESULT]
Child file character count: [count]

ALL 7 STEPS COMPLETED.
GitHub Issue #17351 does NOT affect multi-child sequential workflows.

Expected Files If Working

workflow-multi-step1.txt
workflow-child.txt (from child)
workflow-multi-step3.txt (CRITICAL - after 1st child)
workflow-multi-step5.txt (CRITICAL - after 2nd child)
workflow-multi-final.txt

If bug exists at any point, subsequent files won't be created.

---name: test-workflow-multidescription: Tests workflow continuation with MULTIPLE sequential child skill calls--- # Multi-Child Workflow Continuation Test **RIGOROUS TEST**: Parent calls multiple children in sequence, with work between each. ## Steps (Execute ALL in strict sequence) ### Step 1: Initial marker Write to `earnings-analysis/test-outputs/workflow-multi-step1.txt`: ``` MULTI_STEP1 Timestamp: [ISO timestamp] Starting multi-child workflow test ``` ### Step 2: Call FIRST child Invoke: `/test-workflow-child` Store return value as CHILD1_RESULT. ### Step 3: Post-first-child marker (CRITICAL TEST 1) Write to `earnings-analysis/test-outputs/workflow-multi-step3.txt`: ``` MULTI_STEP3_AFTER_CHILD1 Timestamp: [ISO timestamp] First child returned: [CHILD1_RESULT] Continuing to second child... ``` ### Step 4: Call SECOND child Invoke: `/test-workflow-child` again Store return value as CHILD2_RESULT. ### Step 5: Post-second-child marker (CRITICAL TEST 2) Write to `earnings-analysis/test-outputs/workflow-multi-step5.txt`: ``` MULTI_STEP5_AFTER_CHILD2 Timestamp: [ISO timestamp] Second child returned: [CHILD2_RESULT] Both children completed, workflow still running! ``` ### Step 6: Read child's file and do computation Read: `earnings-analysis/test-outputs/workflow-child.txt` Count characters in the file. ### Step 7: Final summary Write to `earnings-analysis/test-outputs/workflow-multi-final.txt`: ``` MULTI_WORKFLOW_COMPLETE Timestamp: [ISO timestamp] === MULTI-CHILD WORKFLOW TEST RESULTS === Step 1 (before any child): EXECUTED Step 2 (call child 1): EXECUTED Step 3 (after child 1): EXECUTED - proves continuation after 1st child Step 4 (call child 2): EXECUTED Step 5 (after child 2): EXECUTED - proves continuation after 2nd child Step 6 (read & compute): EXECUTED Step 7 (this file): EXECUTED Child 1 return value: [CHILD1_RESULT] Child 2 return value: [CHILD2_RESULT] Child file character count: [count] ALL 7 STEPS COMPLETED. GitHub Issue #17351 does NOT affect multi-child sequential workflows. ``` ## Expected Files If Working 1. workflow-multi-step1.txt 2. workflow-child.txt (from child) 3. workflow-multi-step3.txt (CRITICAL - after 1st child) 4. workflow-multi-step5.txt (CRITICAL - after 2nd child) 5. workflow-multi-final.txt If bug exists at any point, subsequent files won't be created.

Frequently asked questions

Test Workflow Multi