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/manage-mlflow/references/app-update-workflow.md
View on GitHub# App Update Workflow
Guides safe updates to an existing MLflow app's configuration.
> **IMPORTANT:** Use only `sagemaker:UpdateMlflowApp`. Do NOT use `UpdateMlflowTrackingServer` (legacy) — that API is deprecated.
## Step 1: Identify Target App
- If user provided an ARN: use it directly
- If not: run the discovery workflow (`references/app-discovery-workflow.md`), ask user to pick an app
## Step 2: Show Current Configuration
Run `aws sagemaker describe-mlflow-app` with the app ARN. Present the updatable fields with their current values.
Discover which fields are updatable on the `UpdateMlflowApp` API at runtime — do not hardcode a static field list.
Ask: "Which field would you like to update?"
## Step 3: Confirm the Change
- Ask user for the new value
- Discover valid values for the field if applicable
- Present confirmation: "Change `{field}` from `{old_value}` to `{new_value}`?"
- Do not proceed without explicit confirmation
## Step 4: Apply and Verify
- Run `aws sagemaker update-mlflow-app` with the ARN and updated field
- Poll: run `aws sagemaker describe-mlflow-app` in a loop (every minute) until status returns to `ACTIVE` (update triggers `UPDATING` status)
- Timeout: 10 minutes. If exceeded, warn user and suggest checking Console.
- Once `ACTIVE`: verify the field value matches the requested change
- Confirm to user: "{field} updated successfully."
## Error Handling
| Error | Resolution |
|---|---|
| `ConflictException` | Another update is in progress. Wait 30 seconds, then retry. |
| `AccessDeniedException` | "You need `sagemaker:UpdateMlflowApp` permission." |
| `ResourceNotFound` | "This app no longer exists." |
| `ValidationException` | Look up valid values and present them to the user. |
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 |