Agent skill · Data & Analytics

caffe-cifar-10

Guidance for building Caffe from source and training CIFAR-10 models. This skill applies when tasks involve compiling Caffe deep learning framework, configuring Makefile.config, preparing CIFAR-10 dataset, or training CNN models with Caffe solvers. Use for legacy ML framework installation, LMDB dataset preparation, and CPU-only deep learning training tasks.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill caffe-cifar-10 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/ai-ml/caffe-cifar-10/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Caffe CIFAR-10 Build and Training This skill provides procedural guidance for building the Caffe deep learning framework from source and training models on the CIFAR-10 dataset. ## When to Use This Skill - Building Caffe from source on Ubuntu/Debian systems - Training CIFAR-10 or similar image classification models with Caffe - Configuring Caffe for CPU-only execution - Troubleshooting Caffe build and dependency issues ## Critical Requirements Checklist Before starting, identify ALL requirements from the task specification: 1. **Execution mode**: CPU-only vs GPU (affects solver configuration) 2. **Iteration count**: Specific number of training iterations required 3. **Output files**: Where training logs and models should be saved 4. **Model checkpoints**: Which iteration's model file is expected ## Phase 1: Dependency Installation ### System Dependencies Install required packages before attempting to build: ```bash apt-get update && apt-get install -y \ build-essential cmake git \ libprotobuf-dev libleveldb-dev libsnappy-dev \ libhdf5-serial-dev protobuf-compiler \ libatlas-base-dev libgflags-dev libgoogle-glog-dev liblmdb-dev \ libopencv-dev libboost-all-dev \ python3-dev python

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Critical Requirements Checklist
  3. Phase 1: Dependency Installation
  4. System Dependencies
  5. Verification Step
  6. Phase 2: Caffe Source Acquisition
  7. Clone and Checkout
  8. Common Mistake
  9. Phase 3: Makefile.config Configuration
  10. Create Configuration File
  11. Essential Configuration Changes
  12. Configuration Verification
  13. Phase 4: Building Caffe
  14. Memory-Aware Compilation
Ships with 1 file
  • metadata.json
Commands it runs
apt-get update && apt-get install -y \
build-essential cmake git \
libprotobuf-dev libleveldb-dev libsnappy-dev \
libhdf5-serial-dev protobuf-compiler \
libatlas-base-dev libgflags-dev libgoogle-glog-dev liblmdb-dev \
libopencv-dev libboost-all-dev \
python3-dev python3-numpy python3-pip
dpkg -l | grep -E "libhdf5|libopencv|libboost"
git clone https://github.com/BVLC/caffe.git
cd caffe
More from claude-skill-registry
All skills →
About this skill
What does the caffe-cifar-10 skill do?

Guidance for building Caffe from source and training CIFAR-10 models. This skill applies when tasks involve compiling Caffe deep learning framework, configuring Makefile.config, preparing CIFAR-10 dataset, or training CNN models with Caffe solvers. Use for legacy ML framework installation, LMDB dataset preparation, and CPU-only deep learning training tasks.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill caffe-cifar-10 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going