When to use
- User types
/dym-humanizer(no arguments → slug table) or/dym-humanizer <slug>; or/dymroutes here by domain. - The hub only costs the description line; the child workflow body is only read when invoked.
Steps
-
Read ARGUMENTS →
<slug>. No slug → print the table below then stop, do not read any file.slug purpose install-shellInstall Humanizer via shell (Skills CLI / manual copy) install-claude-pluginInstall Humanizer as a Claude Code plugin (chat command) humanize-pasted-textFix pasted text directly (default mode) humanize-files-and-embeddedFix files on disk, and embed into other work (file / embedded mode) tune-false-positivesPrevent over-editing: false positives and details the person wants kept contributor-validate-and-releaseModify Humanizer itself: test suite and release rules (contributor)
- Find the child file in order, take the FIRST file that exists then read EXACTLY ONE file:
(1)
../dym-humanizer-<slug>/SKILL.md(next to the hub — installed vianpx skills add rheinmir/dym); (2).overstack/doyourmagic/humanizer/skills/dym-humanizer-<slug>/SKILL.md(bundled in the project); (3).claude/skills/dym-humanizer-<slug>/SKILL.md. 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.mdnext to the bundle is an index + verification table, not a source of commands.