CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-pack-builder

Create, validate, package, and optionally install original KunAgent skills.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/skill-pack-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 exceptionally lean, well-sectioned overview that respects the token budget and assumes Claude's intelligence. Its main weakness is actionability: the workflow tells Claude what artifacts to create and validate but never shows a concrete example (frontmatter, skill.json schema) or the actual validator invocation, leaving execution details to inference.

Suggestions

Add a minimal example of the YAML frontmatter and a skill.json skeleton (id, version, entry, triggers, priority) so the create steps are copy-paste ready instead of descriptive.

Include the concrete validation command(s) (e.g., the local validator invocation under bash) rather than only listing what to validate.

Add a short feedback loop after the validation step — what to do when validation fails (fix, re-run, only package when passing) — to lift workflow clarity to 5.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and efficient with zero padding: sections like "Tool routing", "Workflow", and "Completion gates" assume Claude's competence and never explain known concepts. It matches 'every token earns its place'; at worst the Purpose line repeats the description, which is standard skill format rather than padding.

5 / 5

Actionability

Concrete artifacts are named ("SKILL.md", "skill.json with stable id, version, entry, triggers, and priority", "~/.kun/skills", root manifest, license), but there is no example frontmatter, no skill.json schema, and no actual validator command — guidance is incomplete and missing key executable details. This sits at 'some concrete guidance but incomplete', below anchor 4's 'mostly executable guidance with concrete code or commands'.

3 / 5

Workflow Clarity

The five-step Workflow is clearly sequenced and includes validation ("Validate links, metadata, tool names, syntax, license, and prohibited secrets before packaging") reinforced by a Completion gates section, matching 'clear sequence with most checkpoints present'. It is not 5 because there is no explicit feedback loop (what to do when validation fails) and no concrete validation commands.

4 / 5

Progressive Disclosure

The skill is under 50 lines, references no external bundle files (and none exist in references/, scripts/, or assets/), and is organized into clear, well-labeled sections. Per the rubric's simple-skill guideline, this earns 5 with just well-organized sections and no nested references.

5 / 5

Total

17

/

20

Passed

Description

58%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 gives a compact, well- scoped 'what' for the skill lifecycle but entirely omits any 'when to use it' guidance and offers only generic verbs without concrete detail. Adding an explicit trigger clause and natural synonyms would substantially raise completeness and trigger term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to build, validate, package, or install a KunAgent skill, or mentions creating a new skill or skill pack."

Include natural synonyms users would actually say — "build", "bundle", "new skill", "skill pack", and relevant file names (e.g., SKILL.md, skill.json) — to broaden trigger term coverage.

Add one layer of concreteness to the actions, such as naming what validation checks (metadata, links, prohibited secrets) or the output artifact (a distributable skill archive).

DimensionReasoningScore

Specificity

"Create, validate, package, and optionally install" lists several actions spanning the full skill lifecycle, matching the 'lists several specific actions; minor gaps' anchor. It falls short of 5 because the actions are generic verbs with no concrete detail about what validation or packaging entail.

4 / 5

Completeness

The 'what' is clear (create, validate, package, install KunAgent skills) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 2 because the 'what' half is concrete, not vague.

3 / 5

Trigger Term Quality

Terms like "skills", "package", and "install" are relevant keywords, but common natural variations users would say ("build a skill", "bundle", "new skill", file extensions) are missing. This fits 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

"original KunAgent skills" carves out a clear niche (authoring/packaging skills for a specific platform) with minor overlap risk against generic skill-authoring or plugin-building skills. It is not a 5 because it lacks distinct explicit trigger phrases to fully disambiguate from those related skills.

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

KunAgent/Kun

Path

resources/bundled-skills/skill-pack-builder/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.