model-data-assets

Manages model weight and dataset asset registries across local Mac and remote servers.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/Kirrito-k423/AutoResearch --skill model-data-assets-kirrito-k423
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: model-data-assets
Source: https://github.com/Kirrito-k423/AutoResearch/tree/main/workspace-core/model-data-assets
Command: npx skills add https://github.com/Kirrito-k423/AutoResearch --skill model-data-assets-kirrito-k423

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Tracking where large model weights and datasets actually live across a local Mac and multiple remote NPU servers is error-prone, leading to duplicate downloads, wasted bandwidth, and adapters pointing at stale or missing paths. ## Core Features & Use Cases - Centralized Asset Registry: Maintains config/data.yaml as the source of truth for each asset's canonical id, source ids, size, local path, and per-server remote paths. - Remote Discovery Before Download: Scans mandatory roots like /home/data, /data*, and /home/*/data on remote machines and records large findings under discovered_large_assets before any network download. - Source Priority and Proxy Fallback: Prefers ModelScope, falls back to Hugging Face, and retries through a local proxy at http://127.0.0.1:7890 when access fails from China. - Use Case: Before training with the Verl adapter on server A2-AK-225, use this Skill to check whether Qwen3.5-2B already exists on the remote host, record its verified path in the registry, and only download if no usable copy is found. ## Quick Start Use the model-data-assets skill to locate or download the Qwen3.5-2B model and the geo3k dataset, then record their local and remote paths in config/data.yaml.

Frequently Asked Questions about model-data-assets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage model weights and datasets across local and remote servers?▼

Record every asset in config/data.yaml with its canonical id, source ids, local path, and per-server remote paths under remotes.<server>. Adapters read this registry before downloading, so paths stay consistent across machines.

How to avoid re-downloading large models that already exist on a remote server?▼

Run remote discovery first, scanning /home/data, /data*, and /home/*/data plus supplemental weight roots. Record paths over 10GB in discovered_large_assets, verify them against the requested asset, and reuse the verified path instead of downloading.

Should I download models from ModelScope or Hugging Face?▼

Try ModelScope first, then fall back to Hugging Face when ModelScope is missing, incomplete, or unavailable. Record both source ids in the registry when they differ so adapters never guess.

What happens when Hugging Face or GitHub is unreachable from China?▼

Retry through the local proxy at http://127.0.0.1:7890 on the Mac. If the remote server has no network access, download locally and stage the files over SSH, or use the network skill's proxy and tunnel path.

When should assets be stored locally versus on a remote server?▼

Keep assets within the configured local_asset_limit_gb (normally 5 GB) under the Mac cache root. Place larger assets on a remote server under a stable remote root, and always record the server name, host, and absolute path.

Can I store API tokens or passwords in the asset registry?▼

No. The registry must never contain tokens, passwords, cookies, SSH keys, or credential-bearing URLs. It records only logical identity and physical locations such as paths, server names, and hosts.