data-to-d3-entry-selector

Use first for the entire requested task. Before broad task discovery, source edits, global verification, a user-task continuation, or a summary, create or read `workflow/data-to-d3-board.json`; use th

SKILL.md

GitHub

Board-v2 Entry selection

  1. Activate. Use this entry skill when workflow/data-to-d3-board.json is absent, both active fields name it, or handoff_to=data-to-d3-entry-selector plus its exact required_handoff_sequence authorizes only the immediate return consume. A prior read, broad task request, or remembered plan is never authorization. workflow/data-to-d3-board.json is persistent: never delete, rename, recreate, or clean it up.
  2. Bootstrap or consume. Immediately after this SKILL.md, make one standalone relative-path sed -n read of workflow/data-to-d3-board.json. Do not run rg, rg --files, ls, a glob, pwd, find, mkdir, test, if, &&, a wrapper, a task-file read, a plan, or a later SKILL first. If it is absent, its immediate next tool action must be one board-only apply_patch creating one canonical base object with each runtime key exactly once: active_stage_id, active_skill_name, active_catalog_item, completed_catalog_item_ids, return_checkpoint, next_work_packet, authorization_lease, continuation_outcome, verifier_status, proof_round, stage_epoch, record_generation, summary_permitted, handoff_to, successor_rebuild, required_next_command, required_handoff_sequence, handoff_complete, response_permitted; set active_stage_id=data-to-d3-entry-selector, active_skill_name=data-to-d3-entry-selector, handoff_to=null, next_work_packet=null, stage_epoch=0, record_generation=0, handoff_complete=false, summary_permitted=false, and response_permitted=false. Its bootstrap return_checkpoint must require publish-next-work-packet and carry selected_item=output-data, entry_probe=/root/data/stock-descriptions.csv, and work_anchor=/root/output/data/. Do not use mkdir, find, test, if, &&, or a task-file read instead of this write; bootstrap is not selection or handoff. If the fresh board selects this role, its immediate next tool call is one board-only Update File consume transition: set both active-stage fields exactly to data-to-d3-entry-selector, keep active_catalog_item, clear only data-to-d3-catalog-return-gate handoff fields, and do no task action. Never use a Delete/Add pair.
  3. One role action. At startup select only output-data. On a gate return, return_checkpoint is the sole routing authority: after its mandatory board-only consume, resolve exactly one matching clause below from return_checkpoint.verified_item and return_checkpoint.verifier_status.status. A generic first-incomplete inference, remembered user plan, or remaining task output is never authorization. return_checkpoint.entry_requirement=publish-next-work-packet is a physical obligation.

