Add blog post: Teaching LLMs When to Use Their Skills#3310
Open
mpnikhil wants to merge 8 commits intohuggingface:mainfrom
Open
Add blog post: Teaching LLMs When to Use Their Skills#3310mpnikhil wants to merge 8 commits intohuggingface:mainfrom
mpnikhil wants to merge 8 commits intohuggingface:mainfrom
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Author
|
Cc @burtenshaw |
Author
|
Cc @pcuenca |
Collaborator
|
no worries @pcuenca. I can take a first pass on this. |
burtenshaw
reviewed
Mar 30, 2026
Collaborator
burtenshaw
left a comment
burtenshaw
left a comment
There was a problem hiding this comment.
@mpnikhil Looks great so far. I would just focus the post on the env a bit more and it should be good to go.
- Update title per suggestion - Remove guest/org from author metadata - Define what a skill is in the intro - Add note clarifying evidence level (design, not empirical results) - Remove attribution from GEPA intro mention - Clarify synthetic tasks are for stress-testing generalization - Move Training Approaches to Open Directions (no training results yet) - Update upskill section wording per suggestion - Update _blog.yml tags per suggestion Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Collaborator
|
Looks good @mpnikhil . Could you add a thumbnail image. |
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
# Conflicts: # _blog.yml
pcuenca
reviewed
Apr 14, 2026
| - game-dev | ||
|
|
||
| - local: upskiller-skill-invocation-env | ||
| date: April 8, 2026 |
Member
There was a problem hiding this comment.
Reminder to update before release.
Apply suggested edits: clarify TL;DR deployment description, simplify skill definition, reframe note as hackathon proof-of-concept, polish SkillsBench section bullets, drop repetitive catalog paragraph, and tighten task description. Move SkillsBench paper link inline citation to references only. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Congratulations! You've made it this far! Once merged, the article will appear at https://huggingface.co/blog. Official articles
require additional reviews. Alternatively, you can write a community article following the process here.
Preparing the Article
You're not quite done yet, though. Please make sure to follow this process (as documented here):
mdfile. You can also specifyguestororgfor the authors.Here is an example of a complete PR: #2382
Getting a Review
Please make sure to get a review from someone on your team or a co-author.
Once this is done and once all the steps above are completed, you should be able to merge.
There is no need for additional reviews if you and your co-authors are happy and meet all of the above.
Feel free to add @pcuenca as a reviewer if you want a final check. Keep in mind he'll be biased toward light reviews
(e.g., check for proper metadata) rather than content reviews unless explicitly asked.