Please create a Huggingface Transformers SKILL for Claude
Author: Emasoft
Pull request: no
Labels: name: Good First Issue

name: Feature request

### Feature request

Please create a Huggingface Transformers SKILL for Claude and a PLUGIN for Claude Code.

### Motivation

It is very hard to navigate all the features of the Transformers library. Letting Claude guide us would make things much faster.

### Your contribution

I'll help testing the SKILL on my mac M4.

Comments:
This is interesting but I'm not sure the core team has capacity! People are welcome to make PRs, but **please** do not just write them with an LLM or something. We will probably only accept skills after they get some community testing to confirm they're actually useful.

Hi @Rocketknight1 ,
 I can take a stab at it using the official [docs](https://code.claude.com/docs/en/skills) as a reference. I already have some basic stuff ready that I worked on a few weeks ago.

<img width="1214" height="504" alt="Image" src="https://github.com/user-attachments/assets/f750dcff-17a1-4786-b553-745ae0bef17f" />

Is this still an open issue ?

> Is this still an open issue ?

Hi @coolgalsandiego 
yes, it is, if I’m not mistaken. I’m almost done with the PR. I just need to do some testing before creating it next week. 

@gautamvarmadatla Great! Does the skill include the diffusers?

Hi @Emasoft,
Apologies for the delayed response and for the delay on the PR. I haven’t been feeling well over the past week.

To answer your question, no. I made it more Transformers specific. But I can add it in if you’d like. Please let me know. I’ll try to create a PR and close this issue this week. Thanks!

A PR would be nice, at least as a starting point for a review! It doesn't have to be immediately perfect

> A PR would be nice, at least as a starting point for a review! It doesn't have to be immediately perfect

Sure! will be done over next couple of days. I'll CC you on the PR :) 

Hello...I would like to work on this issue by creating a beginner friendly Claude skill example for the Hugging Face Transformers library. My goal is to provide a clear and practical demonstration that will help users navigate the library more efficiently. I will focus on producing a working Python example along with documentation to make it easy for others to follow. Please let me know if there are any specific requirements or preferred models for the skill. Thank you


Is this still an open issue ?

This is still open, but we'd prefer smaller, simpler and well-tested changes, rather than big ones. Ideally, it would start by identifying areas where Claude or other code agents currently fail. The goal is to measurably improve code agent performance, not just fill files with 1000 lines of LLM output

got you

Hi! I’d love to work on this issue. Could you please assign it to me?


Hi  @Emasoft ,

I'm a student contributor interested in working on this issue. 
Could you please clarify what exactly "create a SKILL for Claude" means?

Specifically:
1. Is this about creating a new example in `examples/` directory?
2. Should this be an integration script between Transformers and Claude API?
3. Are there existing skill templates I should follow?
4. What should be the main functionality?

I want to ensure I'm building exactly what's needed. 
Thank you for your guidance!
Cherehani Makigo.

@cmakinet 

[Skills](https://support.claude.com/en/articles/12512176-what-are-skills) are a system introduced by Anthropic to teach large language models (LLMs) such as **Claude Opus 4.5**—new domains, tools, or workflows in a structured and reusable way.

Skills work across multiple environments:

- **Claude Code (CLI)**
- **Claude Web**
- **Claude Desktop**

Recently, Anthropic **open-sourced the Skills specification**, making it a vendor-neutral standard. As a result, Skills can now be supported by other platforms and vendors, including **OpenAI**, **Google**, and tooling ecosystems like **Codex** or **Cursor**.

---

## The Agent Skills Open Standard

The full, open specification for Skills—now called **Agent Skills**—is available here:

👉 **https://agentskills.io/**

On the site you’ll find:

- The complete **schema and format specification**
- A **reference validator script** to verify that your Skill conforms to the manifest and schema

This makes Skills portable, inspectable, and interoperable across AI platforms.

---

## What Skills Enable

A Skill can teach an AI model *everything* about a given subject.

For example, creating a **Hugging Face Transformers or Diffusers Skill** means that any compatible LLM (e.g. Claude Opus 4.5, GPT-5.2 Codex, etc.) can:

- Instantly understand the APIs and concepts of those libraries
- Write production-ready code using them
- Debug existing code
- Explain concepts and teach users how to use the libraries effectively

Once installed, the Skill becomes part of the model’s working knowledge—no repeated prompting or explanations required.

---

## Using Skills in Claude

You can learn how Skills are loaded and executed in Claude here:

- **Claude (Web & Platform):**  
  https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview#how-skills-work

- **Claude Code (CLI):**  
  https://code.claude.com/docs/en/skills

---

## Real-World Example

Skills are already being used in production.

For instance, **HeyGen** published a Skill that allows Claude to generate videos using avatars and influencers for platforms like Instagram and TikTok:

👉 https://github.com/heygen-com/skills

This demonstrates that Skills are not limited to programming, they can encode full product capabilities and workflows.

---

## Skill Structure

A Skill is a self-contained knowledge package with the following structure:

- Knowledge is split into **multiple `.md` files**
- Each reference file must be **no more than 500 lines**
- All reference files are indexed and described by a mandatory root file:  
  **`SKILL.md`**

The Skill must contain *everything* needed for the model to understand the domain. It must not refer to online articles or books, papers, etc. but be self-contained and exhaustive. If it teaches an API, it must contain all the API entries, not just few examples. The full knowledge about something must be inside the skill. And it must be written in a way that the AI can understand. So every concept must be defined before using it and the procedures must be actionable step-by-step descriptions. Examples must be included very often to let the AI understand better.
The art of writing a skill is all about knowing how to teach to the AI model. The main trick is to always accompany each concept with an example.
If you wrote the Skill about huggingface transformers (and diffusers) well, the result will be that you would be able to say to Claude "Write a program that uses an AI model from huggingface, running locally on my computer for free, to read a novel ebook and to write the sequel in the same style". And it will do it in one shot.

---

## Creating Skills with `skill-creator`

You don’t need to start from scratch.

Anthropic provides an official Skill called **`skill-creator`** that teaches Claude how to write new Skills.

- Repository:  
  👉 https://github.com/anthropics/skills
- Installation instructions are included for **Claude Code**

Once installed, you can simply ask Claude to guide you through creating your own Skill step by step.

  
---

## Where to Find Skills Online
  
If you want to see some examples of skills, those are great websites with thousands of skills free to download:

https://skills.sh       (~29,000 skills)
https://skillsmp.com    (~106,000 skills)



I've created a Hugging Face Transformers skill for Claude/OpenClaw:

https://github.com/kaigritun/huggingface-transformers-skill

Features:
- ✅ Text generation, sentiment analysis, NER, translation
- ✅ JSON output for easy agent integration
- ✅ Works with 150k+ models on the Hub
- ✅ Ready to test on M4 Mac

The skill provides Python scripts that agents can call via exec(), with clean JSON responses. All common transformers tasks are covered (generation, classification, NER, etc).

Happy to iterate based on feedback!

I'm closing this, even though it might theoretically be useful, because it's attracting tons of awful code agent contributions.