@bendyline/gilde 0.1.95 → 0.2.0

package/data/craftbook-templates/sp/spreadsheet-findings/manifest.json

@@ -0,0 +1,26 @@
+{
+  "schemaVersion": 1,
+  "kind": "craftbook-template",
+  "id": "spreadsheet-findings",
+  "role": "general",
+  "category": "research",
+  "interests": [
+    "data"
+  ],
+  "name": "Make sense of a spreadsheet",
+  "description": "Hand it a spreadsheet and get back what is in it, what stands out, one table worth keeping, and what to look at next, with every number quoted from the file. Works on a CSV, TSV or Excel file and needs no web access and no code. Use it to make sense of sales figures, budgets, survey exports, sign-up lists, or any other table of numbers.",
+  "tags": [
+    "gallery",
+    "first-project",
+    "spreadsheet",
+    "csv",
+    "data",
+    "analysis",
+    "findings"
+  ],
+  "maintainer": {
+    "name": "Gezel"
+  },
+  "license": "MIT",
+  "yankedVersions": []
+}

package/data/craftbook-templates/sp/spreadsheet-findings/versions/1.0.0/craftbook.json

@@ -0,0 +1,186 @@
+{
+  "id": "spreadsheet-findings",
+  "name": "Make sense of a spreadsheet",
+  "description": "Hand it a spreadsheet and get back what is in it, what stands out, one table worth keeping, and what to look at next, with every number quoted from the file. Works on a CSV, TSV or Excel file and needs no web access and no code. Use it to make sense of sales figures, budgets, survey exports, sign-up lists, or any other table of numbers.\n\nIt works on the spreadsheet you choose when you launch it: a file in this project, or one you pick from your computer. No file to hand? Try it on the sample, a small shop's monthly sales.",
+  "entryStepId": "analyse",
+  "triggers": [
+    "make sense of a spreadsheet",
+    "what stands out in this spreadsheet",
+    "analyse a spreadsheet",
+    "analyze a spreadsheet",
+    "findings from a spreadsheet",
+    "summarize a csv"
+  ],
+  "samples": [
+    {
+      "id": "shop-sales",
+      "title": "a small shop's monthly sales",
+      "param": "source",
+      "files": [
+        "samples/shop-sales/sales.csv"
+      ]
+    }
+  ],
+  "paramSchema": {
+    "type": "object",
+    "required": [
+      "source"
+    ],
+    "properties": {
+      "source": {
+        "type": "string",
+        "title": "Spreadsheet",
+        "description": "The spreadsheet to make sense of: a CSV, TSV or Excel file in this project, or one you pick from your computer.",
+        "input": {
+          "kind": "file",
+          "accept": [
+            ".csv",
+            ".tsv",
+            ".xlsx"
+          ]
+        }
+      },
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}",
+        "askUser": false
+      }
+    }
+  },
+  "steps": [
+    {
+      "id": "analyse",
+      "name": "Make sense of it",
+      "description": "Read the spreadsheet and write what is in it and what stands out.",
+      "prompt": "Make sense of the spreadsheet in the `source` input and write what you find to `{{workPath}}/findings.md`.\n\n1. Open the file list `{{task.dir}}/inputs/source.json` with `read_artifact`. It names the spreadsheet and the drawer it is in.\n2. Read the spreadsheet end to end with the tool named on its `source` line under Invocation parameters. Note the column names, the number of data rows, and the first and last date or period, if it has dates.\n3. Work out what stands out: the highest and lowest values, a peak or a dip, how a value changed from the first period to the last, a group that grows or shrinks, a row that does not fit. Prefer numbers you can read straight from the file. When you add numbers up, add them twice and use the total only if both sums agree.\n4. Write `{{workPath}}/findings.md` with `write_artifact`, under exactly these four headings:\n   - `## What is in it`: the columns, the number of data rows, and the date range, or that it has no dates.\n   - `## What stands out`: three to five findings, each in one or two sentences that give the actual numbers from the file.\n   - `## A table worth keeping`: one small markdown table taken or summed from the data, with a header row, a `|---|` line and at most 15 rows.\n   - `## What to look at next`: two or three questions the data raises but cannot answer.\n\nEvery number, name and date you write must come from the spreadsheet. Never invent one. If the file is longer than you can read, say under What is in it how many rows you read, and base every finding on those rows.\n\nIf the spreadsheet is empty or cannot be read, do not write `findings.md`. Write a task note with `write_task_note` that names the file you tried and what you saw, then end your turn.",
+      "suggestedRole": "data-analyst",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "artifact",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      },
+      "consumes": [
+        {
+          "file": "{{task.dir}}/inputs/source.json",
+          "artifact": true
+        }
+      ],
+      "advanceWhen": {
+        "file": "{{workPath}}/findings.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/findings.md",
+            "bytes": 600,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/findings.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*What is in it",
+            "flags": "i",
+            "label": "a \"## What is in it\" section",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/findings.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*What stands out",
+            "flags": "i",
+            "label": "a \"## What stands out\" section",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/findings.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*A table worth keeping",
+            "flags": "i",
+            "label": "a \"## A table worth keeping\" section",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/findings.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*What to look at next",
+            "flags": "i",
+            "label": "a \"## What to look at next\" section",
+            "artifact": true
+          },
+          {
+            "kind": "tableShape",
+            "file": "{{workPath}}/findings.md",
+            "minRows": 2,
+            "artifact": true
+          }
+        ],
+        "onReject": "analyse",
+        "maxAttempts": 3
+      },
+      "next": "finish"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "The deliverable passed its checks. Stamp a short summary and report DONE.",
+      "prompt": "The deliverable passed its checks. Write a one-paragraph DONE summary to task notes via `write_task_note`: what you made, the deliverable path(s), and a one-line confirmation that each required section is there. Then report DONE.",
+      "suggestedRole": "data-analyst",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      },
+      "terminal": true
+    }
+  ],
+  "version": "1.0.0",
+  "releasedAt": "2026-10-12T00:00:00Z",
+  "minGezelVersion": "1.26285"
+}

