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
office-benchmarksRoutes LibMTL's Office-31 and Office-Home multi-input classification workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill for the Office-31 and Office-Home benchmark workflows.
scripts/office_runtime/.scripts/main.py plus the install entry point
scripts/install_office_runtime.py.Choose this route when the user asks things like:
multi_input be true here?"../../references/configuration.md for the shared flags and method kwargs.../../references/troubleshooting.md for cross-cutting install and runtime
failures.references/workflows.md for the command pattern.references/task-contracts.md for the task dictionary, loader, and
encoder/decoder shapes.references/data-layouts.md for the expected split and image trees.references/troubleshooting.md for office-specific failures.office-31 or office-home.scripts/check_office_data.py to confirm the bundled split files and
image root before training.scripts/install_office_runtime.py when you need the console entry point.scripts/main.py or the installed
libmtl-office entry point, not through an external checkout.resnet18 backbone to download or use cache.multi_input must be True.amazon, dslr, webcamArt, Clipart, Product, Real_WorldLeave this sub-skill when the user has the correct dataset family, split files, run command, and failure-recovery notes for the office benchmark.