CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-bundle-release

Bundle release workflow — checkout, prepare, pr, diff-check, audit, publish, sync.

60

Quality

72%

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 ./.skillshare/skills/1k-bundle-release/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 a well-structured, actionable overview that delegates per-step detail to seven one-level reference files with clear navigation, and it sequences the release flow with validation checkpoints. It is concise and assumes Claude's competence while preserving project-specific context that is genuinely non-obvious.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes competence, with project-specific context (OneKey release branches, .env.version gotcha) that Claude would not already know; a little explanatory prose in the Context/Detection sections could be trimmed but earns its place.

4 / 5

Actionability

Provides concrete argument-routing logic, an executable copy-paste bash block for release-branch detection, and a literal command flow diagram; detailed per-subcommand logic is delegated to reference files, leaving only minor gaps inline.

4 / 5

Workflow Clarity

The seven-step release flow is clearly sequenced with an explicit sequence diagram and validation checkpoints (diff-check, audit before publish, user y/n confirmation); the detailed validate→fix→retry loops live in the referenced subcommand files rather than inline, a minor gap.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview that splits each subcommand into its own one-level-deep reference file (all seven referenced files exist in references/rules/), surfaced via both a Quick Reference table and a routing list for easy navigation.

5 / 5

Total

17

/

20

Passed

Description

66%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 is specific and reasonably distinctive, listing a concrete seven-step release workflow, but it omits any explicit 'when to use' trigger guidance, which limits its completeness. Adding a 'Use when...' clause would raise it across completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when shipping a OneKey bundle release — branching, PRing, auditing, or publishing to a release/* branch.'

Expand the terse subcommand tokens into verb+object phrases (e.g. 'check out a release branch', 'create a PR targeting release/*') to improve specificity and naturalness.

Include common synonyms or phrasings users might say ('release branch', 'ship a bundle', 'rebase to x') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Bundle release workflow') and lists seven concrete actions (checkout, prepare, pr, diff-check, audit, publish, sync), but these are terse command tokens without objects, leaving minor gaps versus fully descriptive coverage.

4 / 5

Completeness

It clearly states what the skill does (the seven-stage release workflow) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural release-workflow terms users would say ('checkout', 'prepare', 'pr', 'audit', 'publish', 'sync', 'bundle release'); a few natural synonyms or variations are missing, so it is not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The 'bundle release' niche plus the specific ordered subcommands make it mostly distinct, with only minor overlap risk against general git/commit skills.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 14 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 14 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.