Automated summary

This skill acts as a mock orchestrator for a four-layer thinking-capture test, calling prediction and attribution skills and recording results in files.

Strengths

Explicitly describes the four tested layers and expected output files.
Chains two child skills and asks for a summary of their returns.
Separates initial reasoning and final synthesis into distinct files.

Limitations

It is a mock test harness with no real financial-analysis business logic.
It depends on the /mock-prediction and /mock-attribution skills and on hardcoded paths.
It provides no automated result validation, only output files.

When to use it

Use it to verify thinking-token capture and nested skill orchestration in Claude Code.

When not to use it

Do not use it for real financial analysis or production orchestration.

Security analysis

Safe

Quality score78/100

The skill only uses Read, Write, and Skill tools to create test output files and invoke two named mock child skills. There are no network calls, shell commands, destructive operations, secret exfiltration, or obfuscated payloads. The declared allowed tools match the documented behavior.

No concerns found

How this analysis is made

Examples

Verify four-layer orchestration

Run the mock-orchestrator, call /mock-prediction then /mock-attribution, and report whether mock-orchestrator-reasoning.txt and mock-orchestrator-final.txt were created under earnings-analysis/test-outputs.

Audit reasoning capture

Execute the mock-orchestrator test and summarize the Main → Orchestrator → Prediction/Attribution layer structure and what each child skill returned.

Test skill composition

Use /mock-orchestrator to validate nested child-skill invocation and write the final summary to the expected path.

name: mock-orchestrator description: Mock orchestrator for 4-layer thinking test. Calls prediction and attribution skills. allowed-tools: Read, Write, Skill model: claude-opus-4-5 permissionMode: dontAsk context: fork

Mock Orchestrator (Layer 1)

Name: Mock Orchestrator for Multi-Layer Testing
Author: Skills Guide Bot

Goal: Test thinking token capture across 4 layers: Main → Orchestrator → Prediction/Attribution → Task Subagents

Thinking: Use ultrathink for this analysis.

Task

Think about the 4-layer architecture we're testing
Write your reasoning to: earnings-analysis/test-outputs/mock-orchestrator-reasoning.txt
Call /mock-prediction skill (Layer 2 → Layer 3)
Call /mock-attribution skill (Layer 2 → Layer 3)
After both complete, write final summary to: earnings-analysis/test-outputs/mock-orchestrator-final.txt

Include in your files:

Note that this is "mock-orchestrator (Layer 1)"
Summary of what each child skill returned
The complete layer structure being tested

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/mock-orchestrator-for-multi-layer-testing-mmh8qqq2/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/mock-orchestrator-for-multi-layer-testing-mmh8qqq2' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mock-orchestrator-for-multi-layer-testing-mmh8qqq2/download' --output '.skill-downloads/mock-orchestrator-for-multi-layer-testing-mmh8qqq2/SKILL.md.part' && mv '.skill-downloads/mock-orchestrator-for-multi-layer-testing-mmh8qqq2/SKILL.md.part' '.skill-downloads/mock-orchestrator-for-multi-layer-testing-mmh8qqq2/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Skill

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/mock-orchestrator-for-multi-layer-testing-mmh8qqq2/SKILL.md' && test -s '.skill-downloads/mock-orchestrator-for-multi-layer-testing-mmh8qqq2/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/mock-orchestrator' && cp -R '.skill-downloads/mock-orchestrator-for-multi-layer-testing-mmh8qqq2' '.claude/skills/mock-orchestrator'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/mock-orchestrator-for-multi-layer-testing-mmh8qqq2'

openskills read 'mock-orchestrator-for-multi-layer-testing-mmh8qqq2'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/mock-orchestrator-for-multi-layer-testing-mmh8qqq2/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.