package/data/craftbook-templates/sp/spreadsheet-findings/versions/1.0.0/samples/shop-sales/sales.csv

@@ -0,0 +1,49 @@
+month,product,units,revenue_eur
+2025-01,Sourdough loaf,940,4230.00
+2025-01,Butter croissant,1310,2882.00
+2025-01,Rye loaf,640,2560.00
+2025-01,Honey spice cake,150,975.00
+2025-02,Sourdough loaf,905,4072.50
+2025-02,Butter croissant,1280,2816.00
+2025-02,Rye loaf,610,2440.00
+2025-02,Honey spice cake,135,877.50
+2025-03,Sourdough loaf,960,4320.00
+2025-03,Butter croissant,1395,3069.00
+2025-03,Rye loaf,575,2300.00
+2025-03,Honey spice cake,140,910.00
+2025-04,Sourdough loaf,980,4410.00
+2025-04,Butter croissant,1450,3190.00
+2025-04,Rye loaf,540,2160.00
+2025-04,Honey spice cake,160,1040.00
+2025-05,Sourdough loaf,1010,4545.00
+2025-05,Butter croissant,1560,3432.00
+2025-05,Rye loaf,505,2020.00
+2025-05,Honey spice cake,125,812.50
+2025-06,Sourdough loaf,970,4365.00
+2025-06,Butter croissant,1690,3718.00
+2025-06,Rye loaf,470,1880.00
+2025-06,Honey spice cake,110,715.00
+2025-07,Sourdough loaf,925,4162.50
+2025-07,Butter croissant,1785,3927.00
+2025-07,Rye loaf,430,1720.00
+2025-07,Honey spice cake,95,617.50
+2025-08,Sourdough loaf,890,4005.00
+2025-08,Butter croissant,1740,3828.00
+2025-08,Rye loaf,395,1580.00
+2025-08,Honey spice cake,105,682.50
+2025-09,Sourdough loaf,985,4432.50
+2025-09,Butter croissant,1520,3344.00
+2025-09,Rye loaf,360,1440.00
+2025-09,Honey spice cake,170,1105.00
+2025-10,Sourdough loaf,1020,4590.00
+2025-10,Butter croissant,1440,3168.00
+2025-10,Rye loaf,320,1280.00
+2025-10,Honey spice cake,310,2015.00
+2025-11,Sourdough loaf,1060,4770.00
+2025-11,Butter croissant,1405,3091.00
+2025-11,Rye loaf,285,1140.00
+2025-11,Honey spice cake,720,4680.00
+2025-12,Sourdough loaf,1240,5580.00
+2025-12,Butter croissant,1610,3542.00
+2025-12,Rye loaf,250,1000.00
+2025-12,Honey spice cake,1385,9002.50

