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
network-inferenceUse pySCENIC and Arboreto to infer co-expression adjacencies, add TF-target correlations, and build TF-target modules before motif pruning.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task asks for pySCENIC Phase I work: GRNBoost2 or GENIE3 adjacency inference, Dask-free Arboreto multiprocessing, adding Pearson correlations, or converting adjacencies into TF-target modules.
add_correlation() and modules_from_adjacencies() signatures, dataframe schemas, correlation behavior, and module-construction defaults.pyscenic grn, pyscenic add_cor, arboreto_with_multiprocessing.py, and Python recipes for module construction.min_genes filtering.pyscenic grn for Dask-backed GRNBoost2/GENIE3, or the bundled workflows for arboreto_with_multiprocessing.py when Dask is the failure point.pyscenic add_cor or pyscenic.utils.add_correlation() to add rho and regulation columns before module construction or diagnostics.pyscenic.utils.modules_from_adjacencies() when a task needs unpruned activating or repressing modules from weighted adjacencies.Run the bundled helper before writing commands for a user environment:
python scripts/grn_multiprocessing_smoke.py --help
python scripts/grn_multiprocessing_smoke.py --make-fixtures ./pyscenic-grn-smoke --run-api-smoke
The helper checks imports and prints command templates. It creates only tiny local fixtures when requested and does not download data, run GRNBoost2/GENIE3, train models, or mutate existing files.