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
configurationRoutes evo package-info, settings, logfile, and IPython shell workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill for the non-trajectory, non-metric, non-result workflows around evo's global settings, package metadata, logfile access, and preloaded IPython shell.
evo_config show, set, generate, resetevo pkg --info, --version, --pyversion, --license, --location, --logfile, --open_log, --clear_logevo cat_logevo_ipython../python-api/SKILL.md, except for simple cross-links.references/cli-reference.md for exact flags and output shapes.references/settings.md for settings paths, default values, and merge/reset rules.references/workflows.md for noninteractive recipes.references/troubleshooting.md when a command fails or behaves unexpectedly.~/.evo/settings.json; the global logfile is ~/.evo/evo.log.show --brief --no_color is the safest read-only settings check.generate is read-only unless you pass -o/--out.set and reset mutate the chosen settings file and require write access.evo_ipython requires IPython on PATH and will create the evo profile on first launch if needed.evo cat_log is unavailable on Windows.test/demos/config_demo.sh was intentionally not bundled because it mutates settings and waits for stdin; the CLI recipes above are the safe replacement.No scripts/config_smoke.py is bundled. The safe verification paths are already covered by the CLI itself (show, generate, pkg, cat_log, evo_ipython), and a helper that edits settings would add mutation risk without adding safety.