[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78VC1H48N0P664RZQ2QH3CD":3,"skill-same:01M78VC1H48N0P664RZQ2QH3CD":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M78VC1H48N0P664RZQ2QH3CD","automation-schedules-sensors",null,"Define, debug, and test Dagster schedules, sensors, asset sensors, run status sensors, declarative automation conditions, freshness automation, and backfill policies.","VectorSpaceLab\u002FAREX-Skill","VectorSpaceLab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F180637102?v=4","01M7538C5WPSJGWF7KHR4EFZ9F","01M7538C6R2GFP53NPXTCZNBRT",351,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fdagster\u002Fsub-skills\u002Fautomation-schedules-sensors\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: automation-schedules-sensors\ndescription: \"Define, debug, and test Dagster schedules, sensors, asset sensors,\n  run status sensors, declarative automation conditions, freshness automation,\n  and backfill policies.\"\ndisable-model-invocation: true\nmetadata:\n  disco-role: operating\nlicense: Apache 2.0\n---\n\n# Automation: schedules, sensors, and declarative conditions\n\nUse this sub-skill when the task is about time-based or event-based automation in Dagster code:\n\n- `ScheduleDefinition`, `@schedule`, cron schedules, time zones, schedule run config\u002Ftags, and schedule unit tests.\n- `@sensor`, `RunRequest`, `SkipReason`, `SensorResult`, cursor handling, run keys, resource-backed sensors, and sensor unit tests.\n- `@asset_sensor`, run status sensors, failure sensors, and tests using built Dagster context objects.\n- `AutomationCondition`, `AutomationConditionSensorDefinition`, freshness-driven automation, and `BackfillPolicy` for partitioned assets.\n\nRoute elsewhere when the task is primarily about core asset modeling, deployment\u002Fdaemon operations, or starting\u002Fstopping local CLI processes.\n\n## Start here\n\n- For implementation patterns and API choices, read [references\u002Fapi-reference.md](references\u002Fapi-reference.md).\n- For end-to-end workflows and test commands, read [references\u002Fworkflows.md](references\u002Fworkflows.md).\n- For common failures and fixes, read [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md).\n- To safely inspect what CLI preview commands would be used, run `python skills\u002Fdagster\u002Fsub-skills\u002Fautomation-schedules-sensors\u002Fscripts\u002Fpreview_sensor_schedule.py --help`.\n\n## Quick routing\n\n- Need a cron trigger for a job or asset job: use `@schedule` or `ScheduleDefinition`; test with `build_schedule_context()` and `.evaluate_tick()`.\n- Need polling logic or external-event logic: use `@sensor`, stable `RunRequest(run_key=...)`, and `context.update_cursor(...)` or `SensorResult(cursor=...)`.\n- 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.\n- Need to react to job success\u002Ffailure: use `@run_status_sensor` or `@run_failure_sensor`; avoid triggering an infinite loop when the requested job can produce the same monitored status.\n- Need asset-centric freshness, dependency, or backfill behavior: prefer `AutomationCondition.on_cron()`, `AutomationCondition.eager()`, `AutomationCondition.on_missing()`, freshness policies\u002Fchecks, and `BackfillPolicy`.\n\n## Definition checklist\n\n- Put schedules and sensors in the repository or `Definitions(schedules=[...], sensors=[...])` that loads with the target jobs\u002Fassets.\n- Use only one target style per schedule\u002Fsensor: `job`, `job_name`, `jobs`, `asset_selection`, or `target` as accepted by that definition.\n- 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.\n- Keep schedule\u002Fsensor evaluation pure enough for unit tests: move network\u002Fcredentialed calls behind resources that can be stubbed in `build_*_context`.\n- 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.\n","# Automation: schedules, sensors, and declarative conditions\n\nUse this sub-skill when the task is about time-based or event-based automation in Dagster code:\n\n- `ScheduleDefinition`, `@schedule`, cron schedules, time zones, schedule run config\u002Ftags, and schedule unit tests.\n- `@sensor`, `RunRequest`, `SkipReason`, `SensorResult`, cursor handling, run keys, resource-backed sensors, and sensor unit tests.\n- `@asset_sensor`, run status sensors, failure sensors, and tests using built Dagster context objects.\n- `AutomationCondition`, `AutomationConditionSensorDefinition`, freshness-driven automation, and `BackfillPolicy` for partitioned assets.\n\nRoute elsewhere when the task is primarily about core asset modeling, deployment\u002Fdaemon operations, or starting\u002Fstopping local CLI processes.\n\n## Start here\n\n- For implementation patterns and API choices, read [references\u002Fapi-reference.md](references\u002Fapi-reference.md).\n- For end-to-end workflows and test commands, read [references\u002Fworkflows.md](references\u002Fworkflows.md).\n- For common failures and fixes, read [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md).\n- To safely inspect what CLI preview commands would be used, run `python skills\u002Fdagster\u002Fsub-skills\u002Fautomation-schedules-sensors\u002Fscripts\u002Fpreview_sensor_schedule.py --help`.\n\n## Quick routing\n\n- Need a cron trigger for a job or asset job: use `@schedule` or `ScheduleDefinition`; test with `build_schedule_context()` and `.evaluate_tick()`.\n- Need polling logic or external-event logic: use `@sensor`, stable `RunRequest(run_key=...)`, and `context.update_cursor(...)` or `SensorResult(cursor=...)`.\n- 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.\n- Need to react to job success\u002Ffailure: use `@run_status_sensor` or `@run_failure_sensor`; avoid triggering an infinite loop when the requested job can produce the same monitored status.\n- Need asset-centric freshness, dependency, or backfill behavior: prefer `AutomationCondition.on_cron()`, `AutomationCondition.eager()`, `AutomationCondition.on_missing()`, freshness policies\u002Fchecks, and `BackfillPolicy`.\n\n## Definition checklist\n\n- Put schedules and sensors in the repository or `Definitions(schedules=[...], sensors=[...])` that loads with the target jobs\u002Fassets.\n- Use only one target style per schedule\u002Fsensor: `job`, `job_name`, `jobs`, `asset_selection`, or `target` as accepted by that definition.\n- 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.\n- Keep schedule\u002Fsensor evaluation pure enough for unit tests: move network\u002Fcredentialed calls behind resources that can be stubbed in `build_*_context`.\n- 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.\n",{"name":5,"license":23,"metadata":24,"description":7,"disable-model-invocation":26},"Apache 2.0",{"disco-role":25},"operating",true,"main","ac3fe1afa80fb9a09775ecfb2b6cc3ba850a2db6","skills\u002Frepositories\u002Frepo-skills\u002Fdagster\u002Fsub-skills\u002Fautomation-schedules-sensors",27,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab","2026-09-03 10:25:21",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":26},[36,39,42],{"tool":37,"command":38},"npx","npx skills add VectorSpaceLab\u002FAREX-Skill --skill automation-schedules-sensors",{"tool":40,"command":41},"bunx","bunx skills add VectorSpaceLab\u002FAREX-Skill --skill automation-schedules-sensors",{"tool":43,"command":44},"pnpm","pnpm dlx skills add VectorSpaceLab\u002FAREX-Skill --skill automation-schedules-sensors","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fdagster\u002Fsub-skills\u002Fautomation-schedules-sensors\u002FSKILL.md",[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fapi-reference.md","REFERENCE","参考文档",8258,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fdagster\u002Fsub-skills\u002Fautomation-schedules-sensors\u002Freferences\u002Fapi-reference.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Ftroubleshooting.md",8255,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fdagster\u002Fsub-skills\u002Fautomation-schedules-sensors\u002Freferences\u002Ftroubleshooting.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fworkflows.md",7148,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fdagster\u002Fsub-skills\u002Fautomation-schedules-sensors\u002Freferences\u002Fworkflows.md",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Fpreview_sensor_schedule.py","SCRIPT","脚本",5226,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fdagster\u002Fsub-skills\u002Fautomation-schedules-sensors\u002Fscripts\u002Fpreview_sensor_schedule.py",[68,75,82,89,96,103],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M799NYSH1R3RVAHSM2D88Y84","passnet-triton-opt","Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block\u002Fgrid\u002Fwarp 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.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-triton-opt\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M799NS5APEC0N1FZ7XZVW6BN","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.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-solve\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M799NNY9BKSM21V5R7QVTBJX","passnet-skill","PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under .\u002Fpass_dir\u002F, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-skill\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M799NHH6NP7Z1RK77KGXAN6S","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()\u002Freplacement_args()\u002Freplacement_func() files, when a pass \"failed to match\", or when deciding how to fuse multiple kernels\u002Fops.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-pattern-fusion\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M799ND2J4WNC2PGAZ0A06NDF","passnet-orchestrate","Round\u002Fbatch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep\u002Frevert 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.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-orchestrate\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M799N8SBTMY02ZDG2AZF5ZWE","passnet-feedback","Fast, deterministic feedback for PassNet work: pre-flight pattern\u002Fmatch 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).","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-feedback\u002FSKILL.md",[],[]]