Append Letters

append-letters

When to use this skill

• A minimal, readable example of a GridWatch sequential orchestrator.
• Runs append-x then append-y, each appending one character to a shared file.

Everything above this line is yours to edit. The block below is generated by GridWatch from the orchestration configuration in gridwatch.json — edit the configuration in the Skills Graph and click Save to regenerate it, rather than editing between the markers by hand.

Workflow (sequential)

1. Announce — Print: 🚀 [append-letters] Starting append-letters (sequential)...
2. Determine the session identifier — Set SESSION_ID to the current Copilot CLI session id (the UUID of the active session under ~/.copilot/session-state/). Use it to name all output files so concurrent runs do not clash.
3. Run each step in order, waiting for each to finish before the next. Announce each step yourself before running it:
   1. append-x — Print 📣 [append-letters] Running append-x…, then run the append-x skill and wait for it to finish. Instruct it to write its output to /tmp/gridwatch-demo/letters-<SESSION_ID>.txt.
   2. append-y — Print 📣 [append-letters] Running append-y…, then run the append-y skill and wait for it to finish. Tell it to read its input from /tmp/gridwatch-demo. Instruct it to write its output to /tmp/gridwatch-demo/letters-<SESSION_ID>.txt.
4. Confirm each step wrote its output before continuing.
5. Report back — Print a short summary and the absolute path(s) to the output(s).
6. Announce completion — Print: ✅ [append-letters] Finished append-letters (sequential).

Notes

The two child skills append to the same file, so by the time the orchestrator finishes the file contains XY. Because the run is sequential, append-y is guaranteed to run after append-x has finished writing.

Source: faesel/gridwatch — distributed by TomeVault.