CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-dev-commands

OneKey development commands plus branch, commit, validation, and PR conventions.

62

Quality

74%

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-dev-commands/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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-organized, highly actionable command catalog with real references offloading git conventions and mobile-shell details to separate files. Its only gaps are minor: some redundant sub-bullet scaffolding and absent explicit error-recovery feedback loops in the validation workflow.

DimensionReasoningScore

Conciseness

The body is mostly lean — terse command entries with useful runtimes, common issues, and troubleshooting rather than padding — but the repeated sub-bullet scaffolding across many commands could be trimmed slightly.

4 / 5

Actionability

Every entry gives a copy-paste-ready command with concrete ports, output paths, and an executable pre-commit workflow, fully covering the common cases.

5 / 5

Workflow Clarity

The pre-commit workflow is a clear sequence guarded by `&&` so the commit only runs if checks pass, but explicit error-recovery feedback loops (validate -> fix -> retry) are not spelled out.

4 / 5

Progressive Disclosure

Content is well structured with one-level-deep references to git-workflow.md and mobile-dev-shell.md (both real files), though the body itself is a sizable command catalog that leans toward inline detail.

4 / 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 distinguishable, naming several concrete capability areas in third person. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the 'when to use' dimension only weakly implied.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when running or validating OneKey app builds, or preparing branch/commit/PR changes.'

Include a couple of natural synonyms or file extensions users might say (e.g. 'OneKey app', 'desktop/web/extension/mobile builds') to broaden trigger coverage.

Clarify which platform targets are covered (desktop, web, extension, mobile) so the scope is unmistakable at a glance.

DimensionReasoningScore

Specificity

The phrase 'development commands plus branch, commit, validation, and PR conventions' lists several specific concrete areas rather than vague abstractions, but coverage is not comprehensive enough for a 5.

4 / 5

Completeness

It gives a clear 'what' (OneKey dev commands and conventions) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Natural developer terms like 'branch', 'commit', 'validation', and 'PR' appear and would be said by users, though synonyms and explicit trigger phrasing are missing.

4 / 5

Distinctiveness Conflict Risk

The 'OneKey' qualifier gives it a clear niche distinct from generic git-workflow skills, with only minor overlap risk against a general branch/commit skill.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

Total

15

/

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.