agentleFS
hyf020908hyf020908/modelscope-skills/skills/modelscope-cli/SKILL.md

modelscope-cli

Skill4 starsChanged 8 months agoApache-2.0View on GitHub

Execute ModelScope Hub login, create, download, and upload tasks from plain-language requests with the official CLI.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the task is fundamentally a repository operation and the official modelscope CLI is the most direct path.

    line 8
  2. Distinctive:

    create model or dataset repo

    line 20
  3. Distinctive:

    Check whether authentication is already available.

    line 27
  4. Distinctive:

    Keep local output directories explicit.

    line 28
  5. Distinctive:

    Keep upload target paths explicit.

    line 29
  6. Distinctive:

    If credentials are missing, still prepare the exact command sequence.

    line 30
  7. Distinctive:

    Never guess the repo type.

    line 41
  8. Distinctive:

    Never use ambiguous destination paths.

    line 42
  9. Very specific:

    Prefer deterministic --local_dir downloads.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ModelScope CLI

Use this skill when the task is fundamentally a repository operation and the official modelscope CLI is the most direct path.

Request Style

  • Accept requests like:
    • Download this model locally.
    • 创建一个新的数据集仓库并上传 data/ 目录。
  • Translate the request into explicit CLI commands with explicit repo types and paths.

Core Uses

  • login
  • create model or dataset repo
  • download full or partial snapshots
  • upload files or folders

Workflow

  1. Determine the repo type.
  2. Check whether authentication is already available.
  3. Keep local output directories explicit.
  4. Keep upload target paths explicit.
  5. If credentials are missing, still prepare the exact command sequence.

When Not To Use

  • heavy remote compute
  • dataset transformation logic that deserves a script
  • complex metadata normalization

Guardrails

  • Never hardcode tokens.
  • Never guess the repo type.
  • Never use ambiguous destination paths.
  • Prefer deterministic --local_dir downloads.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.