Complex pixi task workflows and orchestration. Use when building task dependency chains, configuring caching with inputs/outputs, creating parameterized tasks, or setting up CI pipelines—e.g., "pixi task depends-on", "task caching for build automation", "multi-environment test matrices".
99
100%
Does it follow best practices?
Impact
95%
1.26xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Task dependency chains and caching
depends-on used for ordering
100%
100%
Diamond pattern applied
100%
100%
Download cached by output
100%
100%
Processing task uses inputs and outputs
100%
100%
Glob patterns in inputs
0%
0%
No redundant transitive deps
100%
100%
Aggregator task present
100%
100%
Source files tracked (not derived dirs)
100%
100%
All file dependencies in inputs
50%
75%
Report task cached correctly
100%
100%
Tasks use depends-on not just inputs for ordering
100%
100%
Cross-environment testing and CI pipeline
Cross-env depends-on syntax
100%
100%
Multiple environments defined
100%
100%
Feature-per-version pattern
100%
100%
Solve group used
50%
100%
Clear environment names
100%
100%
setup-pixi action version
0%
100%
Pixi cache enabled in CI
0%
100%
Single CI command
100%
100%
Aggregator task present
100%
100%
depends-on for order
100%
100%
Platform-specific tasks and parameterized workflows
Platform task sections used
100%
100%
Platform deps section used
100%
100%
Same task name across platforms
100%
100%
Agnostic task depends on platform task
100%
58%
MiniJinja args field
0%
100%
MiniJinja template in cmd
0%
100%
Template in inputs or outputs
0%
100%
depends-on for ordering
100%
100%
No undocumented task keys
100%
100%
b74de5e
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.