AGENT SKILL

automation-schedules-sensors

Define, debug, and test Dagster schedules, sensors, asset sensors, run status sensors, declarative automation conditions, freshness automation, and backfill policies.

License 许可
Apache-2.0
最近更新
2026-09-03
Stars
★ 351
Forks
27

01 前言 Front Matter

name
automation-schedules-sensors
license
Apache 2.0
metadata
{ "disco-role": "operating" }
description
Define, debug, and test Dagster schedules, sensors, asset sensors, run status sensors, declarative automation conditions, freshness automation, and backfill policies.
disable-model-invocation
true

02 资源文件 4

03 SKILL.md 正文

Automation: schedules, sensors, and declarative conditions

Use this sub-skill when the task is about time-based or event-based automation in Dagster code:

  • ScheduleDefinition, @schedule, cron schedules, time zones, schedule run config/tags, and schedule unit tests.
  • @sensor, RunRequest, SkipReason, SensorResult, cursor handling, run keys, resource-backed sensors, and sensor unit tests.
  • @asset_sensor, run status sensors, failure sensors, and tests using built Dagster context objects.
  • AutomationCondition, AutomationConditionSensorDefinition, freshness-driven automation, and BackfillPolicy for partitioned assets.

Route elsewhere when the task is primarily about core asset modeling, deployment/daemon operations, or starting/stopping local CLI processes.

Start here

Quick routing

  • Need a cron trigger for a job or asset job: use @schedule or ScheduleDefinition; test with build_schedule_context() and .evaluate_tick().
  • Need polling logic or external-event logic: use @sensor, stable RunRequest(run_key=...), and context.update_cursor(...) or SensorResult(cursor=...).
  • Need to react to one asset materialization: use @asset_sensor; prefer declarative automation for asset dependency propagation when custom per-event run config is not required.
  • Need to react to job success/failure: use @run_status_sensor or @run_failure_sensor; avoid triggering an infinite loop when the requested job can produce the same monitored status.
  • Need asset-centric freshness, dependency, or backfill behavior: prefer AutomationCondition.on_cron(), AutomationCondition.eager(), AutomationCondition.on_missing(), freshness policies/checks, and BackfillPolicy.

Definition checklist

  • Put schedules and sensors in the repository or Definitions(schedules=[...], sensors=[...]) that loads with the target jobs/assets.
  • Use only one target style per schedule/sensor: job, job_name, jobs, asset_selection, or target as accepted by that definition.
  • Give every multi-request schedule a non-empty run_key on each RunRequest; use stable sensor run keys only when duplicate suppression should survive cursor resets.
  • Keep schedule/sensor evaluation pure enough for unit tests: move network/credentialed calls behind resources that can be stubbed in build_*_context.
  • For declarative automation, ensure the automation condition sensor is present and enabled in the deployment; route daemon lifecycle and deployment checks to the deployment operations skill.

04 同仓库更多 Skills

VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-triton-opt

Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-solve

END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-skill

PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-pattern-fusion

Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-orchestrate

Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

passnet-feedback

Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).

★ 351