CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-publisher-cli

Validate, version, and package SKILL.md folders for multi-registry marketplace publishing. Use when: Validate SKILL.md files against marketplace standards before shipping; Automate SemVer versioning and CHANGELOG updates for AI skills; Generate clean distribution ZIPs without git or cache junk files.

Quality

62%

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 ./plugins/nex-dev-essentials/skills/skill-publisher-cli/SKILL.md

The canonical home for this skill is skill-publisher-cli in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

28%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 reads as a marketplace landing page rather than operational skill instructions: it is padded with marketing prose, an FAQ, and promo links, and provides no executable commands or sequenced workflow — especially damning since the tooling it describes is explicitly not included in the folder. Structure exists (headers, an example, limitations), which keeps it from the bottom of the scale.

Suggestions

Replace the 'Why use this?', 'Questions' FAQ, and promotional footer sections with concise operational guidance, and move the 'When to use' list out of the body since it duplicates the frontmatter description verbatim.

Add executable guidance — the actual command(s) to run validation, versioning, and packaging — or, since the scripts are not bundled, state plainly what Claude can do with only the files present and remove the simulated CLI transcript.

Present the publish workflow as an explicit numbered sequence (validate -> dry-run -> review proposed changes -> apply -> verify dist/ output) with the dry-run output framed as a validation checkpoint before any files are written or versions bumped.

DimensionReasoningScore

Conciseness

Noticeably verbose for what it conveys: marketing prose ('transforms your raw AI skill folders into production-ready marketplace packages'), a 'Why use this?' section, a five-question FAQ that restates earlier content, and promotional footers ('More skills and info at nex-ai.be and slopsome.com', paid-catalog link). Not 1 because it does not lecture on concepts Claude already knows.

2 / 5

Actionability

Minimal concrete guidance: no commands or code appear anywhere, only a simulated dry-run transcript and a passing 'Ready to apply? Use --apply.' — and the body states 'Scripts, extension source, and templates from the original package are not in this folder', so nothing shown is actually executable from this skill. Not 1 because the example transcript is a concrete high-level hint of intended usage.

2 / 5

Workflow Clarity

The validate -> dry-run -> approve -> apply -> dist/ sequence is only implied via the 'Dry-run first' philosophy paragraph and the example; no steps are listed and no validation checkpoints are articulated for operations that write files and bump versions. Not 3 because steps are not actually enumerated, only hinted at.

2 / 5

Progressive Disclosure

The body has section headers but references no bundle files (references/, scripts/, assets/ do not exist in this folder), and FAQ/marketing content that does not belong in a SKILL.md is inlined across ~80 lines. Not 4 because at this length with off-topic material and zero reference signaling, organization is only partial.

3 / 5

Total

9

/

20

Passed

Description

78%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: it names concrete capabilities and includes an explicit multi-clause 'Use when:' trigger list keyed to natural domain terms (SKILL.md, SemVer, CHANGELOG, ZIP). Its main weakness is that the when-clauses mirror the capability statements instead of describing the situations in which a user would invoke it.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Validate, version, and package SKILL.md folders', 'SemVer versioning and CHANGELOG updates', 'clean distribution ZIPs without git or cache junk files' — with minor gaps; validation is only described as 'against marketplace standards' without naming what is checked. Not 5 because coverage details are thin, not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Explicit 'Use when:' clause with three concrete triggers plus a clear 'what' ('Validate, version, and package SKILL.md folders for multi-registry marketplace publishing'). Not 5 because the when-clauses restate the capability list as tasks rather than describing user situations ('when the user mentions...'); not 3 because the when-guidance is explicit, not merely implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('SKILL.md', 'SemVer', 'CHANGELOG', 'ZIP', 'marketplace', 'before shipping') that matches what a skill publisher would say. Not 5 because common synonyms like 'publish', 'distribute', 'release', or 'bump version' are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — SKILL.md marketplace/registry publishing — with distinct triggers (SKILL.md folders, SemVer/CHANGELOG for AI skills, registry-ready ZIPs), so overlap with other skills is minimal. Fits the anchor 5 example's pattern of a distinct trigger set.

5 / 5

Total

17

/

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

NexaiGuy/nex-ai-skills

Path

plugins/nex-dev-essentials/skills/skill-publisher-cli/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.