⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
hf-release-notes
Generate Hugging Face Hub (huggingface_hub) release notes from cached PR JSON files. Use when asked to draft release notes from PR files.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Quick start
Install the hf CLI with the standalone installer:
# On macOS and Linux.
curl -LsSf https://hf.co/cli/install.sh | bash
# On Windows.
powershell -ExecutionPolicy ByPass -c "irm https://hf.co/cli/install.ps1 | iex"
Log in, then start working with the Hub:
# Log in (use --token $HF_TOKEN in non-interactive environments)
hf auth login
# Find models served by Inference Providers
hf models ls --warm
# Download a model
hf download Qwen/Qwen3-0.6B
# Upload files to your own repo
hf upload username/my-cool-model ./model.safetensors
# Sync a local folder to a storage bucket
hf buckets sync ./checkpoints hf://buckets/username/my-bucket
# Run a job on Hugging Face infrastructure
hf jobs run python:3.12 python -c "print('Hello from the cloud!')"
# Discover everything else
hf --help
The Hub uses tokens to authenticate applications (see docs). Check out the CLI guide for a tour of the main features.
What is huggingface_hub?
The huggingface_hub library allows you to interact with the Hugging Face Hub, a platform democratizing open-source Machine Learning for creators and collaborators. Discover pre-trained models and datasets for your projects, play with the thousands of machine learning apps hosted on the Hub, or create and share your own models, datasets and demos with the community. Everything ships in one package with two interfaces: the hf CLI for your terminal and the huggingface_hub library for Python — both designed to work well for humans and AI agents. Use them to:
- Download files from the Hub.
- Upload files to the Hub.
- Manage your repositories.
- Run Inference on deployed models.
- Run Jobs on Hugging Face infrastructure.
- Search for models, datasets and Spaces.
- Share Model Cards to document your models.
- Engage with the community through PRs and comments.
- Do all of the above from the terminal with the
hfCLI.
Built for humans and AI agents
The hf CLI is designed for people and coding agents alike: the same commands adapt their output when run by an agent. If you use Claude Code, Codex, Cursor, or another coding agent, install the hf CLI Skill — a command reference generated from your installed CLI:
# works with Claude Code, Codex, Cursor, OpenCode, Pi and any agent that loads skills from `.agents/skills`
hf skills add
Learn more in the Hugging Face CLI for AI agents guide and the announcement blog post.
Use the Python library
Install the huggingface_hub package with pip (this also installs the hf CLI):
pip install huggingface_hub
We recommend using uv for a fast and reliable install:
uv pip install huggingface_hub
In order to keep the package minimal by default, huggingface_hub comes with optional dependencies useful for some use cases. For example, if you want to use the MCP module, run:
pip install "huggingface_hub[mcp]"
To learn more about installation and optional dependencies, check out the installation guide.
Download files
Download a single file
from huggingface_hub import hf_hub_download
hf_hub_download(repo_id="zai-org/GLM-5.2", filename="config.json")
Or an entire repository
from huggingface_hub import snapshot_download
snapshot_download("sentence-transformers/all-MiniLM-L6-v2")
Files will be downloaded in a local cache folder. More details in this guide.
Create a repository
from huggingface_hub import create_repo
create_repo(repo_id="super-cool-model")
Upload files
Upload a single file
from huggingface_hub import upload_file
upload_file(
path_or_fileobj="/home/lysandre/dummy-test/README.md",
path_in_repo="README.md",
repo_id="lysandre/test-model",
)
Or an entire folder
from huggingface_hub import upload_folder
upload_folder(
folder_path="/path/to/local/space",
repo_id="username/my-cool-space",
repo_type="space",
)
More details in the upload guide.
Integrating with the Hub.
We
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
.opencode/skills/hf-release-notes/SKILL.md5.5 KBupstream ↗
--- name: hf-release-notes description: Generate Hugging Face Hub (huggingface_hub) release notes from cached PR JSON files. Use when asked to draft release notes from PR files. --- # HF Release Notes ## Overview Generate release notes for huggingface_hub from cached PR JSON files. This skill reads PR metadata, categorizes entries, and produces a formatted markdown release notes document. **Output directory:** The prompt will specify the output directory as `<output_dir>`. All paths below use this placeholder. ## Workflow ### 1. Read PR data Read all PR JSON files from `<output_dir>/tmp/pr_*.json`. Each file contains: ```json { "number": 1234, "title": "...", "author": "username", "merged_at": "2026-01-15T10:30:00Z", "body": "...", "labels": ["highlight", "cli"], "url": "https://github.com/huggingface/huggingface_hub/pull/1234", "doc_diffs": [ { "filename": "docs/source/en/guides/cli.md", "status": "modified", "patch": "@@ -10,6 +10,10 @@ ..." } ] } ``` The `doc_diffs` field contains unified diffs for any `.md` files under `docs/` that were changed in the PR. This is empty (`[]`) for PRs with no documentation changes. ### 2. Identify highlights A PR should be highlighted if: - It has the `"highlight"` label on GitHub, **or** - You judge it significant enough to deserve a detailed section (e.g., a major new feature, a meaningful UX improvement, or a notable breaking change) even without the label. Use your judgment — not every feature PR needs a highlight, but don't limit highlights to only labeled PRs. Each highlight section follows this structure: 1. **Emoji header** — e.g., `## 🖥️ New CLI commands` 2. **Prose summary** — 2-5 sentences describing the user-visible change in flowing text. Avoid bullet points here; write natural sentences. Only use bullets if the content truly calls for a list (e.g., enumerating 4+ distinct sub-features). 3. **Code examples** — if the PR introduces new commands or APIs, include a fenced code block with a concrete usage example (cherry-pick from doc diffs when available). 4. **PR attribution lines** — one bullet per PR that contributed to this highlight: `- PR title by @author in #1234` ### 3. Classify standard items For non-highlight PRs, classify into sections using `references/sections.md` heuristics based on: - PR labels - PR title keywords - PR body content ### 4. Use doc diffs and fetch relevant documentation For highlighted PRs and other PRs that introduce new features, commands, or APIs: **Use doc diffs first:** - Check the `doc_diffs` field in the PR JSON. If present, these contain the actual documentation changes made in the PR (unified diff format). - Use these diffs to understand what was documented, extract code examples, and write more accurate summaries. The diffs show exactly what the PR author wrote in the docs. - The `filename` field maps to a docs page URL. For example, `docs/source/en/guides/cli.md` → `https://huggingface.co/docs/huggingface_hub/main/en/guides/cli` **Fetch full doc pages when needed:** 1. Start by fetching the docs index page to discover the site structure: `https://huggingface.co/docs/huggingface_hub/main/en/index` 2. Based on the PR content (title, body, labels), identify which doc pages might be relevant. For example: - A CLI PR → check `https://huggingface.co/docs/huggingface_hub/main/en/guides/cli` - An Inference PR → check `https://huggingface.co/docs/huggingface_hub/main/en/guides/inference` - A new API class or method → check the corresponding reference page 3. Fetch the candidate doc page to confirm it covers the feature from the PR. 4. Only include a doc link if the page genuinely documents the feature. **How to reference:** - In highlight sections, add a line like: `📚 **Documentation:** [Guide name](https://huggingface.co/docs/huggingface_hub/main/en/guides/...)` - In standard sections, append the doc link inline after the attribution when relevant: `- PR title by @author in #1234 — [docs](https://huggingface.co/docs/huggingface_hub/main/en/...)` - Do NOT add doc links for internal/CI/test PRs or PRs that don't have user-facing docs. - Do NOT fabricate doc URLs — only link to pages you have actually fetched and verified. ### 5. Generate release notes Output to `<output_dir>/RELEASE_NOTES_<version>.md` using the structure from `references/release-notes-template.md`: - Title: `# [vX.Y.Z] <tagline>` (derive tagline from main highlights; always use the base version without prerelease suffix, e.g. `[v1.8.0]` even when generating for `v1.8.0.rc0`) - One section per highlight with emoji header and narrative - Standard sections for remaining items (only include sections with items) ### 6. Quality checks Before finishing: - Verify every PR from `<output_dir>/tmp/` appears exactly once - **Do NOT include any PR that does not have a corresponding file in `<output_dir>/tmp/`** — those PRs belong to a different release and must not appear in these notes - No empty sections - Consistent emoji headings - Every item ends with attribution: `by @author in #1234` - Doc links point to real, verified pages ## Input - Version string (e.g., "v1.3.8") - PR JSON files in `<output_dir>/tmp/` ## Output - Release notes markdown at `<output_dir>/RELEASE_NOTES_<version>.md` ## Resources - `references/release-notes-template.md`: Skeleton structure for release notes - `references/sections.md`: Keyword-based section mapping and guidance - Documentation site: `https://huggingface.co/docs/huggingface_hub/main/en/index`README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/huggingface-huggingface-hub-opencode-skills-hf-release-notes.md