Generated banner for Finetuning
Generated logo for Finetuning

Finetuning

AWS LabsOfficialPublished by AWS Labs

  • Skill
  • Workflow
  • Data and AI
  • Apache-2.0
  • Low risk
  • Has scripts

From the author

Generates code that fine-tunes a base model using SageMaker serverless training jobs. Use when the user says "start training", "fine-tune my model", "I'm ready to train", or when the plan reaches the finetuning step. Supports SFT, DPO, RLVR, and RLAIF trainers, including RLVR Lambda reward function and RLAIF custom prompt creation.
— the description by AWS Labs

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured workflow to generate code for fine-tuning machine learning models on AWS SageMaker. It supports multiple training techniques including SFT, DPO, RLVR, and RLAIF. The skill ensures that all prerequisites—such as use case specifications, model selection, and environment configuration—are met before generating the necessary Python scripts or Jupyter notebooks. It also handles EULA acceptance for specific models and provides options for executing training jobs and monitoring their status.

What it does

  • Generates standardized training code for SFT, DPO, RLVR, and RLAIF techniques.
  • Configures SageMaker serverless training jobs with appropriate model and dataset parameters.
  • Manages EULA review and acceptance for restricted base models.
  • Supports creation of custom reward functions for RLVR workflows.
  • Provides options to run training jobs as scripts or within notebooks.
  • Monitors training job status and reports performance metrics upon completion.

When to use it

  • When the user requests to start training or fine-tune a model.
  • When the project plan reaches the fine-tuning phase.
  • When you need to perform a subsequent round of fine-tuning on an already customized model.

Advantages

  • Ensures consistent code structure and dependency management across projects.
  • Automates the configuration of complex SageMaker training parameters.
  • Provides a safe, step-by-step process that validates prerequisites before execution.
  • Offers flexible execution modes (notebook vs. script) to suit user preferences.

Usage examples

“I'm ready to train my model using SFT.”
The agent verifies prerequisites, selects the SFT template, configures the SageMaker environment, and generates the training notebook or script.
“Can you help me fine-tune this model with RLVR?”
The agent guides the user through creating a reward function or providing an existing ARN, then generates the RLVR training code.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/awslabs/finetuning/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip finetuning.zip -d .agents/skills

Documentation by AWS Labs

Prerequisites

Before starting this workflow, verify:

  1. A use_case_spec.md file exists

    • If missing: Activate the use-case-specification skill first, then resume

    • DON'T EVER offer to create a use case spec without activating the use-case-specification skill.

  2. A fine-tuning technique (SFT, DPO, RLVR, RLAIF, or CPT/RFT (for Nova)) and base model have already been selected

    • If missing: Activate the model-selection and/or finetuning-technique skills to collect what's missing, then resume

    • Don't make recommendations on the spot. You MUST activate the appropriate skill.

  3. A base model name available on SageMakerHub has been identified

    • If missing: Activate the model-selection skill to get it

    • Important: Only use the model name that model-selection retrieves, as it may differ from other commonly used names for the same model

  4. The SDK environment has been verified (SDK version, region, execution role)

    • If not done: Activate the sdk-getting-started skill first, then resume

  5. A training dataset uploaded to a bucket in the environment's default region.

    • If not met: Help the user upload the dataset to the correct S3


Critical Rules

Code Generation Rules

  • ✅ Use EXACTLY the imports shown in each code template

  • ❌ Do NOT add additional imports even if they seem helpful

  • ❌ Do NOT create variables before they're needed in that section

  • 📋 Copy the code structure precisely - no improvisation

  • 🎯 Follow the minimal code principle strictly

  • ✅ When writing code, make sure the indentation and f strings are correct

User Communication Rules

  • ❌ NEVER offer to move on to a downstream skill while training is in progress (logically impossible)

  • ❌ NEVER set ACCEPT_EULA to True without explicit user confirmation in the conversation

  • ✅ Always mention both the number AND title of sections you reference

  • ✅ If user asks how to run (notebook): If run_cell is available, offer to run it. Otherwise, tell them to run cells one by one (mention ipykernel requirement).

  • ✅ If user asks how to run (script): Tell them to run with python3 <script>.py


Workflow

1. Code Generation Setup

1.1 Directory Setup
  1. Identify project directory from conversation context

    • If unclear (multiple relevant directories exist) → Ask user which folder to use

    • If no project directory exists → activate the directory-management skill to set one up

⏸ Wait for user.

1.2 Select Code Template

Read references/code_output_guide.md for output format rules, then read the code template matching the finetuning strategy:

  • SFT → code_templates/sft.py

  • DPO → code_templates/dpo.py

  • RLVR → code_templates/rlvr.py

  • RLAIF with built-in rewards → code_templates/rlaif_builtin.py

  • RLAIF with custom prompt → code_templates/rlaif_custom_prompt.py

The template is a Python file where each # Cell N: Label comment marks the start of a new section. Split on these markers — everything between one marker and the next becomes one unit of output.

1.3 Generate Code
  1. Write the code from the template following the rules in code_output_guide.md

  2. Use same order, dependencies, and imports as the template

  3. DO NOT improvise or add extra code

  4. If the model is NOT a Meta/Llama model (model ID does NOT start with meta-):

    • Omit the ACCEPT_EULA = False line from the config cell

    • Omit the accept_eula=ACCEPT_EULA, line from the trainer call

  5. If the model is from the Nova family, omit any code containing max_epochs or lr_warmup_steps_ratio from the Configure Trainer section and the Hyperparameter Overrides section

