xiaohongshu
xiaohongshu
Create your LLMOps data engineering skill in one prompt, then learn to improve it throughout the chapter
Full skill instructions
Before learning data engineering for fine-tuning—preparing training datasets that transform generic models into domain specialists—you'll own a data engineering skill.
This isn't downloading someone else's notes. You're building expertise from official documentation, creating a reusable asset that will guide you through the entire chapter and beyond.
Traditional learning: Read about data engineering, then maybe create a skill later.
Skill-First learning: Create your skill NOW, then use the chapter to test and improve it.
The difference matters because:
By Part 8, you've seen this pattern repeatedly. This chapter is no different: create the skill first, then battle-test it through real data engineering work.
Start clean. Don't reuse old state—clone fresh:
git clone if you prefer)cd claude-code-skills-lab
claude
Why clone fresh? State from previous chapters can interfere. A clean skills-lab means your skill starts from verified documentation, not cached assumptions.
Before asking Claude to create your skill, articulate what you need. Create a file called LEARNING-SPEC.md:
# LEARNING-SPEC: LLMOps Data Engineering Skill
## What I'm Building
A skill that helps me create high-quality training datasets for fine-tuning LLMs.
## Why I Need It
I want to fine-tune models on domain-specific tasks (like Task API operations) but need to understand:
- How to structure training data (formats like Alpaca, ShareGPT, ChatML)
- How to ensure data quality (accuracy, consistency, coverage, diversity)
- How to generate synthetic data cost-effectively (GPT-4o-mini, under $0.15)
- How to clean and validate datasets before training
## Success Criteria
My skill should be able to:
1. Explain when to use Alpaca vs ShareGPT vs ChatML format
2. Guide me through creating JSONL datasets with Pydantic validation
3. Help me generate synthetic training examples
4. Implement quality filtering (deduplication, LLM-as-Judge scoring)
5. Prepare train/validation/test splits correctly
## Constraints
- Must work within Colab Free Tier (T4 GPU, 15GB VRAM)
- Synthetic data generation costs must stay under $0.15 for 500 examples
- Should use Unsloth and Hugging Face, not vendor-locked platforms
## What I Already Know
- Python fundamentals (Part 5)
- Pydantic for data validation
- OpenAI API basics for generation
Save this file. It becomes your specification for what the skill should achieve.
Now ask Claude to create the skill, grounded in official documentation:
I want to create an llmops-data-engineer skill for preparing training datasets.
First, read my LEARNING-SPEC.md to understand what I need.
Then use Context7 to fetch documentation from:
1. Hugging Face datasets library
2. Unsloth fine-tuning documentation
3. OpenAI fine-tuning data format guide
Finally, create the skill using the skill-creator skill.
Ground everything in the official docs, not assumed knowledge.
Claude will:
Your skill appears at .claude/skills/llmops-data-engineer/.
Check that the skill was created correctly:
ls -la .claude/skills/llmops-data-engineer/
cat .claude/skills/llmops-data-engineer/SKILL.md
You should see a SKILL.md file with:
You now own an llmops-data-engineer skill built from:
| Source | What It Contributes |
|---|---|
| Hugging Face docs | Dataset formats, loading patterns, Hub integration |
| Unsloth docs | Training data requirements, efficiency patterns |
| OpenAI fine-tuning guide | Instruction format, conversation structure |
| Your LEARNING-SPEC | Your specific constraints and success criteria |
This skill isn't generic AI knowledge. It's grounded in authoritative sources and tailored to your needs.
Lessons 1-4 teach you what your skill already knows—but through hands-on practice that reveals nuances:
| Lesson | What You Learn | How Your Skill Improves |
|---|---|---|
| L01: Data Quality Principles | Garbage-in-garbage-out realities | Add quality dimension checklist |
| L02: Instruction Formats | Alpaca vs ShareGPT vs ChatML | Test: can it recommend the right format? |
| L03: Synthetic Data Generation | GPT-4o-mini cost-effective patterns | Add generation templates |
| L04: Data Cleaning | Deduplication, validation, filtering | Add cleaning pipeline guidance |
By the chapter's end, your skill is battle-tested and production-ready.
I want to create a training dataset for a Task API assistant.
The assistant should help users create, update, and complete tasks.
Using my llmops-data-engineer skill, help me decide:
1. Should I use Alpaca or ShareGPT format?
2. How many examples do I need for effective fine-tuning?
3. What quality dimensions should I check?
What you're learning: Whether your skill can give useful guidance right now. If it can't answer these questions well, you'll know exactly what to improve as you work through the chapter.
Look at my llmops-data-engineer skill and compare it to what we'll learn in this chapter:
- Data quality principles
- Instruction formats (Alpaca, ShareGPT, ChatML)
- Synthetic data generation with GPT-4o-mini
- Data cleaning and validation
What's missing from my skill that the chapter will teach?
Create a checklist of improvements I should make as I learn.
What you're learning: Self-assessment through AI dialogue. Your skill has gaps—that's expected. Identifying them upfront makes the chapter more purposeful.
I work in [your domain: healthcare/legal/finance/education/other].
Help me think about what training data I would need to fine-tune a model
for my specific use case. Ask me questions about:
- What tasks do I need the model to perform?
- What knowledge does it need that base models lack?
- Where would I get training examples?
What you're learning: Pattern transfer—applying data engineering concepts to your actual work. The Task API example teaches the mechanics; your domain is where the value lies.
Your skill is created from AI interpretation of documentation. It may have gaps or inaccuracies. The chapter exists to surface these gaps through practice. Don't trust the skill blindly—verify its guidance against your own understanding as you learn.
xiaohongshu
technical spec
product ux expert
database patterns
Conduct multi-agent task orchestration and workflow coordination.
Initialize project with Conductor artifacts (product definition,
Expert in web animations, transitions, and motion design using Framer Motion and CSS
Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...
PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.
Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...
Display project status, active tracks, and next actions
Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience