Design a rigorous bespoke playbook for a task no bundled skill fits — steps that each end in a check, verification commands, failure branches — stored where the checker validates and anchor-validated. For recurring unusual task shapes.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
No bundled skill fits every task. This skill designs the playbook that does fit — once, rigorously — and leaves it behind as a validated, rerunnable artifact.
map firstexecuteResolve the checker and the playbooks directory it validates first — from a
target project the script does not exist at ./scripts/, ordinary launches
may leave both plugin-root variables unset, and OMC_STATE_DIR or a parent
.omc-workspace can redirect OMC state away from the checkout's literal
.omc/:
checker="${CLAUDE_PLUGIN_ROOT:-${OMC_PLUGIN_ROOT:-}}/scripts/check-omc-playbooks.mjs"
if [ ! -f "$checker" ] && omc_bin="$(command -v omc 2>/dev/null)"; then
# Portable realpath: BSD readlink has no -f, so resolve through cd/pwd -P.
bin_dir="$(dirname "$omc_bin")"
bin_dir="$(cd "$bin_dir" && pwd -P)"
for d in "$bin_dir" "$bin_dir/.." "$bin_dir/../.." "$bin_dir/../../.."; do
if [ -f "$d/scripts/check-omc-playbooks.mjs" ]; then checker="$d/scripts/check-omc-playbooks.mjs"; break; fi
done
fi
playbooks_dir="$(node "$checker" "$PWD" --print-playbooks-dir)"Standalone installs reach the script by walking up from the omc binary to
the package root that ships scripts/. If the checker still cannot be
found, report the resolution failure instead of skipping validation.
Store the result at $playbooks_dir/<name>.md with frontmatter:
---
extends: <bundled-skill-name>
when: <one sentence naming the requests this playbook serves>
---Anchor every modification of a bundled step with **After** "<quoted step text>" / **Before** / **Replace** / **In**, quoting the bundled skill
verbatim. Then run node "$checker" . to validate.
It fails when an OMC upgrade rewrites a step you anchored to. Report what it prints; never guess where an unanchored change belongs.
state/verification-ledger.tsv under the resolved state root)
before the playbook is declared done.Yeachan-Heo/oh-my-claudecode
dec7e41
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.