1.4 Auto-Generate Configuration Values

In the 'Setup & Credentials' cell, populate:

  1. BASE_MODEL

    • Use the exact SageMakerHub model name from context

  2. MODEL_PACKAGE_GROUP_NAME

    • Generate from use case (read use_case_spec.md if needed)

    • Format rules:

      • Lowercase, alphanumeric with hyphens only

      • 1-63 characters

      • Pattern: [a-zA-Z0-9](-*[a-zA-Z0-9]){0,62}

      • Example: "Customer Support Chatbot" → customer-support-chatbot-v1

  3. Save notebook

2. RLVR Reward Function (for RLVR only, skip this section if technique is SFT or DPO)

2.1 Check Reward Function Status
  • Ask if user has a reward function already, or would like help creating one.

    • If user says they have one → Ask for the SageMaker Hub Evaluator ARN. Only proceed to Section 2.3 once the user provides a valid Evaluator ARN. If they don't have it registered as a SageMaker Hub Evaluator, continue to 2.2.

    • If user says they do not have one → Continue to 2.2

2.2 Generate Reward Function From Template
  1. Follow workflow in references/rlvr_reward_function.md section "Helping Users Create Custom Reward Functions"

2.3 Set CUSTOM_REWARD_FUNCTION value
  1. Set the value for CUSTOM_REWARD_FUNCTION in the Notebook with the ARN of the reward function (either given directly by the user, or from the function generation code as evaluator.arn).

3. RLAIF (for RLAIF only, skip this section if technique is not RLAIF)

Read references/rlaif_guide.md and follow its instructions.

4. EULA review and acceptance

  1. Look up the official license link for the selected base model from references/eula_links.md

  2. Display the license to the user following the phrasing in references/eula_links.md. For OSS models: "This model is licensed under {License}. Please review the license terms here: {URL}." For Nova models: "This model is subject to the AWS Service Terms: {URL}."

  3. Check if the selected base model is a Meta/Llama model (model ID starts with meta-)

    • If Meta/Llama: Tell the user they must read and agree to the EULA before using this model. Ask: "Do you accept the license terms? (yes/no)". If the user confirms, set ACCEPT_EULA = True and uncomment accept_eula=ACCEPT_EULA in the generated notebook. If the user declines, leave ACCEPT_EULA = False and warn that training will fail without acceptance.

    • If non-Meta: Inform the user of the license for their awareness. No code-level action needed — the ACCEPT_EULA variable and accept_eula parameter should already be omitted from the notebook (see Step 1.3).

5. Post-Generation

After generating the code, offer to run it. Training can take hours depending on your dataset and model.

Notebook mode: If run_cell is available, offer to run the cells. Otherwise tell the user to run cells themselves.

Script mode: Present the user with options:

"Would you like me to:

  1. Leave it to you — run with python scripts/[script_name]

  2. Run it and wait until it's done

  3. Start it but don't wait — we can check status later"

  • Option 1: Done. Wait for user to come back.

  • Option 2: Execute the script as-is. trainer.train(wait=True) blocks until complete. Report final status.

  • Option 3: Change wait=True to wait=False in the script, execute, report the training job name.

Checking status:

  • describe-training-job --training-job-name NAME → TrainingJobStatus, FailureReason, SecondaryStatusTransitions

  • For model package ARN after completion: list-model-packages --model-package-group-name GROUP_NAME --sort-by CreationTime --sort-order Descending --max-results 1

Showing results after completion:

  • Use scripts/mlflow_reference.py as the pattern to query MLflow metrics

  • Present loss by epoch as a text table (total_loss, val_eval_total_loss for SFT; rewards/margins for DPO; critic/rewards/mean for RLVR)

CRITICAL:

  • DON'T suggest moving to next steps before training completes

  • DON'T elaborate on the next steps unless the user specifically asks you about them.

6. Continuous Customization

If the user wants to finetune a model they had already customized, follow the instructions in references/continuous_customization.md


References

  • rlvr_reward_function.md - Lambda reward function creation guide (RLVR only)

  • templates/rlvr_reward_function_source_template.py - Lambda reward function source template for open-weights models (RLVR only)

  • templates/nova_rlvr_reward_function_source_template.py - Lambda reward function source template for Nova 2.0 Lite (RLVR only)

  • code_templates/sft.py - Complete notebook template for Supervised Fine-Tuning (OSS path)

  • code_templates/dpo.py - Complete notebook template for Direct Preference Optimization (OSS path)

  • code_templates/rlvr.py - Complete notebook template for Reinforcement Learning from Verifiable Rewards (OSS path)

  • references/continuous_customization.md - Instructions on fine-tuning an already fine-tuned model.

  • rlaif_guide.md - instructions on RLAIF finetuning options

  • rlaif_builtin.py - Code template for RLAIF with built-in judge prompt

  • rlaif_custom_prompt.py - Code template for RLAIF with custom judge prompt

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python

Security

What our scanner noticed· Low risk

  • Instructions that use the network
  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
AWS Labs
Publisher
AWS Labs (Official)
Source
awslabs/agent-plugins · plugins/sagemaker-ai/skills/finetuning · commit fbefb37
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • NOTICE (added by AutoGineer from NOTICE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by AWS Labs.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download finetuning.zip