Entry-only return selector. Resolve exactly one matching clause only after the mandatory return-stub consume. These clauses are private to entry: never copy an inactive clause, a future anchor, or a future mutation into the board, packet, lease, outcome, verifier status, or any non-entry skill.

  • Bootstrap selects output-data: one standalone source assertion /root/data/stock-descriptions.csv; packet work_anchor=/root/output/data/, lease_scope=Authorize only /root/output/data/ so the copied stock descriptions file and all 50 stock-history CSV files are staged there under the required subdirectory structure., mutation=Copy /root/data/stock-descriptions.csv into /root/output/data/stock-descriptions.csv and copy each manifest-listed /root/data/indiv-stock CSV file into /root/output/data/indiv-stock/ without renaming., and local scoped_check=Confirm /root/output/data/ contains the copied stock-descriptions file and all 50 copied stock-history CSV files under indiv-stock/..
  • A failed or blocked return for output-data reselects only output-data: one standalone source assertion /root/data/stock-descriptions.csv; packet work_anchor=/root/output/data/, lease_scope=Authorize only /root/output/data/ so the copied stock descriptions file and all 50 stock-history CSV files are staged there under the required subdirectory structure., mutation=Copy /root/data/stock-descriptions.csv into /root/output/data/stock-descriptions.csv and copy each manifest-listed /root/data/indiv-stock CSV file into /root/output/data/indiv-stock/ without renaming., and local scoped_check=Confirm /root/output/data/ contains the copied stock-descriptions file and all 50 copied stock-history CSV files under indiv-stock/..
  • A passed return for output-data reselects only d3-bundle: one standalone predecessor assertion /root/output/data/stock-descriptions.csv; packet work_anchor=/root/output/js/d3.v6.min.js, lease_scope=Authorize only /root/output/js/d3.v6.min.js as the offline D3.js v6 runtime required by the stock web app., mutation=Write a local vendored D3.js v6 bundle to /root/output/js/d3.v6.min.js so the page can load D3 force, scale, selection, and CSV APIs offline., and local scoped_check=Confirm /root/output/js/d3.v6.min.js is a substantial local D3 v6 bundle with the APIs needed by the stock app..
  • A failed or blocked return for d3-bundle reselects only d3-bundle: one standalone source assertion /root/data/stock-descriptions.csv; packet work_anchor=/root/output/js/d3.v6.min.js, lease_scope=Authorize only /root/output/js/d3.v6.min.js as the offline D3.js v6 runtime required by the stock web app., mutation=Write a local vendored D3.js v6 bundle to /root/output/js/d3.v6.min.js so the page can load D3 force, scale, selection, and CSV APIs offline., and local scoped_check=Confirm /root/output/js/d3.v6.min.js is a substantial local D3 v6 bundle with the APIs needed by the stock app..
  • A passed return for d3-bundle reselects only style-sheet: one standalone predecessor assertion /root/output/js/d3.v6.min.js; packet work_anchor=/root/output/css/style.css, lease_scope=Authorize only /root/output/css/style.css for the horizontal chart-and-table layout, legend, tooltip, and selection styling., mutation=Write the stylesheet for a side-by-side bubble-chart and table layout, including legend styling, ticker readability, tooltip presentation, and highlighted row or bubble states., and local scoped_check=Confirm /root/output/css/style.css defines the side-by-side layout, legend, tooltip, and selected-state styles for the stock dashboard..
  • A failed or blocked return for style-sheet reselects only style-sheet: one standalone source assertion /root/data/stock-descriptions.csv; packet work_anchor=/root/output/css/style.css, lease_scope=Authorize only /root/output/css/style.css for the horizontal chart-and-table layout, legend, tooltip, and selection styling., mutation=Write the stylesheet for a side-by-side bubble-chart and table layout, including legend styling, ticker readability, tooltip presentation, and highlighted row or bubble states., and local scoped_check=Confirm /root/output/css/style.css defines the side-by-side layout, legend, tooltip, and selected-state styles for the stock dashboard..
  • A passed return for style-sheet reselects only visualization-js: one standalone predecessor assertion /root/output/css/style.css; packet work_anchor=/root/output/js/visualization.js, lease_scope=Authorize only /root/output/js/visualization.js for the D3 bubble chart, sector legend, tooltip behavior, and linked table interactions., mutation=Write the D3 v6 script that loads the copied stock data, builds one clustered bubble chart by sector, sizes nodes by market cap with uniform ETF sizing, labels each node by ticker, suppresses ETF tooltips, renders the stock table, and links bubble and row selection., and local scoped_check=Confirm /root/output/js/visualization.js contains the clustered-bubble, ETF guard, tooltip, legend, and linked table-selection logic for the copied stock data..
  • A failed or blocked return for visualization-js reselects only visualization-js: one standalone source assertion /root/data/stock-descriptions.csv; packet work_anchor=/root/output/js/visualization.js, lease_scope=Authorize only /root/output/js/visualization.js for the D3 bubble chart, sector legend, tooltip behavior, and linked table interactions., mutation=Write the D3 v6 script that loads the copied stock data, builds one clustered bubble chart by sector, sizes nodes by market cap with uniform ETF sizing, labels each node by ticker, suppresses ETF tooltips, renders the stock table, and links bubble and row selection., and local scoped_check=Confirm /root/output/js/visualization.js contains the clustered-bubble, ETF guard, tooltip, legend, and linked table-selection logic for the copied stock data..
  • A passed return for visualization-js reselects only index-page: one standalone predecessor assertion /root/output/js/visualization.js; packet work_anchor=/root/output/index.html, lease_scope=Authorize only /root/output/index.html as the single-page shell that wires the copied data, local D3 bundle, stylesheet, and visualization script together., mutation=Write /root/output/index.html with the side-by-side application shell, the bubble-chart and stock-table containers, the tooltip container, and the local asset references to css/style.css, js/d3.v6.min.js, and js/visualization.js., and local scoped_check=Confirm /root/output/index.html loads the local assets and exposes the side-by-side chart, table, and tooltip shell for the stock dashboard..
  • A failed or blocked return for index-page reselects only index-page: one standalone source assertion /root/data/stock-descriptions.csv; packet work_anchor=/root/output/index.html, lease_scope=Authorize only /root/output/index.html as the single-page shell that wires the copied data, local D3 bundle, stylesheet, and visualization script together., mutation=Write /root/output/index.html with the side-by-side application shell, the bubble-chart and stock-table containers, the tooltip container, and the local asset references to css/style.css, js/d3.v6.min.js, and js/visualization.js., and local scoped_check=Confirm /root/output/index.html loads the local assets and exposes the side-by-side chart, table, and tooltip shell for the stock dashboard..
  • A passed return for index-page increments proof_round and reselects only output-data: one standalone predecessor assertion /root/output/data/stock-descriptions.csv; packet work_anchor=/root/output/data/, lease_scope=Authorize only /root/output/data/ so the copied stock descriptions file and all 50 stock-history CSV files are staged there under the required subdirectory structure., mutation=Copy /root/data/stock-descriptions.csv into /root/output/data/stock-descriptions.csv and copy each manifest-listed /root/data/indiv-stock CSV file into /root/output/data/indiv-stock/ without renaming., and local scoped_check=Confirm /root/output/data/ contains the copied stock-descriptions file and all 50 copied stock-history CSV files under indiv-stock/..

The first non-board task action is exactly the one standalone selected-input source assertion from the resolved clause. Immediately publish only that clause's one result packet, then make the required successor handoff before another task action. A file-discovery form of rg (including rg --files), ls, a glob, repository discovery, a broad task plan, a task edit, a lease write, a second probe, or direct work on another output is never that assertion.

