agentleFS
Sign inStart free
hyf020908hyf020908/modelscope-skills/skills/modelscope-mcp/SKILL.md

modelscope-mcp

Skill4 starsChanged 8 months agoApache-2.0View on GitHub

Configure the official ModelScope MCP server from plain-language setup requests and use it for tool-based Hub discovery.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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. Distinctive:

    Use this skill when the runtime supports MCP and the user wants ModelScope search or metadata access exposed as tools.

    line 8
  2. Distinctive:

    Check whether MCP config already exists.

    line 18
  3. Very specific:

    Add the minimal valid uvx modelscope-mcp-server config only if needed.

    line 19
  4. Distinctive:

    Keep token management outside repository files.

    line 20
  5. Distinctive:

    Use CLI or SDK only when MCP is unavailable.

    line 21
  6. Distinctive:

    Never invent undocumented MCP tool names.

    line 44
  7. Very specific:

    Never store MODELSCOPE_API_TOKEN in checked-in files.

    line 45
  8. Distinctive:

    Keep the config minimal.

    line 46

≈ “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 MCP

Use this skill when the runtime supports MCP and the user wants ModelScope search or metadata access exposed as tools.

Request Style

  • Accept requests such as:
    • Set up ModelScope MCP for this client.
    • 让 agent 可以通过 MCP 搜索模型和数据集。

Workflow

  1. Check whether MCP config already exists.
  2. Add the minimal valid uvx modelscope-mcp-server config only if needed.
  3. Keep token management outside repository files.
  4. Use CLI or SDK only when MCP is unavailable.

Minimal Valid Config

The expected local launch shape is:

{
  "mcpServers": {
    "modelscope-mcp": {
      "command": "uvx",
      "args": ["modelscope-mcp-server"]
    }
  }
}

Reference

  • references/client_config.md

Guardrails

  • Never invent undocumented MCP tool names.
  • Never store MODELSCOPE_API_TOKEN in checked-in files.
  • Keep the config minimal.

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.

Check your setup, free