job

Run predefined transform pipelines via the Starlake CLI alias.

209|30|Updated Sep 18, 2021
One-click install
npx skills add https://github.com/starlake-ai/starlake --skill job
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: job
Source: https://github.com/starlake-ai/starlake/tree/main/.agent/skills/job
Command: npx skills add https://github.com/starlake-ai/starlake --skill job

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a lightweight alias to run transform workflows, reducing the need to retype long CLI commands and lowering the barrier to reuse existing pipelines.

Core Features & Use Cases

  • Alias to transform: execute transform workflows with a shorter, simpler command.
  • Consistency: reuse established transform configurations without duplication.
  • Use Case: trigger a standard data-cleaning pipeline in a single command across multiple datasets.

Quick Start

Run a transform workflow by executing starlake job with the appropriate options for your transform.

Frequently Asked Questions about job

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a transform job with a shorter command in Starlake?

To run a transform job with a shorter command, use the job alias to execute predefined transform workflows via the Starlake CLI, reducing the need to retype long commands.

What is a CLI alias for transform workflows used for?

A CLI alias for transform workflows is used to trigger established data pipelines quickly, ensuring consistency by reusing existing transform configurations without duplication across datasets.

How do I trigger a predefined data pipeline across multiple datasets?

You trigger a predefined data pipeline across multiple datasets by executing the job alias, which applies existing transform definitions to run standard workflows like data cleaning in a single command.

Do I need existing transform definitions to use the job command?

Yes, you need existing transform definitions to use the job command, because it relies on predefined transform pipeline configurations and acts purely as an alias to invoke them via the Starlake CLI.

What is the best way to reuse established transform configurations without duplication?

The best way to reuse established transform configurations without duplication is using a lightweight CLI alias, which triggers standard transform pipelines consistently while lowering the barrier to reusing existing workflows.