opensite-ai/opensite-skills / aws-ai-ml
aws-ai-ml
VerifiedSelects, deploys, and customizes AI models on Amazon SageMaker. Training or Processing jobs, fine-tuning (SFT/DPO/RLVR/RLAIF), model selection, dataset preparation, evaluation, SageMaker or Bedrock deployment, inference optimization and endpoint diagnostics. Covers the full lifecycle from planning through production. Use when fine-tuning models on SageMaker, choosing which base model to customize, fine-tune, or deploy from SageMaker JumpStart or Hub, SageMakerPublicHub, or the SageMaker public model catalog, transforming or validating training data, evaluating model quality, deploying or optimizing endpoints, configuring IAM/S3 for training, or managing SageMaker Managed MLflow. Use for endpoint health, failures, latency, logs, metrics, errors. Covers Serverless Model Customization, Nova and OSS deployment paths, and PySDK v3. NOT for Ground Truth labeling, Feature Store, or general-purpose AWS infrastructure.
references/finetuning-technique/overview.md
View on GitHub
# Finetuning Technique
Guides the user through selecting a fine-tuning technique based on their use case and validates compatibility with the selected model.
## When to Use
- User has decided to finetune and needs to choose a technique
- User wants to change their finetuning technique
- Technique needs to be validated against a selected model
## Prerequisites
- A base model has been selected (via model-selection reference). The model name and hub must be known.
- A `use_case_spec.md` file exists. If not, load the use-case-specification reference to generate it first.
## Workflow
### Step 1: Determine Finetuning Technique
Consult `references/finetune_technique_selection_guide.md` to recommend the best-fit technique based on the use case and the user's needs (SFT, DPO, RLVR, RLAIF).
Present the recommendation and reasoning to the user. Ask if they'd like to go with the recommendation or prefer a different technique.
### Step 2: Validate Technique Availability
1. Once the user confirms a technique, retrieve the finetuning techniques available for the selected model by running: `python finetuning-technique/scripts/get_recipes.py <model-name> <hub-name>`
- This script filters to SFT, DPO, RLVR, and RLAIF, which have validated workflows in this skill. The model may support additional techniques (e.g. CPT, MTRL, PPO) that are not returned by this script.
2. If the chosen technique is available for the model, proceed to Step 3.
3. If the chosen technique is not available for the model, explain that the selected model does not support it on SageMaker and offer to go back to model-selection to pick a different model that supports the chosen technique. If the technique is one the model may support but is not returned by this script (e.g. CPT, MTRL, PPO), explain that this skill does not have a validated workflow for it and offer to help using general knowledge.
### Step 3: Confirm Selections
Present a summary to the user:
```
Here's what we've selected:
- Base model: [model name]
- Fine-tuning technique: [SFT/DPO/RLVR/RLAIF]
```
## References
- `references/finetune_technique_selection_guide.md` — Technique guidance (SFT/DPO/RLVR/RLAIF)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |