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

setup-guide

Skill161 starsChanged 6 months agoApache-2.0View on GitHub

Use when the user wants to set up synthetic data generation for the first time, or when sdg_hub is not yet installed/configured in the current environment.

  • Reads credentials
  • 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

9 rules. 0 are common, 5 are distinctive, and 4 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.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask permission: "I can install it for you.

    line 21
  2. Very specific:

    If yes and installer=uv: run uv pip install sdg_hub

    line 22
  3. Very specific:

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

    line 24
  4. Distinctive:

    If the user accepts, skip to Step 5 using the detected key and defaults.

    line 42
  5. Distinctive:

    Ask these questions one at a time:

    line 50
  6. Distinctive:

    If no API key was detected in Step 3, tell the user to set the appropriate environment variable:

    line 62
  7. Very specific:

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

    line 74
  8. Very specific:

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

    line 86
  9. Distinctive:

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

    line 111

“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

sdg_hub Setup Guide

You are helping the user set up synthetic data generation.

Step 1: Detect Environment

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

Step 2: Install if Needed

If library=missing:

  • Explain: "sdg_hub is a framework for synthetic data generation — it uses composable blocks and YAML-defined flows to build LLM training datasets from seed data."
  • Ask permission: "I can install it for you. Want me to proceed?"
  • If yes and installer=uv: run uv pip install sdg_hub
  • If yes and installer=pip: run pip install sdg_hub
  • If installer=none: tell the user they need Python and pip/uv installed first

Step 3: Quick Setup or Custom

Also check for API keys in the environment:

echo "openai_key=${OPENAI_API_KEY:+found}" "anthropic_key=${ANTHROPIC_API_KEY:+found}"

If an API key was detected, offer a one-question fast path:

"I detected your OpenAI API key. I can set up with these defaults:

  • Model: openai/gpt-4o-mini
  • Temperature: 0.7
  • Concurrency: 5

Accept these defaults, or would you like to customize?"

If the user accepts, skip to Step 5 using the detected key and defaults.

For Anthropic keys, default to anthropic/claude-sonnet-4-20250514.

If no API key was detected, or the user wants to customize, proceed to Step 4.

Step 4: Collect Configuration

Ask these questions one at a time:

  1. Model: "Which LLM model do you want to use for generation?" — e.g., openai/gpt-4o-mini, meta-llama/Llama-3.3-70B-Instruct, anthropic/claude-sonnet-4-20250514
  2. API endpoint: "What's your model endpoint URL?" — e.g., http://localhost:8000/v1 for vLLM, or leave empty for cloud provider defaults
  3. Temperature: "What temperature for generation?" (default: 0.7)
  4. Max concurrency: "How many parallel LLM requests?" (default: 5) — higher is faster but may hit rate limits
  5. Checkpoint directory: "Where should generation checkpoints be saved?" (default: ./checkpoints) — allows resuming interrupted runs

Step 5: Ensure API Key

API keys are read from environment variables — never store them in the config file. LiteLLM (used by sdg_hub) reads standard env vars automatically.

If no API key was detected in Step 3, tell the user to set the appropriate environment variable:

"Set your API key as an environment variable before running generation:

export OPENAI_API_KEY="sk-..."        # OpenAI models
export ANTHROPIC_API_KEY="sk-ant-..."  # Anthropic models

For local endpoints (vLLM, Ollama) that don't require authentication, no API key is needed. LiteLLM picks up these env vars automatically — no extra configuration required."

Step 6: Save Config

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

{
  "model": "<model>",
  "api_base": "<endpoint>",
  "temperature": 0.7,
  "max_concurrency": 5,
  "checkpoint_dir": "./checkpoints"
}

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

Confirm the config file was written, then report success:

"Setup complete! To run generation, use the data-generation skill, or the flow-browser skill to browse available flows.

API keys are read from environment variables, not the config file. Make sure the appropriate variable is set in your shell:

export OPENAI_API_KEY="sk-..."        # OpenAI models
export ANTHROPIC_API_KEY="sk-ant-..."  # Anthropic models

Local endpoints (vLLM, Ollama) don't need an API key."

Step 7: Verify

List available flows to confirm the installation works:

"${CLAUDE_PLUGIN_ROOT}/scripts/sdg_flows.sh" list

Report success and remind the user they can now use the data-generation skill to run generation, or the flow-browser skill to browse available flows.

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.