rowlab

Installation
SKILL.md

Rowlab

Define a task, try it on selected rows, measure the quality needed for the user's purpose, then complete and export the run. Model and manual execution use the same task definitions. Each run creates a new dataset containing its selected rows and output columns; it preserves source data. Completed outputs are immutable.

Use the connected MCP tools' descriptions for current parameters and response shapes. The MCP guide covers connection and tool usage; the API reference is for scripts. Installing this skill does not connect the server. Check available tools before relying on manual execution or file links; older servers may not expose run_answers, run_finish, dataset_upload or dataset_download.

Define the task

Import a supplied file when it is not already a dataset: dataset_add takes a public URL or an s3:// object, and on a local server also a path. For a file on your machine with a hosted server, get a link with dataset_upload and run its curl command; the link expires after 15 minutes and acts for the user's organisation, so don't share it. Inspect the dataset and representative rows with dataset_get and sql_query. Establish what one row represents, what the output should mean, and which errors matter. Keep existing reference labels and model predictions in their own columns.

Choose the narrowest useful answer type: yes/no, pick one, pick any, scale, typed extraction, or text. Explain ambiguous options in their descriptions. Add a meaningful “not applicable” option when the task needs one; do not silently invent categories that change the user's question. Build the prompt from the row's actual columns, and check its rendered form with run_preview.

Several fields from the same text can share one extraction task. Distinct questions can be separate tasks in one run; grouping tasks does not by itself reduce model calls. Tasks and row selection are frozen when the run starts. Changing them requires a new run, with output names that do not collide with existing columns.

Choose execution

Models: default to run_start with method="llm" for bulk labeling unless the user requests manual execution or supplies existing labels. Try a small set of rows before an expensive run when the task has not been checked. Read answers alongside their inputs, including empty, ambiguous and unusual cases. A small prompt-debugging sample does not establish accuracy. Decision models are candidates for classification; extraction and generation need language models. Use the live model catalog for capabilities and prices.

Before a paid full run, preview its SQL selection and report rows, calls and estimated cost. If that spend is not covered by existing authorization, agree a budget before starting; do not ask again for steps already covered. Resolve material budget or task changes before proceeding.

Installs
3
First Seen
13 days ago