git:20261012.9d4f213 to git:20261014.c2b0cfa

---

name: deepline-plays-review

description: 'Use this skill when a human needs to review a Deepline Play result and hand feedback, labels, or approval back to the agent for revision, evaluation, comparison, or bounded iteration. Triggers on “put this run in a Sheet,” “review these results,” “read my feedback,” “make this a standing rule,” “never regress on this case,” “compare these runs,” “keep improving,” or “add the revised run to the same spreadsheet.” Skip ordinary Play authoring or execution with no human review loop, generic spreadsheet work, and one-off CSV export.'

---

# Review and Improve Deepline Plays

## Quick Start

```bash

npm install -g deepline

deepline auth register --wait auto

deepline -h

```

## CLI resolution

Run `deepline` when it is available. If the shell reports that command is missing, use `<workspace-root>/.deepline/runtime/bin/deepline` (or the npm-created `.cmd` shim on Windows). If neither exists, follow `https://code.deepline.com/INSTALL.md` to set up Deepline.

## Route the request

| User intent | Start here |

| ------------------------------------ | ---------------------------------------------- |

| Put a run in a Sheet | Export the completed dataset for review |

| Address edits, notes, or comments | Read fresh feedback and run one revision |

| Make feedback a standing rule | Record a general expectation |

| Never regress on a corrected case | Add a case-specific expectation or golden case |

| Compare revisions | Evaluate both against one frozen basis |

| Try several improvements | Establish a bounded agent-driven loop |

| Keep improving together across turns | Resume the loop and yield after each candidate |

**Stop at planning boundaries.** When the user asks for a plan,

classification, or proposed evaluation before any calls or edits, write it

from the supplied context and stop. Do not inspect live Plays, runs, files, or

## Establish or resume the loop

- **Revision:** the Play version under test.

- **Run:** that revision executed on known inputs.

- **Assessment:** evidence about how a run met an expectation.

```bash

deepline search "Play run dataset -> spreadsheet" --type tools

deepline search "spreadsheet ID -> its rows and comments" --type tools

deepline tools describe google_workspace_export_dataset

deepline tools describe google_workspace_request

```

## Run and review

Run the Play and keep its completed run ID. When provider calls are involved,

```bash

deepline runs get "$RUN_ID" --full --json > "$WORKDIR/run.json"

jq -e '

.datasets | if type != "array" then error("Expected datasets array") else .[] end |

if (.datasetId | type) != "string" or .datasetId == "" then error("Missing dataset identity")

else {datasetId, name, table: .storage.table, rowCount} end

' "$WORKDIR/run.json"

```

```bash

: "${SKILL_DIR:?Set SKILL_DIR to the installed deepline-plays-review directory}"

: "${RUN_ID:?Set RUN_ID to a completed Play run}"

: "${DATASET_ID:?Set DATASET_ID to the selected datasets[].datasetId}"

TAB_LABEL="${TAB_LABEL:-Results}"

SPREADSHEET_TITLE="${SPREADSHEET_TITLE:-Play review}"

OPERATION_KEY="${OPERATION_KEY:-review-$(date -u +%Y%m%dT%H%M%SZ)}"

PRESENTATION="$(node "$SKILL_DIR/scripts/review-sheet-presentation.mjs")"

EXPORT_INPUT="$(jq -n \

--arg run_id "$RUN_ID" \

--arg dataset_id "$DATASET_ID" \

--arg spreadsheet_id "${SPREADSHEET_ID:-}" \

--arg spreadsheet_title "$SPREADSHEET_TITLE" \

--arg tab_name "$TAB_LABEL" \

--arg operation_key "$OPERATION_KEY" \

--argjson presentation "$PRESENTATION" \

'{

dataset: {run_id: $run_id, dataset_id: $dataset_id},

destination: (

{tab_name: $tab_name, mode: "new_tab"} +

if $spreadsheet_id == ""

then {spreadsheet_title: $spreadsheet_title}

else {spreadsheet_id: $spreadsheet_id}

end

),

presentation: $presentation,

operation_key: $operation_key

}')"

deepline tools execute google_workspace_export_dataset \

--input "$EXPORT_INPUT" --json |

tee "$WORKDIR/export.json"

```

Use the returned spreadsheet ID, URL, tab name, Shared Drive URL, and folder URL

credentials, or broaden sharing.

```bash

deepline tools execute google_workspace_request --input "{

\"method\": \"sheets.spreadsheets.values.get\",

\"spreadsheet_id\": \"$SPREADSHEET_ID\",

\"params\": {\"range\": \"'$TAB_NAME'!A1:Z5000\"}

}" --json > "$WORKDIR/values.json"

deepline tools execute google_workspace_request --input "{

\"method\": \"drive.comments.list\",

\"spreadsheet_id\": \"$SPREADSHEET_ID\",

\"params\": {\"page_size\": 100}

}" --json > "$WORKDIR/comments.json"

```

## Interpret feedback and revise

Classify feedback before acting:

| Feedback | Treatment |

| -------------------------------------- | ------------------------- |

| Judgment about this result | Assessment for this run |

| “Always apply this rule” | General expectation |

| Correct answer for this concrete input | Case-specific expectation |

| “Never get this case wrong again” | Golden case |

| Preference between candidate outputs | Comparative assessment |

| Requested Play behavior | Candidate revision |

| Continue, accept, reject, or stop | Loop decision |

Make one attributable behavior change where practical, run the candidate, and

export it to the same spreadsheet as a new tab. Never overwrite a reviewed tab:

## Evaluate and decide

Expectations can be general rules, case-specific answers, constraints, rubrics,

representation that captures what the user means. Package repeated

Prefer deterministic graders when the expectation permits them: normalized

equality for labels, tolerance bands for numbers, set precision/recall for

multi-value outputs, and explicit rubric labels for judgments.

Keep missing, duplicate, invalid, and unscorable cases separate from incorrect

Accept a candidate when the objective improves enough, constraints pass, and no

protected slice materially regresses. Otherwise reject it, revise the

hypothesis, or stop.

## Continue, checkpoint, or recover

Human-stepped work produces one candidate and yields. For agent-driven work,

Stop when the target is met, the budget is exhausted, the plateau rule fires,

or the next change needs broader authority. Preserve rejected candidates and

their assessments so a resumed session does not repeat failed ideas.

Checkpoint the objective, expectation and case-set versions, baseline and

candidate revisions, run IDs, spreadsheet and tab IDs, decisions, remaining

budget, and next action.

Route expected Workspace failures:

- `GOOGLE_WORKSPACE_EXPORT_CONFLICT`: preserve reviewer work; use a new

operation key and tab for a genuinely new export.

- `GOOGLE_WORKSPACE_EXPORT_BUSY` or `GOOGLE_WORKSPACE_CREATE_NOT_VISIBLE`:

retry the exact request with the same operation key.

- `INTEGRATION_CONFIG_ERROR`: report that the managed integration is not ready;

do not ask the customer for Deepline's Google credentials.

- Edited expectations or labels: mark the comparison stale and restart against

the new basis rather than presenting incomparable scores.