Conversation
| @@ -1,186 +1,130 @@ | |||
| --- | |||
| name: hugging-face-cli | |||
| description: Execute Hugging Face Hub operations using the `hf` CLI. Use when the user needs to download models/datasets/spaces, upload files to Hub repositories, create repos, manage local cache, or run compute jobs on HF infrastructure. Covers authentication, file transfers, repository creation, cache operations, and cloud compute. | |||
| name: hf-cli | |||
There was a problem hiding this comment.
cc @evalstate I have no strong opinion here, should we rename the skill to hugging-face-cli in huggingface_hub ?
There was a problem hiding this comment.
just note, we are about to fix all skills on this repo hugging-face-* to huggingface-*
There was a problem hiding this comment.
is it okay if we keep the SKILL name hf-cli ? huggingface-cli is the name of the deprecated command and we want to avoid this name as much as possible since most LLMs still think that huggingface-cli still exists. wdyt?
There was a problem hiding this comment.
No really strong views on the name.
This skill is a little unusual in that we want:
- To trigger when the user wants to achieve something with "hugging face" or "hub"
- To (hopefully) intercept when the model would otherwise have used the deprecated "huggingface_hub" command.
For things following the spec it should look in the system prompt like:
<available_skills>
hf-cli
(Our description)
/home/.wherever/SKILL.md
</available_skills>
I think all the proposed names are reasonably good options that have a good chance of triggering the skill... I'd go for whatever looked aesthetically best :)
There was a problem hiding this comment.
very clear, thanks @evalstate! keeping hf-cli then, we can reassess if needed :)
There was a problem hiding this comment.
btw is it okay to merge even though the validation workflow is failing? 🙈
There was a problem hiding this comment.
Updates ->
Rename directory to match skill name (spec requirement)
Update .claude/marketplace.json manually maintained metadata.
There was a problem hiding this comment.
LGTM thank you!
Update marketplace metadata to match name
3 participants
Following some users feedback, we made the skill much more token-efficient (~12k tokens -> ~1.3k tokens) so it actually works with open models that can't handle that many tokens at once. The skill is now auto-generated by introspecting the CLI's command tree.
We're also setting up a GitHub Action in
huggingface_hubhuggingface/huggingface_hub#3885 that will automatically open a PR here whenever we cut a new release, so the skill will always stay in sync with the CLI.