CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-dev-commands

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

63

Quality

75%

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

100%

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

The skill body is a well-organized, actionable command reference with explicit validation checkpoints and a clean one-level reference split for git conventions. It assumes Claude's competence and adds only project-specific operational detail.

DimensionReasoningScore

Conciseness

The body is a lean command catalog providing project-specific runtimes, failure modes, and troubleshooting without explaining concepts Claude already knows (e.g. what Electron, Rspack, or Jest are); nearly every token earns its place.

3 / 3

Actionability

It lists fully executable `yarn ...` commands with outputs and prerequisites, plus a copy-paste pre-commit workflow (`yarn agent:check --profile commit && git commit -m "your message"`), making the guidance directly actionable.

3 / 3

Workflow Clarity

Validation checkpoints are explicit (run `agent:check` before commit, zero-tolerance lint, per-build "Verification" steps) and troubleshooting lines provide error-recovery feedback loops for startup and build failures.

3 / 3

Progressive Disclosure

The body opens with a clearly signaled one-level-deep reference to the real `references/git-workflow.md` for git conventions, while keeping the core command quick-reference inline, giving clear and easy navigation.

3 / 3

Total

12

/

12

Passed

Description

50%

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 clearly identifies a project-specific niche and lists relevant dev-workflow categories, but it lacks concrete action verbs and any explicit trigger guidance for when to invoke it. It is solid but not maximally specific or trigger-complete.

Suggestions

Add concrete action verbs, e.g. "Run OneKey dev/build commands and follow branch, commit, validation, and PR conventions".

Append an explicit trigger clause such as "Use when working in the OneKey repo, running local dev/build commands, or preparing a branch, commit, or PR".

Include natural-term variations users might say (e.g. "OneKey", "yarn", "pre-commit check", "pull request") to improve trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("OneKey development commands") and several categories ("branch, commit, validation, and PR conventions"), but lists convention areas rather than concrete action verbs, so it is not comprehensive of specific actions.

2 / 3

Completeness

It states what the skill covers but provides no explicit "when"/trigger guidance; per the rubric a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like "branch", "commit", and "PR" are natural developer keywords, but common variations are missing and there is no "Use when..." trigger phrasing to broaden coverage.

2 / 3

Distinctiveness Conflict Risk

The "OneKey" qualifier pins it to a specific project niche, but the generic branch/commit/PR workflow terms could still overlap with general git or development skills.

2 / 3

Total

8

/

12

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.