CtrlK
BlogDocsLog inGet started
Tessl Logo

skillnet

Search, download, create, evaluate, analyze and route reusable agent skills with SkillNet. Use when asked to find or reuse a skill, turn a repo/document/trace into a skill, assess skill quality, build a local skill graph, select skills for a task, or fill a clearly identified capability gap with a reusable skill. 中文:搜索、下载、创建、评估、分析与路由技能。不用于普通代码修改或仅阅读文档。

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 body is an efficient, highly actionable overview: concrete CLI commands for every workflow, explicit sequencing, built-in validation, and a dedicated error-recovery section with feedback loops. The only weaknesses are minor — slight redundancy in a few policy sentences and a scripts/ bundle directory that is not surfaced or navigable from SKILL.md itself.

Suggestions

Add one line in the Create and evaluate section linking the bundled helper scripts (e.g. scripts/skillnet_create.py, scripts/skillnet_validate.py) or move their usage entirely to workflow-patterns.md with a pointer from SKILL.md, so every bundle file is discoverable from the overview.

Tighten the few redundant policy sentences (e.g. collapse "An existing destination is preserved by default... Do not silently delete an existing skill" into one sentence) and move the inline "version 0.1.1+" pin into setup.md, which already tracks CLI installation.

DimensionReasoningScore

Conciseness

The body is dense and imperative with almost no explanation of concepts Claude already knows, fitting the efficient/minor-trim anchor; it falls below the lean-every-token-counts anchor because of a few redundant policy sentences ("Do not silently delete an existing skill" restates the preceding --overwrite guidance) and inline version-sensitive details ("version 0.1.1+") not confined to a setup/reference section.

4 / 5

Actionability

Every workflow is backed by copy-paste-ready, fully-specified CLI commands with flags and --json ("skillnet search \"pdf\" --limit 5 --json", "skillnet download \"<skill_url>\" --target-dir ./downloaded_skills --json", "skillnet create --prompt ... --evaluate --json", "skillnet evaluate ..."), covering the common cases, which matches the fully-executable anchor at 5 rather than the minor-gaps anchor at 4.

5 / 5

Workflow Clarity

All five workflows are explicitly sequenced with arrows and decision points, validation is built in ("checks generated structure before evaluating", "exercise the skill on a small representative input"), and the Results and recovery section provides feedback loops for errors ("ok: true", nonzero exit, "retry evaluation, not creation"), matching the explicit-validation/feedback-loop anchor at 5; destructive overwrite is guarded ("Use --overwrite only when an update/replacement is intended"), so the destructive-operation cap of 3 does not apply.

5 / 5

Progressive Disclosure

The body is a clear overview with six well-signaled, one-level-deep reference pointers, each with a stated purpose ("Read [api-reference.md] for flags, output fields, provider compatibility and error recovery"), and all referenced files exist in references/; it falls just short of the ideal-splitting anchor because the scripts/ directory (3 files) is never mentioned or linked from SKILL.md — the only path to it is a passing mention inside workflow-patterns.md — a minor organization gap per the level-4 anchor.

4 / 5

Total

18

/

20

Passed

Description

87%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.

A strong description: explicit what-and-when structure, concrete trigger phrases, and an explicit exclusion boundary that reduces conflict risk. The Chinese translation line duplicates the English content (only the exclusion clause is new), which adds padding without adding capability information.

DimensionReasoningScore

Specificity

The description lists six concrete actions ("Search, download, create, evaluate, analyze and route reusable agent skills"), matching the several-specific-actions anchor with comprehensive workflow coverage; it stops short of the level-5 anchor only because the actions are stated at the verb level without object-level detail (e.g. no mention of GitHub URLs, SKILL.md structure checks, or the embedding-based graph), a minor coverage gap.

4 / 5

Completeness

It explicitly answers both what ("Search, download, create, evaluate, analyze and route reusable agent skills with SkillNet") and when ("Use when asked to find or reuse a skill, ... or fill a clearly identified capability gap"), with concrete trigger phrases and an additional negative scope boundary ("不用于普通代码修改或仅阅读文档"), matching the level-5 anchor exactly rather than the weaker-'when' anchor at 4.

5 / 5

Trigger Term Quality

Natural phrases a user would actually say are well covered ("find or reuse a skill", "turn a repo/document/trace into a skill", "assess skill quality", "build a local skill graph", "select skills for a task", "capability gap"), fitting the good-coverage anchor; a few common variations are missing (e.g. "SKILL.md", "skill library", "install a skill"), keeping it below the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and distinct (a SkillNet SDK workflow for reusable agent skills, not general coding or document reading — explicitly excluded), so triggers are unlikely to fire for unrelated skills, matching the clear-niche/minimal-conflict anchor at 5 rather than the minor-overlap anchor at 4.

5 / 5

Total

18

/

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
zjunlp/SkillNet
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.