CtrlK
BlogDocsLog inGet started
Tessl Logo

hugging-face

Hugging Face integration. Manage Models, Datasets, Spaces. Use when the user wants to interact with Hugging Face data.

60

Quality

71%

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 ./skills/hugging-face/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 skill is highly actionable with concrete commands and a solid connection workflow, but it carries introductory padding, a dangling step reference, and no validation guidance for the destructive repository actions it exposes.

Suggestions

Remove the introductory "Hugging Face is a platform..." paragraph and the empty Overview stub; assume Claude knows what Hugging Face is.

Add a verification/caution step for destructive actions (e.g., confirm the repository name and list files before running delete-repository or move-repository).

Fix the "skip to Step 2" reference by labeling the target section (e.g., "## Step 2: Search for actions") so the sequence is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands and tables, but the opening paragraph ("Hugging Face is a platform and community for machine learning...") and the empty "Hugging Face Overview" stub explain concepts Claude already knows and add padding.

3 / 5

Actionability

It provides copy-paste-ready commands (login, connection ensure/get, action list/run, request) with concrete flags and a populated actions table, covering the common cases fully.

5 / 5

Workflow Clarity

The connection flow has explicit state-based validation and a poll-after-action feedback loop, but destructive operations (delete-repository, move-repository) get no verification guidance and "skip to Step 2" is a dangling reference; the destructive-ops cap applies.

3 / 5

Progressive Disclosure

Sections are well-organized with clear headers and no nested references, and there are no bundle files to split out; minor gaps like the placeholder "Overview" stub keep it from a 5.

4 / 5

Total

15

/

20

Passed

Description

73%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 answers both what and when with a clear, distinct niche, but relies on the generic verb "Manage" and a broad trigger clause rather than enumerating concrete actions and specific trigger phrases.

Suggestions

Replace the generic "Manage Models, Datasets, Spaces" with specific concrete actions (e.g., "Create, list, move, and delete model, dataset, and Space repositories").

Expand the "Use when" clause with concrete triggers (e.g., "Use when the user wants to list, create, duplicate, or delete Hugging Face models, datasets, or Spaces").

Add common synonyms/extensions users might say (e.g., "HF Hub", "model hub") to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

"Manage Models, Datasets, Spaces" names the domain and several resources, but the single verb "Manage" is generic rather than a list of concrete actions, so it does not reach the specific-action coverage of level 4.

3 / 5

Completeness

Both "what" (Hugging Face integration; manage Models/Datasets/Spaces) and an explicit "Use when the user wants to interact with Hugging Face data" trigger are present, but the "when" clause is somewhat generic rather than listing concrete trigger phrases.

4 / 5

Trigger Term Quality

"Hugging Face", "Models", "Datasets", "Spaces", and "interact with Hugging Face data" are natural terms a user would say, giving good keyword coverage, though a few common variants are missing.

4 / 5

Distinctiveness Conflict Risk

"Hugging Face integration" carves out a clear niche with distinct platform-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.