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
speedster-optimizationGuides Speedster inference optimization workflows, compiler/backend selection, save/load, and troubleshooting for optimized models.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the user wants to accelerate an existing model, choose optimize_model parameters, save or load an optimized learner, or understand why a compiler/backend path was selected or skipped.
metric_drop_ths, optimization_time, dynamic_info, ignore_compilers, ignore_compressors, or device.references/api-reference.md for verified function signatures, accepted inputs, and return behavior.references/workflows.md for end-to-end recipes and parameter choices.references/framework-recipes.md for framework-specific notes and compiler/backend selection.references/troubleshooting.md for install/import/backend and data-format failures.../nebullvm-backends/SKILL.md when the question is really about DataManager, device parsing, compiler lists, or optional dependency probes.scripts/speedster_quick_probe.py when you want a safe import/signature/backend smoke probe.optimize_model, save_model, and load_model.If the user asks “how do I make this model faster?”, start here. If the user asks “which backend/compiler package should I install?”, read the NebullVM backend sub-skill next.