CtrlK
BlogDocsLog inGet started
Tessl Logo

release

Cut and publish a Neko Master release — main product (Docker, v* tags) or Go agent (agent-v* tags). Use when bumping versions, writing CHANGELOG entries, tagging, or verifying CI artifacts.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

The body is a lean, actionable release runbook with executable commands, a clearly sequenced workflow including validation and CI verification checkpoints, and well-signaled one-level references to external docs. No bundle files were present to verify.

DimensionReasoningScore

Conciseness

The body is lean — compact tables, numbered steps, and executable blocks with no concept-explanation padding — and every line carries operational information, matching the lean-and-efficient anchor.

3 / 3

Actionability

It provides copy-paste-ready commands (pnpm filters, tsc --noEmit, git tag -a, gh release create, go vet ./...) with concrete file paths and placeholders, matching the fully-executable anchor.

3 / 3

Workflow Clarity

The main release is a numbered 1-6 sequence with explicit validation gates (step 4 "all must pass") and a verify-CI checkpoint (step 6, "must end completed/success", "poll rather than assume"), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

Content is sectioned and detailed material is deferred one level deep with clear pointers ("See docs/agent/release.en.md", "docs/release-checklist.md") rather than inlined or nested, matching the well-signaled one-level reference anchor.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich, and complete, explicitly covering both what the skill does and when to use it in third-person voice. It carves a distinct niche with concrete tag-based release lines.

DimensionReasoningScore

Specificity

"Cut and publish", "bump versions", "writing CHANGELOG entries", "tagging", and "verifying CI artifacts" are multiple distinct concrete actions, matching the anchor for listing several specific actions rather than naming a domain with partial actions.

3 / 3

Completeness

It states the what ("Cut and publish a Neko Master release") and an explicit when ("Use when bumping versions..."), clearly answering both per the top anchor.

3 / 3

Trigger Term Quality

"Use when bumping versions, writing CHANGELOG entries, tagging, or verifying CI artifacts" gives good coverage of natural phrases a user would say when requesting a release, rather than jargon or a single generic term.

3 / 3

Distinctiveness Conflict Risk

The product-specific scope ("Neko Master", Docker, "v* tags", Go agent, "agent-v* tags") carves a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
foru17/neko-master
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.