package/data/craftbook-templates/sp/spreadsheet-findings/versions/1.0.0/test.json

@@ -0,0 +1,88 @@
+{
+  "schemaVersion": 1,
+  "mode": "workflow",
+  "title": "Make sense of a spreadsheet on the shop-sales sample",
+  "objective": "Prove that a small local model can run the Make sense of a spreadsheet craftbook on its bundled shop-sales sample, offline, and reach the terminal step with a findings report whose numbers come from the file.",
+  "tags": [
+    "first-project",
+    "sample",
+    "data"
+  ],
+  "prompt": "What stands out in this spreadsheet of a small bakery's monthly sales?",
+  "setup": {
+    "projectName": "Bakery sales",
+    "about": "A small made-up bakery's 2025 sales: one row per product per month, with units sold and revenue in euros. No web access or outside data is needed.",
+    "missionObjectives": "Run the craftbook on source/sales.csv and leave findings.md in the task folder, with every number taken from the file.",
+    "files": [
+      {
+        "path": "source/sales.csv",
+        "content": "month,product,units,revenue_eur\n2025-01,Sourdough loaf,940,4230.00\n2025-01,Butter croissant,1310,2882.00\n2025-01,Rye loaf,640,2560.00\n2025-01,Honey spice cake,150,975.00\n2025-02,Sourdough loaf,905,4072.50\n2025-02,Butter croissant,1280,2816.00\n2025-02,Rye loaf,610,2440.00\n2025-02,Honey spice cake,135,877.50\n2025-03,Sourdough loaf,960,4320.00\n2025-03,Butter croissant,1395,3069.00\n2025-03,Rye loaf,575,2300.00\n2025-03,Honey spice cake,140,910.00\n2025-04,Sourdough loaf,980,4410.00\n2025-04,Butter croissant,1450,3190.00\n2025-04,Rye loaf,540,2160.00\n2025-04,Honey spice cake,160,1040.00\n2025-05,Sourdough loaf,1010,4545.00\n2025-05,Butter croissant,1560,3432.00\n2025-05,Rye loaf,505,2020.00\n2025-05,Honey spice cake,125,812.50\n2025-06,Sourdough loaf,970,4365.00\n2025-06,Butter croissant,1690,3718.00\n2025-06,Rye loaf,470,1880.00\n2025-06,Honey spice cake,110,715.00\n2025-07,Sourdough loaf,925,4162.50\n2025-07,Butter croissant,1785,3927.00\n2025-07,Rye loaf,430,1720.00\n2025-07,Honey spice cake,95,617.50\n2025-08,Sourdough loaf,890,4005.00\n2025-08,Butter croissant,1740,3828.00\n2025-08,Rye loaf,395,1580.00\n2025-08,Honey spice cake,105,682.50\n2025-09,Sourdough loaf,985,4432.50\n2025-09,Butter croissant,1520,3344.00\n2025-09,Rye loaf,360,1440.00\n2025-09,Honey spice cake,170,1105.00\n2025-10,Sourdough loaf,1020,4590.00\n2025-10,Butter croissant,1440,3168.00\n2025-10,Rye loaf,320,1280.00\n2025-10,Honey spice cake,310,2015.00\n2025-11,Sourdough loaf,1060,4770.00\n2025-11,Butter croissant,1405,3091.00\n2025-11,Rye loaf,285,1140.00\n2025-11,Honey spice cake,720,4680.00\n2025-12,Sourdough loaf,1240,5580.00\n2025-12,Butter croissant,1610,3542.00\n2025-12,Rye loaf,250,1000.00\n2025-12,Honey spice cake,1385,9002.50\n"
+      }
+    ],
+    "craftbookParams": {
+      "source": "source/sales.csv"
+    },
+    "worker": {
+      "name": "Data Analyst",
+      "role": "data-analyst",
+      "about": "A careful data analyst. Follow the craftbook steps exactly, read the file you are given, and never invent a number."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The spreadsheet-findings task read the sample, wrote findings.md with all four sections and a table, named the December peak and the falling rye loaf, and reached its terminal step without external services.",
+    "deliverables": [
+      {
+        "path": "{{task.dir}}/findings.md",
+        "kind": "markdown-report",
+        "artifact": true,
+        "minBytes": 600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/findings.md",
+            "pattern": "\\bDec(?:ember)?\\b|2025-12",
+            "flags": "i",
+            "label": "the December peak",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{task.dir}}/findings.md",
+            "pattern": "\\brye\\b",
+            "flags": "i",
+            "label": "the falling rye loaf",
+            "artifact": true
+          }
+        ]
+      }
+    ],
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    }
+  },
+  "rubric": {
+    "artifact": {
+      "path": "{{task.dir}}/findings.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "grounding",
+        "description": "Every number, product and month in findings.md appears in sales.csv or is a correct sum of values in it."
+      },
+      {
+        "name": "insight",
+        "description": "The findings name what a shop owner would want to know first: the December peak driven by the honey spice cake, and the steady fall of the rye loaf."
+      }
+    ],
+    "contextNote": "Advisory only. Deterministic pass/fail comes from the craftbook runtime gates, the deliverable checks, attribution, and terminal progress."
+  },
+  "qualityFocus": [
+    "real spreadsheet-findings craftbook task attribution",
+    "numbers quoted from the file, never invented",
+    "all four required sections and a derived table",
+    "terminal workflow progress offline"
+  ]
+}

