add-afm-model

Analyze HuggingFace MLX model config.json files to onboard them into AFM registries and Swift backend workflows.

324|17|Updated Aug 8, 2025
One-click install
npx skills add https://github.com/scouzi1966/maclocal-api --skill add-afm-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-afm-model
Source: https://github.com/scouzi1966/maclocal-api/tree/main/.claude/skills/add-afm-model
Command: npx skills add https://github.com/scouzi1966/maclocal-api --skill add-afm-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and onboard HuggingFace MLX models into AFM, enabling automatic compatibility checks, architecture mapping, and integration workflows.

Core Features & Use Cases

  • Identify MLX status from config.json
  • Determine registry compatibility and necessary patches or ports
  • Support MoE and VLM variants with appropriate backend registration

Quick Start

Invoke the skill with /add-afm-model <model-id> or a HuggingFace URL to begin onboarding a new MLX model.

Frequently Asked Questions about add-afm-model

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

FAQPage Schema
How do I add HuggingFace MLX models to AFM?

To add HuggingFace MLX models to AFM, you invoke the onboarding workflow with a model ID or URL. The system analyzes the model's config.json to determine MLX status, architecture, and registry compatibility before applying necessary Swift backend patches.

How does MLX model architecture compatibility checking work?

MLX model architecture compatibility checking works by analyzing the model's config.json to determine its MLX status and architecture. A structured decision workflow then classifies the model as already supported, requiring a port from Python, or needing a new architecture entirely.

Can I use this to onboard vision-language models (VLMs) into AFM?

Yes, you can onboard vision-language models (VLMs) into AFM. The onboarding workflow includes specific considerations for VLM variants and provides guidance for registering them in the appropriate VLM registries alongside the standard LLMTypeRegistry.

Does the AFM onboarding workflow support Mixture of Experts (MoE) models?

Yes, the AFM onboarding workflow supports Mixture of Experts (MoE) models. The structured decision process includes specific MoE considerations to classify the model and apply the correct backend patches for successful integration.

What is the process to patch the Swift backend for a new MLX model?

Patching the Swift backend involves classifying the model's architecture requirements and then applying structured code patches. After patching, you must register the model in LLMTypeRegistry and validate the integration using a dedicated test workflow.

Why do I need to port Python models to Swift for AFM integration?

You need to port Python models to Swift for AFM integration when the model architecture is not already supported natively. The workflow identifies this requirement during config analysis, guiding you through the Swift backend patching and LLMTypeRegistry registration.