CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/hf-release-notes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a strong, actionable instruction skill: a clear six-step workflow with concrete paths, schemas, formats, and a closing validation checklist for the batch operation, with detail appropriately offloaded to real reference files. The gaps are minor: no explicit feedback loop on validation failure, one orphaned bundle file, and light redundancy between inline guidance and the template.

DimensionReasoningScore

Conciseness

The body is lean and instructional: it documents the PR JSON schema in one compact example, gives exact path patterns, and never explains concepts Claude already knows (no "what is a PR" or "what is a diff" padding). It falls short of anchor 5 only through minor redundancy — the highlight-section structure and doc-link formatting rules are spelled out inline at some length even though a template file already encodes much of it, and section 4's "Use doc diffs first" and "Fetch full doc pages" sub-blocks repeat the filename→URL mapping idea twice.

4 / 5

Actionability

Guidance is fully concrete and executable: exact input glob (`<output_dir>/tmp/pr_*.json`), a complete JSON schema example, exact output filename pattern (`RELEASE_NOTES_<version>.md`), verbatim attribution formats (`- PR title by @author in #1234`), concrete doc-URL construction with a worked example (`docs/source/en/guides/cli.md` → the docs URL), and explicit anti-fabrication rules. Per the scoring note, absence of code is not penalized in an instruction-only skill, and the specific examples cover the common cases.

5 / 5

Workflow Clarity

The six-step workflow is clearly sequenced (read → highlight → classify → enrich → generate → check) and ends with an explicit validation checklist for a batch operation ("Verify every PR from `<output_dir>/tmp/` appears exactly once", "Do NOT include any PR that does not have a corresponding file", "No empty sections", "Doc links point to real, verified pages"), so the batch-ops cap of 3 does not apply. It stops short of anchor 5 because there is no explicit error-recovery feedback loop — the checks say what to verify but not what to do when a check fails (e.g., "if a PR is missing, re-scan and fix before regenerating").

4 / 5

Progressive Disclosure

Scored against the actual bundle: the body cleanly splits detail into one-level-deep references that exist and are clearly signaled in a Resources section (`references/sections.md`, `references/release-notes-template.md`), and the SKILL.md itself stays a readable overview. It misses anchor 5 because `references/slack-post-template.md` is present in the bundle but never referenced from SKILL.md — an undiscoverable orphan — and some detailed guidance (highlight structure, doc-link formatting rules) is inlined where the template file partially duplicates it.

4 / 5

Total

17

/

20

Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific to a clear niche and correctly answers both "what" and "when" in third person without fluff. Its main weakness is breadth: it names only one action and a thin set of trigger phrases, missing synonyms like "changelog" or "pull requests" that a user would naturally say.

Suggestions

Enumerate the concrete actions the skill performs, e.g., "Reads PR metadata, categorizes entries into highlight and standard sections, enriches items with verified documentation links, and writes a formatted markdown release-notes file."

Broaden the trigger phrase to cover natural variations: "Use when asked to draft release notes or a changelog from merged PR / pull request files, or to summarize what shipped in a huggingface_hub release."

Include the repository keyword "huggingface_hub" more prominently as a trigger so the skill is distinguishable from generic release-note generators for other repos.

DimensionReasoningScore

Specificity

"Generate Hugging Face Hub (huggingface_hub) release notes from cached PR JSON files" names the domain and one concrete action (generate release notes) plus the input source, but coverage is not comprehensive — no mention of the categorization, doc-link enrichment, or output format that the skill actually performs. It sits between anchor 3 (domain + 1-2 concrete actions, not comprehensive) and anchor 4 (several specific actions with minor gaps), closer to 3 because only one action is stated.

3 / 5

Completeness

The "what" is explicit ("Generate Hugging Face Hub (huggingface_hub) release notes from cached PR JSON files") and the "when" is present ("Use when asked to draft release notes from PR files"), so both boxes are checked — satisfying the >3 cap requirement. Not a 5 because the "when" clause is narrow and somewhat circular (it repeats "PR files" rather than giving varied concrete trigger phrases like "changelog", "summarize merged PRs", or "what's new in vX.Y.Z").

4 / 5

Trigger Term Quality

"release notes", "PR", and "draft release notes" are natural terms a user would say, but common variations and synonyms are missing — e.g., "changelog", "PRs", "pull requests", "huggingface_hub", "HF". This matches anchor 3 (some relevant keywords but missing common variations or synonyms) rather than 4, which requires good coverage with only a few terms absent.

3 / 5

Distinctiveness Conflict Risk

The niche is clear — release notes for huggingface_hub specifically, from cached PR JSON files — which distinguishes it from generic documentation or git-diff skills. However, "draft release notes from PR files" as a trigger phrase has minor overlap risk with any other release-notes/changelog skill, matching anchor 4 (mostly distinct, minor overlap risk with closely related skills) rather than 5 (clear niche with minimal conflict risk).

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

huggingface/huggingface_hub

Path

.opencode/skills/hf-release-notes/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.