huawei-cloud-msmodelslim-model-analysis — Claude Code skill
huawei-cloud-msmodelslim-model-analysis — a skill for Claude Code and Codex that inspects a model architecture before writing an msModelSlim adapter. Checks implementation source and MoE quantization risks.
MIT 163 installs ★ 59 updated 2026-11-12
npx skills add huaweicloud/huaweicloud-skills --skill huawei-cloud-msmodelslim-model-analysis -a claude-codeWhat huawei-cloud-msmodelslim-model-analysis does
This skill runs on Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode using python3. Before you build an msModelSlim quantization adapter, the agent checks where the model code lives. First it reads config.json. From model_type and auto_map, it resolves whether the architecture comes from transformers or local modeling_*.py files.
Next, it compares the decoder layout against standard Qwen2-style LLMs to spot custom attention or MoE blocks. It checks whether expert weights in gate/up/down are stored as fused multi-expert tensors, which affects quantization scripts. Missing config and code files can be fetched without weights via modelscope download --model <org>/<model> --local_dir ./models/<name> --exclude '*.safetensors'. Without readable model code, analysis stops.
The analysis requires transformers version 4.40.0 or newer. It covers decoder-only LLMs and the text backbone of multimodal understanding models. Non-transformers architectures and multimodal generation models are not supported and get blocked right away.
What it helps with
- detect whether a model uses
transformersor localmodeling_*.pycode - assess quantization feasibility before writing an msModelSlim adapter
- flag fused MoE tensor risks in
gate/up/downweights - identify layer traversal order and layer-by-layer loading needs
Example prompts for the agent
- Analyze the model in
./models/qwenfor msModelSlim adapter feasibility - Check
config.jsonandmodeling_*.pyfor fused MoE weight risks - Inspect this LLM decoder structure before creating an msModelSlim adapter
How to install huawei-cloud-msmodelslim-model-analysis
1Skills CLI (Vercel)
npx skills add huaweicloud/huaweicloud-skills --skill huawei-cloud-msmodelslim-model-analysis -a claude-code2Manually: put the files in place
~/.claude/skills/huawei-cloud-msmodelslim-model-analysis/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/huawei-cloud-msmodelslim-model-analysis/
1Skills CLI (Vercel)
npx skills add huaweicloud/huaweicloud-skills --skill huawei-cloud-msmodelslim-model-analysis -a codex2Manually: put the files in place
.agents/skills/huawei-cloud-msmodelslim-model-analysis/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add huaweicloud/huaweicloud-skills --skill huawei-cloud-msmodelslim-model-analysis -a cursor2Manually: put the files in place
.cursor/skills/huawei-cloud-msmodelslim-model-analysis/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install huaweicloud/huaweicloud-skills skills/ai/modelarts/huawei-cloud-msmodelslim-model-analysis2Manually: put the files in place
.github/skills/huawei-cloud-msmodelslim-model-analysis/SKILL.md1Skills CLI (Vercel)
npx skills add huaweicloud/huaweicloud-skills --skill huawei-cloud-msmodelslim-model-analysis -a gemini-cli2Platform CLI
gemini skills install https://github.com/huaweicloud/huaweicloud-skills --path skills/ai/modelarts/huawei-cloud-msmodelslim-model-analysisManually: put the files in place
.devin/skills/huawei-cloud-msmodelslim-model-analysis/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add huaweicloud/huaweicloud-skills --skill huawei-cloud-msmodelslim-model-analysis -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about huawei-cloud-msmodelslim-model-analysis
How to install huawei-cloud-msmodelslim-model-analysis in Claude Code?
Run npx skills add huaweicloud/huaweicloud-skills --skill huawei-cloud-msmodelslim-model-analysis -a claude-code in your terminal. The skill will then be available in Claude Code.
What does huawei-cloud-msmodelslim-model-analysis do?
The skill evaluates a candidate model before you write an msModelSlim quantization adapter. It resolves the implementation source, maps structural differences in decoder layers, and flags risks such as fused MoE weights.
Which models are supported and what files are required?
It supports decoder-only LLMs and the text backbone of multimodal understanding models with transformers 4.40.0 or newer. Multimodal generation models and non-transformers architectures are blocked. You need config.json, plus local modeling_*.py files if the model is not built into transformers.
Source text
SKILL.md · MIT
---
name: huawei-cloud-msmodelslim-model-analysis
description: |
Analyze candidate models before adapter implementation. Determine model
implementation source (transformers or model-local), structural features,
layer-by-layer loading requirements, and MoE fused weight risks. Use this
skill when the user wants to assess model adaptation feasibility before
creating msModelSlim adapters, analyze model structure and type
classification, or evaluate MoE compatibility for quantization.
Triggers include: "model analysis", "msModelSlim", "adapter", "transformers",
"MoE", "layer-by-layer", "model assessment", "feasibility", "模型分析",
"适配可行性", "模型评估", "MoE分析"
compatibility:
- transformers >= 4.40.0
tags: [msModelSlim, analysis, model, MoE]
allowed-tools:
- python3
---
# Huawei Cloud msModelSlim Model Analysis
## Overview
This skill analyzes candidate models before adapter implementation for msModelSlim.
**Architecture**: Implementation Source Detection → Model Type Classification →
Structural Feature Analysis → Risk Assessment
**Related Skills**:
- `huawei-cloud-msmodelslim-model-adapt` - Adapter creation based on analysis
results
## Architecture Components
This skill involves the following cloud services and components:
- **msModelSlim**: Huawei Cloud's model quantization framework
- **Transformers Library**: Hugging Face Transformers for model loading
- **ModelScope**: Model download and management platform
- **config.json**: Model configuration file for analysis
**Architecture Diagram:**
```text
┌─────────────────────────────────────────────────────────────┐
│ msModelSlim Model Analysis Skill │
├─────────────────────────────────────────────────────────────┤
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Model │───▶│ Source │───▶│ Structure │ │
│ │ Input │ │ Detection │ │ Analysis │ │
│ │ (config) │ │ │ │ │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Type │ │ MoE │ │ Risk │ │
│ │ Classification│ │ Assessment │ │ Assessment │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
└─────────────────────────────────────────────────────────────┘
```
## Use Cases
**Typical Problem Scenarios:**
- Assessing model adaptation feasibility before creating msModelSlim adapters
- Analyzing model structure and type classification
- Evaluating MoE compatibility for quantization
- Determining if a model can be quantized with msModelSlim
- Identifying potential risks before adapter development
**Typical User Phrases:**
- "Analyze my model for msModelSlim compatibility"
- "Check if this model can be quantized"
- "Evaluate MoE fused weights risk"
- "Assess model adaptation feasibility"
- "Analyze model structure for quantization"
- "AnalysisModelmsModelSlim"
- "ModelQuantization"
- "CheckMoE"
## Scope
**Supported:**
- Decoder-only LLM
- VLM text backbone analysis (LLM/text path only)
**Not supported:**
- Non-transformers implementations
- Multimodal generation models (image/video/audio generation)
## Required Input
- Model path or model repository identifier
- `config.json`
- Optional: `modeling_*.py`, `model.safetensors.index.json` in the model
directory
- If files are missing locally:
- Download non-weight files using:
`modelscope download --model <org>/<model> --local_dir ./models/<name>
--exclude '*.safetensors'`
- Read `config.json` and `modeling_*.py` from the download directory as input
for analysis.
## Hard Requirement: Parse Implementation Source First
Must complete before any structural analysis. Agent should manually parse
following these steps:
1. **Read `config.json`**:
- Get `model_type`
- Get `auto_map` (if present)
2. **Try parsing from transformers**:
- Check if `transformers` library supports the `model_type`.
- Check if path exists:
`transformers/models/<model_type>/modeling_<model_type>.py`.
- If exists, record as `transformers` implementation.
3. **If not parsed, try model-local implementation**:
- Check if files pointed by `auto_map` exist in the model directory.
- Check if `modeling_*.py` files exist in the model directory.
- If exists, record as `model-local` implementation.
4. **If neither path available**:
- Stop analysis.
- Request user to provide readable model implementation code.
## Minimum Workflow
1. Parse implementation source (complete hard requirement above).
2. Determine model type, structural differences, and connections:
- Type: Pure LLM / Multimodal understanding / Multimodal generation
- Compare with common Qwen2-like LLMs, record special structural designs
(e.g., MoE, non-standard attention, SSM/hybrid blocks, additional heads
or parallel branches)
- Check special structure connections (location, dependencies,
serial/parallel/residual connections, impact on backbone traversal)
3. Identify structural features:
- Decoder layer class, attention/MLP module naming, forward signature
4. Determine features affecting adaptation:
- Layer traversal path and order
- Whether layer-by-layer loading is needed
- MoE fused expert weight risk
- Quantized model dequantization script risk
- MTP structure implementation availability and weight handling risk
5. Output structured analysis results (refer to template below).
6. Provide next steps:
- Proceed to adapter creation workflow
- Or block and explain what user needs to provide
### Model Type, Structural Differences, and Connection Determination
(relative to common Qwen2)
- **Pure LLM**: Text token input only, backbone is decoder-only language model.
- **Multimodal understanding**: Contains vision/audio encoders, but generation
path centers on text backbone; only text portion can be analyzed and adapted.
- **Multimodal generation**: Core goal is image/video/audio generation; current
workflow does not support, should block and explain reason directly.
- Structural differences only need to record "existence + impact direction",
no deep implementation details required.
- Connection relationships should record at minimum: which stage special
structure is located in backbone, which modules it connects to, connection
type (serial/parallel/residual), and impact on traversal/forward alignment.
### MoE Layout Determination
- **Non-fused MoE**: Experts expanded by module/list (commonly each expert has
its own `gate/up/down` linear layers).
- **Fused MoE**: Multiple expert weights packaged as tensor parameters, no
longer independent linear layers.
- If any of `gate/up/down` stored in `[..., num_experts, ...]` or
`[num_experts, ...]` form, treat as "fused".
- Three-dimensional expert weights (e.g., gate/up/down each fused into 3D
parameters) uniformly classified as `MoE fused`, with "may need unpack"
marked in report.
## Required Output: Analysis Report
Agent should directly generate analysis report (Markdown format), must include
following elements. Refer to template below:
```markdown
# Analysis Report
## Model Identification
- Model Path/Repository: {model_path}
- `model_type`: {model_type}
- `architectures`: {architectures}
## Implementation Source Analysis
- Result: `transformers` | `model-local` | `unsupported`
- Basis:
- Resolved file path: {path}
- Related configuration fields (`model_type`, `auto_map`): {details}
## Model Features and Specifications
- Hidden size: {hidden_size}
- Number of layers: {num_layers}
- Attention heads / KV heads: {num_heads} / {num_kv_heads}
- Analyze only VLM text portion: Yes/No
## Model Type, Structural Differences and Connections
- Model type: Pure LLM | Multimodal understanding | Multimodal generation
- Special structures vs common Qwen2: {special_structures}
- Special structure connections: {special_structure_connections}
- Impact on adaptation workflow: {structure_impact}
## Layer-by-Layer Loading Assessment
- Need layer-by-layer loading: Yes/No
- Reason: {reason}
- Constraints (memory/runtime environment): {constraints}
## MoE Assessment
- Contains MoE: Yes/No
- Layout type: No MoE | Non-fused MoE | Fused MoE
- Suspected fused keys/modules: {keys}
- Expert weight form: Independent linear layers | Packaged tensors
- Needs unpack: Yes/No
## Adaptation Impact Points
- Decoder traversal path: {traversal_path}
- Attention module naming: {attn_module}
- MLP module naming: {mlp_module}
- `visit/forward` strict alignment points: {alignment_points}
## Quantization and MTP Risk Assessment
- Model already quantized: Yes/No
- Quantization determination basis: {quant_evidence}
- Dequantization script provided: Yes/No
- Dequantization script status: {dequant_status}
- MTP structure exists: Yes/No
- MTP implementation code accessibility: Accessible/Not accessible
- MTP risk description: {mtp_risk}
## Risks and Next Steps
- Risk level: Low | Medium | High
- Blockers: {blockers}
- Recommended next steps:
- Proceed to adapter creation workflow
- Or request user to provide implementation code
```
### Risk Identification and User Communication Requirements (Mandatory)
- If identified as "model already quantized", must mark "missing dequantization
script" as blocker, explicitly requiring user to actively provide
dequantization script before continuing adaptation.
- If MTP structure identified but implementation code inaccessible, must
explicitly inform:
- Agent may not be able to fully implement MTP structure adaptation;
- To continue, user needs to copy MTP-related weights themselves (map
according to user-side implementation).
- When at least one of above two risk types hits, `risk level` must not be
lower than "Medium".
## Pass/Fail Criteria
- **Pass**: Implementation source is `transformers` or `model-local`, model
type is pure LLM or multimodal understanding, and report is complete; if
quantization/MTP risks hit, clear user action requirements given in report.
- **Fail**: Source not parsed, unsupported implementation type, determined as
multimodal generation model, or hits "quantized model without dequantization
script" blocking condition.
## Enhanced Features
### Automated Analysis Script
This skill ships an automated analysis script
(`scripts/analyze_model.py`) that runs the SKILL.md analysis flow against a
local model directory and produces a Markdown report:
```bash
python3 scripts/analyze_model.py --model-path <model_dir> --cli-region <region> [--output report.md] [--verbose]
```
**Features:**
- **Implementation Source Detection**: reads `config.json` and reports whether
the model is `transformers`-supported, `model-local`, or `unsupported`
- **Model Type Classification**: pure LLM / multimodal understanding /
multimodal generation
- **Structural Feature Extraction**: `hidden_size`, number of layers,
attention / KV heads, and MoE indicators from config
- **MoE Layout Assessment**: detects fused vs non-fused expert weight layouts
(via config fields and safetensors tensor names) and flags unpack needs
- **Layer-by-Layer Loading Assessment**: heuristic recommendation based on
model structure and environment memory
- **Quantization and MTP Risk Flags**: flags quantized models (missing
dequantization script) and MTP structures (missing implementation code)
The report generated follows the analysis report template in the "Required
Output" section above and must be interpreted together with the agent manual
analysis steps (`analysis-checklist.md`). The script output is a structured
starting point, not a replacement for code-level inspection of `modeling_*.py`.
## Reference Documents
- [Analysis Checklist](references/analysis-checklist.md) - Analysis verification
checklist
- [Acceptance Criteria](references/acceptance-criteria.md) - Functional
acceptance criteria
- [Verification Method](references/verification-method.md) - Verification approach
- [Troubleshooting](references/troubleshooting.md) - Common issues and solutions
- [IAM Policies](references/iam-policies.md) - Permission requirements
## Prerequisites
- transformers >= 4.40.0 installed
- Model code available for analysis
- Basic understanding of model structure
## Analysis Workflow
The analysis workflow follows these steps:
1. Parse model configuration (`config.json`)
2. Determine implementation source (transformers or model-local)
3. Analyze model architecture and structural features
4. Assess MoE layout and fused weight risks
5. Generate structured analysis report
6. Provide adaptation recommendations
## Core Commands
The skill does not call cloud APIs; model analysis is performed on local model
files. Two equivalent execution paths are supported:
### 1. Automated Analysis Script
```bash
python3 scripts/analyze_model.py --model-path <model_dir> --cli-region <region> [--output <report.md>] [--verbose]
```
Produces a Markdown report following the "Required Output" template.
### 2. Manual Analysis Steps
Follow the "Hard Requirement: Parse Implementation Source First" and "Minimum
Workflow" sections above; use `references/analysis-checklist.md` to verify each
step. Read `config.json`, `modeling_*.py`, and safetensors metadata from the
local model directory.
### Model Downloads (non-weight files, when missing locally)
```bash
modelscope download --model <org>/<model> --local_dir ./models/<name> --exclude '*.safetensors'
```
## Parameter Confirmation
For the automated analysis script:
| Parameter | Description | Required |
|--------------|-------------------------------------|----------|
| `--model-path` | Local model directory containing `config.json` | Yes |
| `--cli-region` | Region context for the downstream msModelSlim adapter workflow, e.g. `cn-north-4` (default `cn-north-4`) | No |
| `--output` | Analysis report output path | No |
| `--verbose` | Print extra progress information | No |
For the manual workflow, the required input is the model path or repository
identifier plus its `config.json` (and optionally `modeling_*.py` /
`model.safetensors.index.json`).
© huaweicloud · MIT · huaweicloud/huaweicloud-skills