executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
cli-and-containersOrchestrate safe pySCENIC CLI, command-file, container, and HPC workflows across GRN, motif pruning, and AUCell.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task needs an end-to-end pySCENIC command plan, container invocation, @args.txt command file, resource checklist, or operational decision between local, container, and scheduler-backed execution.
grn -> ctx -> aucell templates, @args.txt rules, output suffix choices, and resource checks.@args.txt quoting, output extension mistakes, import/help failures, Dask/HPC filesystems, and scanpy extras.pyscenic grn, optional pyscenic add_cor, pyscenic ctx, and pyscenic aucell commands.--check-help before expensive runs; add --emit-template or --write-args-dir to create dry-run-ready command templates.python scripts/pyscenic_cli_smoke.py --check-help --emit-template
The helper only probes command help and prints templates by default. It does not download ranking databases, run GRN inference, launch motif pruning, score AUCell, start containers, or mutate existing files unless --write-args-dir or --make-fixtures is explicitly supplied.