agentleFS
Red-Hat-AI-Innovation-TeamRed-Hat-AI-Innovation-Team/training_hub/.claude/skills/setup-guide/SKILL.md

setup-guide

Skill104 starsChanged 5 months agoApache-2.0View on GitHub

Use when the user wants to set up LLM training for the first time, or when training_hub is not yet installed/configured in the current environment.

  • Installs packages

6 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 5 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ask permission: "training_hub isn't installed.

    line 20
  2. Very specific:

    If yes and installer=uv: run uv pip install training-hub

    line 21
  3. Very specific:

    If installer=none: tell the user they need Python and pip/uv installed first

    line 23
  4. Very specific:

    If gpu=unavailable, warn: "No GPU detected.

    line 33
  5. Distinctive:

    If the user has a clear task ("fine-tune Llama on my data"), offer a fast path with sensible defaults:

    line 39
  6. Distinctive:

    If the user accepts, ask only for model path and data path, then skip to Step 7.

    line 50
  7. Distinctive:

    Ask these questions one at a time:

    line 56
  8. Very specific:

    Ask: "Do you want to configure experiment tracking?" (W&B, MLflow, or TensorBoard).

    line 70
  9. Very specific:

    Write the config to .training-hub/config.json:

    line 74
  10. Very specific:

    Add .training-hub/ to .gitignore if not already present.

    line 89
  11. Distinctive:

    Ask: "Want me to estimate GPU memory requirements before training?"

    line 93
  12. Distinctive:

    If this skill is invoked again and a config already exists, ask: "You already have a configuration.

    line 102

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

training_hub Setup Guide

You are helping the user set up LLM training. For algorithm selection guidance, hyperparameter tuning, and troubleshooting, consult the training-hub-guide skill.

Step 1: Detect Environment

"${CLAUDE_PLUGIN_ROOT}/scripts/th_detect.sh"

Step 2: Install if Needed

If library=missing:

  • Ask permission: "training_hub isn't installed. I can install it for you — want me to proceed?"
  • If yes and installer=uv: run uv pip install training-hub
  • If yes and installer=pip: run pip install training-hub
  • If installer=none: tell the user they need Python and pip/uv installed first
  • Ask about extras:
    • CUDA: training-hub[cuda] — flash-attn, bitsandbytes for GPU acceleration
    • LoRA: training-hub[lora] — Unsloth, TRL for parameter-efficient fine-tuning
    • GRPO: training-hub[grpo] — ART, veRL for reinforcement learning

For installation issues, consult the training-hub-guide skill (installation-troubleshooting section).

Step 3: Check GPU

If gpu=unavailable, warn: "No GPU detected. Training requires CUDA-capable GPUs. You can still configure, but training will fail without a GPU."

Report GPU count if available.

Step 4: Quick Setup or Custom

If the user has a clear task ("fine-tune Llama on my data"), offer a fast path with sensible defaults:

"I detected N GPU(s). I can set up with these defaults:

  • Algorithm: lora_sft (parameter-efficient, works on a single GPU)
  • Learning rate: 1e-5
  • Epochs: 2
  • Batch size: 64
  • Max sequence length: 4096

You'll just need to provide your model path and data path. Accept these defaults, or customize?"

If the user accepts, ask only for model path and data path, then skip to Step 7.

If the user wants to customize, proceed with the full configuration.

Full Configuration

Ask these questions one at a time:

  1. Algorithm: "Which training algorithm do you want to use?" — consult the training-hub-guide skill for algorithm selection guidance if the user is unsure.
  2. Model path: "What's the model identifier?" — e.g., meta-llama/Llama-3.1-8B-Instruct, or a local path.
  3. Data path: "Where is your training data?" — Path to a JSONL file with messages field.
  4. Output directory: "Where should checkpoints be saved?" — Default: ./output
  5. GPU count: "How many GPUs should be used?" — Default: detected count or 1.

Step 5: Hyperparameters

Collect hyperparameters based on the chosen algorithm. Consult the training-hub-guide skill (hyperparameter-guide section) for recommended defaults by dataset size and algorithm.

Step 6: Logging Config (Optional)

Ask: "Do you want to configure experiment tracking?" (W&B, MLflow, or TensorBoard). See the training-hub-guide skill for logger details.

Step 7: Save Config

Write the config to .training-hub/config.json:

{
  "algorithm": "<algorithm>",
  "model_path": "<model_path>",
  "data_path": "<data_path>",
  "ckpt_output_dir": "<output_dir>",
  "nproc_per_node": N,
  "hyperparams": { ... },
  "algorithm_config": { ... },
  "logging": { ... }
}

Add .training-hub/ to .gitignore if not already present.

Step 8: Offer Memory Estimation

Ask: "Want me to estimate GPU memory requirements before training?"

If yes, run:

"${CLAUDE_PLUGIN_ROOT}/scripts/th_estimate.sh"

Updating Config

If this skill is invoked again and a config already exists, ask: "You already have a configuration. Do you want to update it or start fresh?"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.