mcpbeat

Model Selection

awslabs/model-selection

Selects a base model for the user's use case by querying SageMaker Hub. Use when the user asks which model to use, wants to select or change their base model, mentions a model name or family (e.g., "Llama", "Mistral", "Nova"), or wants to evaluate a base model — always activate even for known model names because the exact Hub model ID must be resolved. Queries available models, presents benchmarks and licenses, and confirms selection.

11k tokens
context cost
the whole folder, loaded on every use
12
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
850
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/awslabs/agent-plugins --skill model-selection

The instruction itself

9 sections, as written by the author

Model Selection

Guides the user through selecting a base model based on their use case.

When to Use

  • User asks which model to use
  • User wants to select or change their base model
  • User mentions a model name or family (e.g., "Llama", "Mistral", "Nova") — the exact Hub model ID still needs to be resolved
  • User wants to evaluate a base model before deciding whether to finetune

Prerequisites

  • A use_case_spec.md file exists. If not, activate the use-case-specification skill to generate it first.

Workflow

Step 1: Check Region

Run:

python -c "import boto3; print(boto3.session.Session().region_name)"
  • None → STOP. Tell user: "Set your region via export AWS_DEFAULT_REGION=us-west-2 or aws configure."
  • Set → store REGION in context, continue.

Step 2: Discover Hub

  • List all available SageMaker Hubs in the user's region by calling the SageMaker ListHubs API using the aws___call_aws tool.
  • From the results, filter out any hub whose HubDescription contains "AI Registry" — these do not contain JumpStart models.
  • The remaining hubs are eligible (e.g., SageMakerPublicHub and any private hubs).
  • If exactly one eligible hub exists, use it automatically — do not ask the user.
  • If multiple eligible hubs exist, present them to the user and ask which one to use. Example:
   I found the following model hubs:
   - SageMakerPublicHub — SageMaker Public Hub
   - Private-Hub-XYZ — Private Hub models
   Which hub would you like to use?
  • Store the selected hub name for use in subsequent steps.

Step 3: Select Base Model

First, retrieve all available SageMaker Hub model names by running: python model-selection/scripts/get_model_names.py <hub-name>.

Present all available models to the user with their licenses before making any recommendations. Cross-reference the model list with references/model-licenses.md and display each as <model name> - <license>. For example: "Qwen3-4B - Apache 2.0"

If you already know the model the user wants to use (from conversation context or planning files), confirm that it's in the list, display its license, and move on. Otherwise, help the user pick a model following the instructions in references/model-selection.md.

Important: Make sure to remember this list of available models when helping with model selection. Don't recommend a model that's not available to the user.

Step 4: Confirm Selection

Present a summary to the user:

Here's what we've selected:
- Base model: [model name]

Ask if they'd like to proceed with this model.

References

  • references/model-selection.md — Model selection instructions and benchmark descriptions
  • references/model-licenses.md — Model license information for display during model selection

How to use it

Copy the folder

Take awslabs/model-selection from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.