upstream-mlx-vlm-issues

Drafts reproducible maintainer-ready GitHub issues for upstream mlx-vlm failures.

1|1|Updated Apr 21, 2025
One-click install
npx skills add https://github.com/jrp2014/check_models --skill upstream-mlx-vlm-issues-jrp2014
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upstream-mlx-vlm-issues
Source: https://github.com/jrp2014/check_models/tree/main/.agents/skills/upstream-mlx-vlm-issues
Command: npx skills add https://github.com/jrp2014/check_models --skill upstream-mlx-vlm-issues-jrp2014

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a failed mlx-vlm model run into a clear, reproducible upstream bug report is tedious: you must gather environment facts, minimize the repro, and format everything so a maintainer can act on it. This Skill converts check_models failures and native repros into paste-ready GitHub issue drafts without manual assembly. ## Core Features & Use Cases - Artifact-driven drafting: Builds issues from existing src/output/issues/issue_*.md, diagnostics.md, run_summary.md, results.jsonl, and environment.log instead of re-deriving facts. - Repro minimization guidance: Reduces failures to a single native python -m mlx_vlm.generate command or a server start plus one curl request, with conda/pip conventions (never uv). - Classification and quality bar: Distinguishes model/config, runtime, harness preflight, environment, and connectivity failures, and enforces a maintainer-ready template with environment, model revision, expected vs actual behavior, and trimmed tracebacks. - Use Case: After a benchmark sweep crashes one model, ask for an upstream issue draft and receive a complete Markdown report with exact versions, resolved model revision, minimal repro command, and root exception—ready to paste into GitHub only if you explicitly ask. ## Quick Start Draft an upstream mlx-vlm issue from the latest crash draft in src/output/issues without filing it on GitHub.

Frequently Asked Questions about upstream-mlx-vlm-issues

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

FAQPage Schema
How do I write a reproducible bug report for mlx-vlm?▼

Collect the mlx-vlm version or commit, Python and macOS versions, chip, exact model ID with resolved revision, and the minimal native command that fails. Lead with the root exception and first frames inside mlx-vlm, and state expected versus actual behavior.

How do I minimize an mlx-vlm reproduction before filing an issue?▼

Reduce the failure to the smallest native command or curl request that still fails, using one model per process and one image before multi-input. Prefer public models and small synthetic media, and remove private paths and tokens.

Does this Skill file GitHub issues automatically?▼

No. It only drafts or improves issue Markdown locally under src/output/issues or in chat. Running gh issue create or opening an upstream PR happens only when the user explicitly requests filing.

Can I report mlx-vlm server endpoint failures like /v1/chat/completions?▼

Yes. Start the server with python -m mlx_vlm.server and capture the startup command, server logs, curl request JSON, status code, and response body. Keep streaming and non-streaming repros separate, since check_models does not cover HTTP server behavior.

When should a failed model run not become an upstream issue?▼

Completed-but-unusable outputs and neutral observations, such as declared EOS or thinking wrappers, stay in diagnostics unless independently reproduced as a defect. Connectivity and download failures are usually indeterminate and not model crashes.