agentleFS
hyf020908hyf020908/modelscope-skills/skills/modelscope-local-vision-trainer/SKILL.md

modelscope-local-vision-trainer

Skill4 starsChanged 8 months agoApache-2.0View on GitHub

Turn plain-language local vision-training requests into editable configs and launch scripts, then run them after the user fills a local config file and replies continue.

  • Reads credentials

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 7 are distinctive, and 6 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.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants local vision training on a Linux GPU workstation or server and describes the job in natural language.

    line 8
  2. Very specific:

    Run scripts/prepare_local_vision_training_workspace.py with the user's exact request text.

    line 24
  3. Very specific:

    Only after the user replies continue, run bash scripts/run_local_vision_training.sh.

    line 37
  4. Distinctive:

    Read the user request and infer the task, model, dataset paths, and training parameters.

    line 46
  5. Very specific:

    Ask the user to review or edit configs/local.vision.required.env.

    line 49
  6. Very specific:

    Only after continue, run bash scripts/run_local_vision_training.sh.

    line 51
  7. Very specific:

    When task is ambiguous, default to classification

    line 58
  8. Distinctive:

    Keep the generated launch script readable and editable.

    line 62
  9. Distinctive:

    Prefer one process by default unless the user clearly asks for distributed local training.

    line 65
  10. Very specific:

    Never skip the continue gate.

    line 73
  11. Distinctive:

    Never auto-run on macOS or an unknown host.

    line 74
  12. Distinctive:

    Never assume the local training entrypoint already exists without checking.

    line 75
  13. Distinctive:

    Never claim built-in local execution for a task unless the configured entrypoint is present on the target machine.

    line 76

≈ “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 Local Vision Trainer

Use this skill when the user wants local vision training on a Linux GPU workstation or server and describes the job in natural language.

Request Style

  • Accept requests such as:
    • Train an image classifier locally with ./data/train and ./data/val, epoch=5.
    • 我想在本地做目标检测,训练标注是 ./data/annotations/train.json,验证标注是 ./data/annotations/val.json。
  • Infer missing fields where that is safe.
  • Default task: classification
  • Default model:
    • Classification: google/vit-base-patch16-224
    • Detection: facebook/detr-resnet-50
    • Segmentation: facebook/sam-vit-base

What You Must Create

Run scripts/prepare_local_vision_training_workspace.py with the user's exact request text. It must create:

  1. configs/local.vision.training.json
  2. configs/local.vision.required.env
  3. configs/local.vision.train.env
  4. scripts/run_local_vision_training.sh

Execution Rule

  • This skill always pauses once before execution.
  • First create configs/local.vision.required.env with non-empty default values.
  • Tell the user to review or edit that file.
  • Tell the user to reply with exactly continue.
  • Only after the user replies continue, run bash scripts/run_local_vision_training.sh.
  • On macOS or any unknown host, stop after writing the files and report that execution should happen on the intended Linux GPU host.

Primary Script

  • scripts/prepare_local_vision_training_workspace.py

Workflow

  1. Read the user request and infer the task, model, dataset paths, and training parameters.
  2. Run scripts/prepare_local_vision_training_workspace.py --request "<user text>".
  3. Inspect the generated plan, configs/local.vision.required.env, and launch script.
  4. Ask the user to review or edit configs/local.vision.required.env.
  5. Tell the user to reply with exactly continue.
  6. Only after continue, run bash scripts/run_local_vision_training.sh.

Task Rules

  • Classification keywords: classification, 分类
  • Detection keywords: detection, 目标检测
  • Segmentation keywords: segmentation, segment, 分割, sam
  • When task is ambiguous, default to classification

Command Rules

  • Keep the generated launch script readable and editable.
  • configs/local.vision.required.env should start with sensible defaults instead of blank placeholders.
  • The launch script must verify that the configured local training entrypoint exists before it tries to run.
  • Prefer one process by default unless the user clearly asks for distributed local training.

References

  • references/runtime_requirements.md

Guardrails

  • Never skip the continue gate.
  • Never auto-run on macOS or an unknown host.
  • Never assume the local training entrypoint already exists without checking.
  • Never claim built-in local execution for a task unless the configured entrypoint is present on the target machine.

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.