/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
$ npx -y skills add awslabs/agent-plugins --skill model-selection --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/model-selection
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
model-selection.SKILL.mdname: model-selection
description: 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.
metadata:
version: "1.0.0"
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
1. List all available SageMaker Hubs in the user's region by calling the SageMaker `ListHubs` API using the `aws___call_aws` tool. 2. From the results, filter out any hub whose `HubDescription` contains "AI Registry" — these do not contain JumpStart models. 3. The remaining hubs are eligible (e.g., `SageMakerPublicHub` and any private hubs). 4. If exactly one eligible hub exists, use it automatically — do not ask the user. 5. 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?
6. 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>](<url>)`. For example: "Qwen3-4B - [Apache 2.0](https://huggingface.co/Qwen/Qwen3-4B/blob/main/LICENSE)"
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
Read more
name: model-selection description: 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. metadata: version: "1.0.0"
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
1. List all available SageMaker Hubs in the user's region by calling the SageMaker `ListHubs` API using the `aws___call_aws` tool. 2. From the results, filter out any hub whose `HubDescription` contains "AI Registry" — these do not contain JumpStart models. 3. The remaining hubs are eligible (e.g., `SageMakerPublicHub` and any private hubs). 4. If exactly one eligible hub exists, use it automatically — do not ask the user. 5. 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?
6. 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>](<url>)`. For example: "Qwen3-4B - [Apache 2.0](https://huggingface.co/Qwen/Qwen3-4B/blob/main/LICENSE)"
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
Read this in other languages: 日本語 Generative AI can make mistakes. You should consider reviewing all output and costs generated by your chosen AI model and agentic coding assistant. See AWS Responsible AI Policy.
Other skills on agent-plugins.
- /amazon-location-service
Integrates Amazon Location Service APIs for AWS applications. Use this skill when users want to add maps (interactive MapLibre or static images); geocode addresses to coordinates or reverse geocode coordinates to addresses; calculate routes, travel times, or service areas; find
Open skill - /amplify-workflow
Build and deploy full-stack web and mobile apps with AWS Amplify Gen2
Open skill - /api-gateway
Build, manage, and operate APIs with Amazon API Gateway (REST, HTTP, and WebSocket). Triggers on phrases like: API Gateway, REST API, HTTP API, WebSocket API, custom domain, Lambda authorizer, usage plan, throttling, CORS, VPC link, private API. Also covers troubleshooting API
Open skill - /aws-lambda-durable-functions
Build resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions. Covers the critical replay model, step operations, wait/callback patterns, error handling with
Open skill - /aws-lambda-managed-instances
Evaluate, configure, and migrate workloads to AWS Lambda Managed Instances (LMI). Triggers on: Lambda Managed Instances, LMI, capacity provider, multi-concurrency Lambda, dedicated instance Lambda, EC2-backed Lambda, cold start elimination, Graviton Lambda, instance type for
Open skill - /aws-lambda-microvms
Build, run, debug, and operate applications on AWS Lambda MicroVMs — Firecracker-isolated, snapshot-resumable serverless compute environments that run inside a container with up to 8-hour lifetimes. Triggers on: Lambda MicroVMs, Firecracker isolation, snapshot-resumable compute,
Open skill

