dym-harness-sdk

Skill: dym-harness-sdk — workflow hub for Strands harness

When to use

• User types /dym-harness-sdk (no arguments → slug table) or /dym-harness-sdk <slug>; or /dym routes here by domain.
• The hub only costs the description line; the child workflow body is read only when invoked.

Steps

1. Read ARGUMENTS → <slug>. No slug → print the table below then stop, read no file.

   slug	purpose	type
   quickstart	Install strands-harness into an isolated venv, build the agent, see what it assembles	shell + python
   interventions	Attach tool-call guardrail: ask / smart / .cedar / text policy	python
   effect-tests	Write live-model tests the Strands way: assert EFFECT, do not assert wording	pytest
   evals	Grade agents with the Strands Evals SDK (external repo) — not yet verified	python + CLI
   contributor	Modify the harness itself: run unit/integration/selective tests like CI	shell

1. Find the child file in order, take the FIRST file that exists then read EXACTLY ONE file: (1) ../dym-harness-sdk-<slug>/SKILL.md (next to the hub — installed via npx skills add rheinmir/dym); (2) .overstack/doyourmagic/harness-sdk/skills/dym-harness-sdk-<slug>/SKILL.md (bundled in the project); (3) doyourmagic-bundles/harness-sdk/skills/dym-harness-sdk-<slug>/SKILL.md (clone rheinmir/dym next to the project). Follow that file's Steps/Rules; do not read other child files; if none of the 3 are found → say so clearly, stop.

Rules

• Each sub-skill is self-contained; the hub does not stuff the whole bundle into context.
• workflows.md next to the bundle is an index + verification table + comparison with overstack, not a source of commands.