Claude Code Usage

​

Operating checklist

1. Confirm workspace with deepline auth status --json; for automation, run from a folder with .env.deepline.
2. If using a prebuilt play, run deepline plays search and deepline plays describe.
3. If authoring or editing a .play.ts, run deepline plays check <file>.
4. Pilot with 1-3 rows or one JSON input.
5. Inspect output and failures.
6. Run the full job with --watch, then export the completed rows with deepline runs export <run-id> --out <output.csv>.
7. Report input, output path, row counts, failures, and workspace.

​

Good prompt shape

Use the Deepline SDK docs.
I have leads.csv with linkedin_url and company_domain.
Write a play that finds verified work emails.
Run deepline plays check before running anything.
Pilot only the first 3 rows before the full file.

​

Ask for checks by name

After editing the play, run:
deepline plays check my-play.play.ts
Then run:
head -n 4 leads.csv > pilot.csv
deepline plays run --file my-play.play.ts --csv pilot.csv --watch
deepline runs export run_123 --out output.csv

​

Keep the story visible

​

Skills are optional

/deepline-gtm Build a workflow for this CSV, then check and pilot it before the full run.