CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-code-quality

Code quality standards — lint (eslint/oxlint), type check (tsc), pre-commit hooks, and comment conventions. All comments must be in English.

61

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-code-quality/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 tight, highly actionable overview with executable commands and concrete examples, well-supported by clearly signaled one-level references, with only minor redundancy and a feedback loop that could be sequenced more explicitly.

DimensionReasoningScore

Conciseness

Lean and example-driven with no over-explanation of concepts Claude already knows; minor trimming opportunities remain (the pre-commit command is repeated, and the Detailed Guides bullets restate body topics).

4 / 5

Actionability

Fully executable commands (yarn agent:check --profile commit/pr, yarn lint, yarn tsc:only) plus concrete copy-paste-ready fix examples cover the common lint and comment cases.

5 / 5

Workflow Clarity

Clear pre-commit/PR gate with agent:check as the validation checkpoint plus a verification checklist, though the fail→fix→re-run loop is spread across sections rather than sequenced in one place.

4 / 5

Progressive Disclosure

Well-signaled one-level-deep references to real files (code-quality.md, fix-lint.md) each with a content summary; the body inlines some topics also covered in the referenced guide, a minor organization gap.

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 tool-grounded with good natural keywords, but it omits any explicit "Use when..." trigger guidance, leaving the "when" only weakly implied and capping completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when modifying OneKey code, running pre-commit checks, or fixing lint/type errors" to satisfy the "when" half of completeness.

Reframe the capability list with verb-led actions ("Lints, type-checks, and runs pre-commit gates for OneKey code") to lift specificity toward anchor 5.

Include a couple more natural user phrases (e.g. "fix lint warnings", "pass pre-commit") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete areas with specific tool names ("lint (eslint/oxlint)", "type check (tsc)", "pre-commit hooks", "comment conventions"), but they are topic nouns rather than verb-led actions, so they fall short of comprehensive anchor 5.

4 / 5

Completeness

Clearly states the "what" (code quality standards with specific tooling) but has no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural developer keywords (lint, type check, pre-commit hooks, code quality) plus tool-specific terms (eslint/oxlint, tsc) that serve the synonym role, with only a few natural variations missing.

4 / 5

Distinctiveness Conflict Risk

The OneKey-specific tooling framing (eslint/oxlint, tsc, agent:check) gives it a mostly distinct niche, with only minor overlap risk against general coding-patterns 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: 2 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 2 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.