Return packet lock. On a passed gate return, the entry board read locks one fixed sequence: consume only the return stub in one board-only update; run exactly one standalone one-byte predecessor probe; publish the selected packet; make the binder successor handoff; emit the entry marker; then read the binder SKILL. No task action is allowed between those six actions. For the output-data -> d3-bundle return, that sole probe is exactly head -c 1 /root/output/data/stock-descriptions.csv >/dev/null. Before the packet and binder handoff, do not read /root/data, inspect a CSV schema, discover/download D3, make a directory, or create/revise any output. A statement that the app is ready to implement is never a substitute for this sequence.

D3 entry packet lock. For a passed d3-bundle return, after this entry SKILL the immediate standalone board read and return-stub consume are mandatory. The sole non-board probe is exactly head -c 1 /root/output/js/d3.v6.min.js >/dev/null. Then publish only the style-sheet packet, make the binder handoff, emit the entry marker, and read the binder SKILL. Until that binder read, do not inspect copied data or a schema, create a CSS/JS/HTML file, or describe implementing the app. Having the data and D3 bundle available is not an authorization lease.

  1. Result commit — not handoff. Immediately after the one role action, make one board-only Update File as one board-only local diff: retain every unspecified top-level key unchanged, and never duplicate, rename, delete, or recreate a key. Write the selected active_catalog_item, one actual selection_evidence, and exactly one complete selected-card next_work_packet with checkpoint_generation, selected_item, entry_probe, observed_precondition, work_anchor, lease_scope, mutation, and the compact local scoped_check intent; only entry may replace that packet. The packet must not contain a shell/Python command. Do not write a lease, outcome, or verifier status. Keep active_stage_id=data-to-d3-entry-selector and active_skill_name=data-to-d3-entry-selector, set handoff_to=null, and preserve summary_permitted=false, handoff_complete=false, and response_permitted=false. Do not write successor state or a marker. This result commit is not a handoff: no task read, task action, catalog selection, planning, SKILL read, marker, or response may intervene before block 5.
  2. Successor handoff — mandatory next tool call. Make one board-only Update File as one board-only local diff: retain every unspecified top-level key unchanged, and never duplicate, rename, delete, or recreate a key preserving this role’s result and active item. Increment stage_epoch and record_generation; keep summary_permitted=false, handoff_complete=false, and response_permitted=false; set active_stage_id=data-to-d3-scope-binder, active_skill_name=data-to-d3-scope-binder, and handoff_to=data-to-d3-scope-binder exactly; write only data-to-d3-scope-binder successor_rebuild with successor_skill_read_required=true, successor_board_read_required=true, and response_permitted=false; and store required_next_command as the exact block-6 marker plus required_handoff_sequence=emit-marker,read-successor-skill,read-board,consume-stub. A result commit or consume transition never substitutes for this successor handoff.
  3. Emit the literal marker. The next tool call executes the stored standalone printf or echo marker. Its marker fields are stage_id=data-to-d3-entry-selector, record_generation=, validates_successor=data-to-d3-scope-binder, validation_status=, rebuild_required=true, handoff_to=data-to-d3-scope-binder, board_path=workflow/data-to-d3-board.json, board_epoch=, continuation_required=true, catalog_item=, handoff_complete=false, response_permitted=false, and next_action=read-data-to-d3-scope-binder-skill; stage_id is this skill name, never active_catalog_item, and board_path has no /root/ or other workspace prefix. Copy only the just-written decimal record_generation, decimal board_epoch, validation status, and current catalog item into the remaining fields. Use one physical source line with ASCII spaces and one trailing ; no placeholders, shell variables, or combined command.
  4. Activate the successor. The marker is evidence only. This data-to-d3-entry-selector predecessor remains responsible and its handoff is incomplete until its exact next three independent tool actions finish in order: read data-to-d3-scope-binder/SKILL.md from the exact installed root used to read this SKILL; make the successor standalone relative-path board read; then let only data-to-d3-scope-binder consume its rebuild stub in one board-only write. response_permitted=false is a non-response transition lock, not an advisory board value. No green user result, all-passed catalog, repeated visit, or broad task objective permits a reply, summary, task-file read, task mutation, plan, or other tool before those three actions finish. Only after stub consumption does data-to-d3-scope-binder own its one role action. Do not use &&, ;, pipes, loops, functions, command substitution, source, a batch-stage command, a global build/test, or a task summary.

Board ambiguity is never an escape. If this fresh board contains duplicate, stale, or inconsistent active fields, treat them as inherited inert text: do not diagnose, normalize, delete/add, recreate, or explain the board, and never infer that remaining user-task outputs are authorized. The exact incoming handoff_to plus required_handoff_sequence, or the paired active fields for this role, still authorize only this role's prescribed board transition. After that transition, emit the stored marker and activate the named successor; no ambiguity permits task work outside the ring.

No role may set summary_permitted=true. A green result is not closeout; after all ids pass, entry starts the next proof_round with the oldest passed id.