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/dataset-transformation/references/code_output_guide.md
View on GitHub# Code Output Guide
## Mode Selection
Ask the user once before generating code: **"Would you like me to generate a Jupyter notebook or a Python script?"**
If the output format has already been decided in the conversation context, keep consistent — do not re-ask.
## Shared Rules (Both Modes)
- Use EXACTLY the imports shown in each code template — do not add extras
- Replace `[PLACEHOLDER]` values with user-specific configuration
- Include `set_attribution(Attribution.SAGEMAKER_AGENT_PLUGIN)` in the setup cell/section
## Reading Code Templates
Templates use `# Cell N: Label` markers to delimit sections. `# NOTEBOOK_ONLY` skips a line in script mode; `# NOTEBOOK_ONLY_SECTION` on a `# Cell N:` line skips the entire section.
## Notebook Mode
Write a `.ipynb` file in `<project-dir>/notebooks/`.
**Naming and appending:**
- Notebook path: `<project-dir>/notebooks/<project-name>.ipynb`
- If the notebook already exists → ask: _"Would you like me to append cells to the existing notebook, or create a new one?"_
- If it doesn't exist → create it
- When appending, use the template's `# Cell 0 [markdown]:` cell as the section divider before the new cells
**Formatting:**
- Use your file write tool to create the complete notebook JSON, OR use notebook MCP tools (`create_notebook`, `add_cell`) if available
- Do NOT use bash commands, shell scripts, or `echo`/`cat` piping
- 2-space JSON indentation
- Each source line is a separate string ending with `\n` (except the last)
- Escape quotes: `\"`
- No trailing commas
**Structure:**
- Wrap cells in `{"cells": [...], "metadata": {...}, "nbformat": 4, "nbformat_minor": 4}`
- Code cells: `cell_type`, `execution_count: null`, `metadata: {}`, `outputs: []`, `source: [...]`
- Markdown cells: `cell_type: "markdown"`, no `execution_count` or `outputs`
- `# Cell 0 [markdown]:` becomes a markdown cell; all others become code cells
**Execution:**
- If notebook execution tools are available (e.g., `run_cell` MCP), offer to run cells for the user. If not available, tell the user to run cells themselves.
- Do NOT use bash commands or inline scripts to execute notebook cells.
## Script Mode
Write a numbered `.py` file in `<project-dir>/scripts/`.
**Naming:**
- Format: `NN_<descriptive_name>.py` (e.g., `01_sft_finetuning.py`) — use the next available number in `<project-dir>/scripts/`
**Formatting:**
- Plain Python file, standard text
- Use `# %%` cell markers to preserve logical sections (IDE-compatible)
- Include a docstring at the top describing what the script does
- `# Cell 0 [markdown]:` → a comment block or docstring
**Dependencies:**
- Install any required pip packages directly (e.g., `pip install 'sagemaker>=3.7.1,<4.0'`) before writing or running the script. Do not embed install commands in the script itself.
**Execution:**
- Run the script using standard Python execution (`python3 <script>.py`).
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 |