agentleFS
MCamnerMCamner/mq-image-analyze/skills/model-setup-maintainer/SKILL.md

model-setup-maintainer

Skill1 starsChanged 22 days agoMITView on GitHub

Use when changing mq-image-analyze model setup, YOLO weights, Ollama/OpenAI vision backends, doctor readiness checks, or model documentation.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for local and cloud vision model readiness.

    line 8
  2. Very specific:

    Use gpt-4o when specifically requested.

    line 48
  3. Distinctive:

    Keep doctor output clear about missing dependencies and model files.

    line 52
  4. Distinctive:

    Keep model names consistent across README, CLI docs, and provider code.

    line 53
  5. Distinctive:

    Do not require cloud credentials for local modes.

    line 54
  6. Distinctive:

    Do not download or commit model weights automatically without explicit user request.

    line 55

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

Model Setup Maintainer

Use this skill for local and cloud vision model readiness.

Evals

Should trigger

  • "update the YOLO weights"
  • "switch the Ollama vision backend"
  • "doctor model readiness check fails"
  • "document the OpenAI vision setup"

Should not trigger

  • "change MCP tools" → use mcp-tools-maintainer
  • "change CLI flags" → use cli-maintainer
  • "docs only" → use docs-maintainer

Core Files

  • docs/model-setup.md
  • mq_image_analyze/cli/doctor.py
  • mq_image_analyze/vision/detection/detector.py
  • mq_image_analyze/vision/semantic/provider.py
  • mq_image_analyze/vision/semantic/ollama_vision.py
  • mq_image_analyze/vision/semantic/openai_vision.py
  • tests/test_doctor.py
  • tests/test_semantic_provider.py

Model Contracts

Detection:

  • YOLOv8n weights are expected locally.
  • Model weights must not be committed.

Semantic vision modes:

  • local-fast defaults to bakllava via Ollama.
  • local-deep defaults to llama3.2-vision via Ollama.
  • cloud-verify defaults to gpt-4.1 via OpenAI.
  • Use gpt-4o when specifically requested; do not invent gpt-4.0.

Change Rules

  • Keep doctor output clear about missing dependencies and model files.
  • Keep model names consistent across README, CLI docs, and provider code.
  • Do not require cloud credentials for local modes.
  • Do not download or commit model weights automatically without explicit user request.

Verification

python -m pytest tests/test_doctor.py tests/test_semantic_provider.py -q
mq-image doctor --json

For docs changes:

rg "local-fast|local-deep|cloud-verify|gpt-4.1|gpt-4o|bakllava" README.md docs mq_image_analyze

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.