Name: 1k-dev-commands
Rating: 60 (1 reviews)
Author: OneKeyHQ

Blog Docs Log inGet started

1k-dev-commands

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-dev-commands/SKILL.md

Quality

Content

86%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 content is a well-structured command reference: fully executable commands with runtimes, outputs, and troubleshooting, a clear pre-commit validation workflow, and clean progressive disclosure to three real one-level-deep reference files. Only minor tightening of vague verification lines and an explicit error-recovery loop in the pre-commit flow would improve it.

Dimension	Reasoning	Score
Conciseness	The body is a dense command/metadata listing ("yarn app:desktop - Start desktop Electron app development with Rspack" plus Runtime/Common issues/Troubleshooting lines) with no explanations of concepts Claude already knows. Minor filler like "Verification: Test installers on target platforms" keeps it at 'efficient; minor instances of over-explanation that could be trimmed' rather than the lean anchor 5.	4 / 5
Actionability	Every command is fully executable and copy-paste ready (e.g. "yarn agent:check --profile commit && git commit -m \"your message\""), with exact output paths ("apps/ext/build/chrome_v3/"), runtimes, and concrete troubleshooting fixes ("Run yarn clean && yarn reinstall if startup fails"). Specific examples cover the common dev, build, and validation cases, matching the top anchor.	5 / 5
Workflow Clarity	There is a clear pre-commit sequence with a validation checkpoint ("yarn agent:check --profile commit" before commit) and per-command troubleshooting recovery hints, plus ordering guidance for mobile ("Read this guide before starting the app"). It falls short of 5 because the pre-commit workflow lacks an explicit fix-and-re-run loop and overall the skill is a reference listing rather than a fully sequenced, checkpointed workflow.	4 / 5
Progressive Disclosure	The body is a concise overview with three well-signaled, one-level-deep references that all exist in the bundle (git-workflow.md, mobile-dev-shell.md, mobile-dependencies.md), each introduced with a clear purpose ("For branch naming, commit format, rebasing, and PR conventions, read git-workflow.md"). Detailed conventions and mobile shell internals are appropriately offloaded, and no reference nests further references.	5 / 5
	Total	18 / 20 Passed

Description

55%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 clear, moderately specific statement of what the skill covers but completely lacks when-to-use trigger guidance, and its keywords miss the natural terms (build, lint, test) for much of the skill's content. The generic git-convention tail also creates overlap risk with general git-workflow skills.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when running or building OneKey apps, running lint/tests, or preparing branches, commits, and PRs in the OneKey repo.'

Include the natural trigger terms for the skill's core commands — build, lint, test, run the desktop/web/mobile apps, yarn — so users' phrasing matches the description.

Qualify the git conventions as OneKey-specific (e.g. 'OneKey's branch, commit, validation, and PR conventions') to reduce overlap with generic git-workflow skills.

Dimension	Reasoning	Score
Specificity	"development commands plus branch, commit, validation, and PR conventions" lists several specific action areas, matching the 'lists several specific actions; minor gaps' anchor. It falls short of 5 because these are category labels rather than the concrete commands (build, lint, test, mobile dev) the skill actually covers.	4 / 5
Completeness	The 'what' is clearly stated (OneKey development commands plus conventions), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete, and not 4 because 'when' is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	"branch", "commit", and "PR" are natural user terms, but the description omits the common variations users would say for the skill's core content (build, lint, test, run the app, yarn). This fits 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor 4.	3 / 5
Distinctiveness Conflict Risk	"OneKey development commands" anchors the skill to a specific project, but "branch, commit, validation, and PR conventions" is generic territory that would overlap with any general git-workflow skill. This fits 'somewhat specific but could still overlap with similar skills' rather than the mostly-distinct anchor 4.	3 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: OneKeyHQ/app-monorepo
Path: .skillshare/skills/1k-dev-commands/SKILL.md
Commit: 356c24e

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.