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
hub-and-cliUse ModelScope Hub, cache, download/upload, and CLI workflows safely from the modelscope package.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is about ModelScope Hub access, the modelscope/ms command line, downloading repositories or files, upload command selection, authentication boundaries, endpoint/cache settings, offline cache reuse, or cache troubleshooting.
snapshot_download, dataset_snapshot_download, model_file_download, dataset_file_download, HubApi, credentials, endpoint variables, or modelscope_hub compatibility behavior: read Hub API reference.modelscope_hub, or local_dir/cache_dir confusion: read troubleshooting.python scripts/plan_download.py --help, then use the generated CLI command or Python snippet after approval. The script performs no network calls.../pipelines-and-models/SKILL.md.MsDataset.load, dataset streaming, dataset recipe validation, or config/file I/O after a dataset snapshot is available, route to ../datasets-config/SKILL.md.../serving-export-and-tools/SKILL.md.modelscope/ms CLI, Python download helper, or HubApi.owner/name), repo type (model or dataset for most downloads), revision, and whether the target is public or private.local_dir for a user-visible copy, cache_dir/MODELSCOPE_CACHE for reusable cache, and local_files_only=True only when the cache is already populated.token= parameters over literal tokens in shell history.