Automated pipeline that takes a company name and produces a custom Tessl skill plus an eval report showing per-scenario lift (baseline agent vs with-skill agent). A1 MVP cell of the produce/consume × personalization 2x2.
88
86%
Does it follow best practices?
Impact
89%
1.45xAverage score across 13 eval scenarios
Advisory
Suggest reviewing before use
The ML platform team at your company has a new engineer joining next week. She will be responsible for running the automated skill-build-and-evaluate pipeline for new company targets. The pipeline takes a pre-selected target (stored in a selection.json file) and runs it through scaffold generation, scenario creation, quality review, eval execution, and report generation — all orchestrated via the tessl CLI and a set of helper Python scripts.
To help her get up to speed quickly, her tech lead wants a single, executable shell script called pipeline.sh that encodes every step of the pipeline in the right order. The script should be self-contained: given a selection.json path as its first argument, it should run the full pipeline without any additional human input. It must handle the case where the target has already been scaffolded in a previous run (the scaffold directory already exists), and it must include logic for what to do if the quality review gate is not met or if the eval run encounters an error.
The company's standard is:
The selection context is in inputs/selection.json and its linked discovery data is in inputs/discovery.json. Write pipeline.sh using those as the concrete example paths.
Produce a single file: pipeline.sh
The script should:
selection.json as its first argument (default to inputs/selection.json if not provided)run_dir (the directory of the selection file) as the base path for all artifactsevals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
skills
batch-driver
build-and-evaluate
company-list-filter
discovery
discovery-produce
select-target