ds
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
ds — a data project, run through work with a computed data-quality gate
What this skill carries — grep references/ for any subject the names below miss:
!d=${CLAUDE_SKILL_DIR}; command -v skill-toc >/dev/null 2>&1 && exec skill-toc "$d"; s=$HOME/.claude/skills/plugin-utils/bin/skill-toc; [ -x "$s" ] && exec "$s" "$d"; echo "(skill-toc unavailable: references and scripts are NOT listed here — install the plugin-utils plugin, or start a new session so its bin/ reaches PATH)"
DS constraints in force — every rule scoped to this workflow, discovered from the corpus so a new one needs no edit here; read the ones your task touches:
!c=${CLAUDE_PLUGIN_ROOT}/scripts/load-constraints; [ -x "$c" ] && exec "$c" ds; echo "(constraint index unavailable: NO DS rule is listed here — the four named below are not the whole set)"
The lifecycle is work. Read it and follow it.
This file is a delta: it supplies the domain — the CLARIFY axes, the plan grammar, the lens,
the mechanical checks, the refs, the authority text. It ships no workflow.js and restates none of
work's mechanics.
What makes a run ds rather than plain work is one thing: every declared data output is verified
by a computed runner, not by the agent that produced it. scripts/ds-dq.py reads the approved
plan's ## Data Outputs table and opens each artifact itself; work's JS reads its exit code.