package/data/craftbook-templates/sp/spreadsheet-model/manifest.json

@@ -4,6 +4,10 @@
   "id": "spreadsheet-model",
   "role": "general",
   "category": "business",
+  "interests": [
+    "data",
+    "business"
+  ],
   "name": "Spreadsheet / Financial Model",
   "description": "Build a working spreadsheet-style model (budget, forecast, unit economics, pricing, or scenario calculator) with clearly separated inputs, calculations, and outputs. Scopes the model's purpose, drivers, and assumptions FIRST so the formulas have a contract, then builds the model with live formulas and labeled assumption cells, then verifies the math by hand-checking key outputs and a sanity scenario. Use this for a financial model, budget calculator, ROI/forecast spreadsheet, unit-economics model, or any input-driven calculator.",
   "tags": [

package/data/craftbook-templates/sp/sprite-sheet/manifest.json

@@ -4,6 +4,10 @@
   "id": "sprite-sheet",
   "role": "general",
   "category": "media",
+  "interests": [
+    "content",
+    "play"
+  ],
   "name": "Game Sprite Sheet",
   "description": "Produce a game-ready sprite sheet — a character or object with its animation frames (idle, walk, jump, attack) on a uniform grid — plus the frame metadata (JSON atlas) a game engine needs to slice it. Lock the style and the frame inventory FIRST (cell size, pivot, palette, which animations and how many frames each) because a sprite sheet is only usable if every cell is the same size and the pivot is consistent; then generate the frames and pack them into a sheet with a matching atlas. Covers sprite sheets, game art, animation frames, texture atlases, pixel-art characters, and 2D game assets.",
   "tags": [

package/data/craftbook-templates/sq/sql-analysis/manifest.json

@@ -4,6 +4,9 @@
   "id": "sql-analysis",
   "role": "general",
   "category": "code-data",
+  "interests": [
+    "data"
+  ],
   "name": "Answer a Question with SQL",
   "description": "Answer a specific business question against a database or table set with a correct, readable SQL query and a short written answer. Scopes the question, the tables/columns, and the grain FIRST (so the query measures the right thing at the right level), then writes and runs the query as a data-analyst, then verifies the result with a sanity check and an explanation. Use this for SQL analysis, querying a database, writing a report query, computing a metric in SQL, or answering 'how many / what's the trend' from tables.",
   "tags": [

package/data/craftbook-templates/st/standup-summary/manifest.json

@@ -4,6 +4,9 @@
   "id": "standup-summary",
   "role": "general",
   "category": "business",
+  "interests": [
+    "work"
+  ],
   "name": "Standup / Team Update Summary",
   "description": "Condense a pile of raw team updates (standup messages, async check-ins, channel dumps) into one clean summary grouped by person or workstream, surfacing blockers and decisions. Scopes the grouping axis and summary shape FIRST (by-person vs by-project, what counts as a blocker, the yesterday/today/blockers frame), then a copywriter compresses every raw update into that frame without dropping anyone. The scope-first step prevents a 4B model from rambling and guarantees blockers get their own callout section instead of being buried. Use for daily standup summaries, async update rollups, team check-in digests, and turning Slack threads into a readable recap.",
   "tags": [

package/data/craftbook-templates/st/status-report/manifest.json

@@ -4,6 +4,9 @@
   "id": "status-report",
   "role": "general",
   "category": "business",
+  "interests": [
+    "work"
+  ],
   "name": "Recurring Status Report",
   "description": "Produce a recurring (weekly/biweekly) status report by gathering signals from the team's tools and writing a tight, skimmable update for stakeholders. Scopes the report template and the exact data sources FIRST (sections, audience, reporting window, RAG/health convention), then a developer gathers the raw signals from issue trackers, PRs, metrics, and notes into a facts file, then a copywriter writes the polished report strictly from those gathered facts. Scoping the template before gathering is what keeps every recurring issue consistent and prevents the model from padding with prose. Use for weekly status updates, sprint reports, project health reports, stakeholder updates, and exec summaries.",
   "tags": [

package/data/craftbook-templates/su/subscription-audit/manifest.json

@@ -4,6 +4,10 @@
   "id": "subscription-audit",
   "role": "maintenance-review",
   "category": "business",
+  "interests": [
+    "home",
+    "business"
+  ],
   "name": "Audit Recurring Subscriptions",
   "description": "Audit a set of transactions or a vendor list to find every recurring subscription, normalize each to a monthly cost, surface duplicates, price hikes, and zombie/unused services, and produce a prioritized cancel/keep recommendation report. Locks the recurrence-detection rule, the normalization (to monthly), and the recommendation criteria FIRST, then detects and analyzes the recurring charges, then writes a clear report whose every recommendation is backed by the evidence in the data. Defining what counts as 'recurring' and how to rank cancel candidates before analyzing is what makes the audit actionable rather than a list of guesses.",
   "tags": [

package/data/craftbook-templates/su/survey-analysis/manifest.json

@@ -4,6 +4,10 @@
   "id": "survey-analysis",
   "role": "general",
   "category": "research",
+  "interests": [
+    "data",
+    "work"
+  ],
   "name": "Survey Analysis",
   "description": "Analyze survey responses into a clear summary of what respondents actually said, across both quantitative (rating/multiple-choice) and open-text questions. Scopes the questions, response types, and segments FIRST, then analyzes — tallying closed questions and theming open-text comments as a data-analyst, then writes a findings summary with the headline results, segment differences, and representative quotes. Use this for analyzing survey results, summarizing a questionnaire, NPS/feedback analysis, theming open-ended responses, or a survey readout.",
   "tags": [

package/data/craftbook-templates/ta/tailor-resume/manifest.json

@@ -4,6 +4,9 @@
   "id": "tailor-resume",
   "role": "general",
   "category": "business",
+  "interests": [
+    "learning"
+  ],
   "name": "Tailor Résumé to a Posting",
   "description": "Adapt an EXISTING résumé to a specific job posting — a fit map of must-hit requirements first, then a tailored variant that re-orders and re-words real experience without inventing any. Distinct from building a résumé from scratch (see Résumé / CV): this book starts from a base résumé plus a posting and produces the targeted variant along with honest gap notes for the cover letter and interview. Use per serious application in a job search.",
   "tags": [

package/data/craftbook-templates/ti/tidy-spreadsheet/manifest.json

@@ -0,0 +1,26 @@
+{
+  "schemaVersion": 1,
+  "kind": "craftbook-template",
+  "id": "tidy-spreadsheet",
+  "role": "general",
+  "category": "research",
+  "interests": [
+    "data"
+  ],
+  "name": "Tidy up a spreadsheet",
+  "description": "Clean up a messy CSV or TSV file: trims stray spaces, puts email addresses in lower case and dates in one format, settles on one spelling of each repeated value, and removes duplicate rows. You get the tidy file plus a note of every change and of everything it could not fix, such as empty cells and dates that read two ways. It never guesses a missing value.",
+  "tags": [
+    "gallery",
+    "first-project",
+    "spreadsheet",
+    "csv",
+    "data-cleaning",
+    "tidy",
+    "duplicates"
+  ],
+  "maintainer": {
+    "name": "Gezel"
+  },
+  "license": "MIT",
+  "yankedVersions": []
+}

package/data/craftbook-templates/ti/tidy-spreadsheet/versions/1.0.0/craftbook.json

@@ -0,0 +1,183 @@
+{
+  "id": "tidy-spreadsheet",
+  "name": "Tidy up a spreadsheet",
+  "description": "Clean up a messy CSV or TSV file: trims stray spaces, puts email addresses in lower case and dates in one format, settles on one spelling of each repeated value, and removes duplicate rows. You get the tidy file plus a note of every change and of everything it could not fix, such as empty cells and dates that read two ways. It never guesses a missing value.\n\nIt works on the spreadsheet you choose when you launch it: a file in this project, or one you pick from your computer. Your file is never changed; the tidy copy lands in the task folder. No file to hand? Try it on the sample, a volunteer club's messy member list.",
+  "entryStepId": "tidy",
+  "triggers": [
+    "tidy up a spreadsheet",
+    "clean up a spreadsheet",
+    "clean a csv",
+    "tidy a csv",
+    "fix a messy spreadsheet",
+    "remove duplicate rows"
+  ],
+  "samples": [
+    {
+      "id": "club-members",
+      "title": "a volunteer club's messy member list",
+      "param": "source",
+      "files": [
+        "samples/club-members/members.csv"
+      ]
+    }
+  ],
+  "paramSchema": {
+    "type": "object",
+    "required": [
+      "source"
+    ],
+    "properties": {
+      "source": {
+        "type": "string",
+        "title": "Spreadsheet",
+        "description": "The CSV or TSV file to tidy: a file in this project, or one you pick from your computer. It is read, never changed.",
+        "input": {
+          "kind": "file",
+          "accept": [
+            ".csv",
+            ".tsv"
+          ]
+        }
+      },
+      "workPath": {
+        "type": "string",
+        "title": "Working folder",
+        "description": "Per-task working folder in the artifacts drawer. Defaults to this task's own folder so runs never collide; override with a stable name when you deliberately want runs to share files.",
+        "default": "{{task.dir}}",
+        "askUser": false
+      }
+    }
+  },
+  "steps": [
+    {
+      "id": "tidy",
+      "name": "Tidy the spreadsheet",
+      "description": "Write a cleaned copy of the data and a note of every change.",
+      "prompt": "Tidy the spreadsheet in the `source` input into a clean CSV file, and say what you changed.\n\n1. Open the file list `{{task.dir}}/inputs/source.json` with `read_artifact`. It names the spreadsheet and the drawer it is in.\n2. Read the spreadsheet end to end with the tool named on its `source` line under Invocation parameters. Count its data rows.\n3. Clean it. Keep every column, in the same order, and every real row:\n   - trim spaces at the start and end of every cell, and turn a double space inside a cell into one;\n   - write email addresses in lower case;\n   - write every date as YYYY-MM-DD. A date that reads two ways, such as 03/04/2025, stays as it is and goes under What I could not fix;\n   - when one value is spelled several ways in a column (yes, Yes, YES), use its most common spelling;\n   - remove a row that is an exact copy of an earlier row after this cleaning, and keep the first;\n   - leave an empty cell empty. Never guess a missing value.\n4. Write the cleaned data to `{{workPath}}/tidy.csv` with `write_artifact`: plain comma-separated text with no code fence, the header row first, one line per row, every row with as many cells as the header, and any cell that contains a comma wrapped in double quotes.\n5. Then write `{{workPath}}/changes.md` with `write_artifact`, under exactly these two headings:\n   - `## What I changed`: how many data rows you read and how many you wrote, each duplicate you removed, and each kind of fix with how many cells it changed.\n   - `## What I could not fix`: each empty cell in a column most rows fill, each date that reads two ways, and anything else you left alone, with the row it is on. Write `Nothing.` if there is none.\n\nUse only values from the file. Never invent a row or a value. If the file has more than 150 data rows, tidy the first 150 and say first, under What I could not fix, that the rest were not tidied.\n\nIf the spreadsheet is empty or cannot be read, write neither file. Write a task note with `write_task_note` that names the file you tried and what you saw, then end your turn.",
+      "suggestedRole": "data-analyst",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "artifact",
+        "additionalOutputMedia": [
+          "task-note"
+        ]
+      },
+      "consumes": [
+        {
+          "file": "{{task.dir}}/inputs/source.json",
+          "artifact": true
+        }
+      ],
+      "advanceWhen": {
+        "file": "{{workPath}}/changes.md",
+        "minBytes": 1,
+        "sniff": "nonempty",
+        "artifact": true
+      },
+      "gate": {
+        "at": "completion",
+        "checks": [
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/tidy.csv",
+            "bytes": 60,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/tidy.csv",
+            "pattern": "^[^\\n]*[A-Za-z][^\\n]*,[^\\n]*\\r?\\n[^\\n]*\\S",
+            "label": "a header row of column names, then the data rows",
+            "artifact": true
+          },
+          {
+            "kind": "csvShape",
+            "file": "{{workPath}}/tidy.csv",
+            "minRows": 1,
+            "consistentColumns": true,
+            "artifact": true
+          },
+          {
+            "kind": "minBytes",
+            "file": "{{workPath}}/changes.md",
+            "bytes": 150,
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/changes.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*What I changed",
+            "flags": "i",
+            "label": "a \"## What I changed\" section",
+            "artifact": true
+          },
+          {
+            "kind": "contains",
+            "file": "{{workPath}}/changes.md",
+            "pattern": "(?:^|\\n)#{1,3}\\s*What I could not fix",
+            "flags": "i",
+            "label": "a \"## What I could not fix\" section",
+            "artifact": true
+          }
+        ],
+        "onReject": "tidy",
+        "maxAttempts": 3
+      },
+      "next": "finish"
+    },
+    {
+      "id": "finish",
+      "name": "Finish",
+      "description": "The deliverable passed its checks. Stamp a short summary and report DONE.",
+      "prompt": "The deliverable passed its checks. Write a one-paragraph DONE summary to task notes via `write_task_note`: what you made, the deliverable path(s), and a one-line confirmation that each required section is there. Then report DONE.",
+      "suggestedRole": "data-analyst",
+      "toolPolicy": {
+        "disallowBuiltinToolsets": [
+          "ai-apps",
+          "archives",
+          "artifacts",
+          "audio",
+          "browser-automation",
+          "code-execution",
+          "craftbooks",
+          "data-tables",
+          "entity-intel",
+          "git",
+          "image-intel",
+          "images",
+          "role-delegation",
+          "role-delegation-escalation",
+          "security-intel",
+          "team-management",
+          "videos",
+          "web",
+          "workspace-fs-write"
+        ],
+        "outputMedium": "task-note"
+      },
+      "terminal": true
+    }
+  ],
+  "version": "1.0.0",
+  "releasedAt": "2026-10-12T00:00:00Z",
+  "minGezelVersion": "1.26285"
+}