CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-coding-patterns

Coding patterns and best practices — React components, promise handling, and TypeScript conventions.

60

Quality

71%

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-coding-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exemplar of a lean reference skill: concise, fully executable code examples, and a clean overview that offloads detail to real one-level-deep reference files with no padding.

DimensionReasoningScore

Conciseness

The body is lean: a Quick Reference table and tight ❌/✅ code pairs with no explanation of what React, promises, or TypeScript are, assuming Claude's competence and earning every token.

5 / 5

Actionability

Provides copy-paste-ready ❌/✅ code examples covering the common cases (floating promises, FC imports, toLocaleLowerCase, direct hd-core imports) with concrete correct alternatives.

5 / 5

Workflow Clarity

A well-organized lookup reference (topic → guide → key points) with unambiguous single-purpose structure, but it is a catalog rather than a sequenced workflow, so it stops just short of the explicit-checkpoint anchor.

4 / 5

Progressive Disclosure

The body is a clear overview with a table linking to three one-level-deep reference files (promise-handling.md, react-components.md, restricted-patterns.md), all verified to exist, with bulk detail offloaded and inline summaries preserved.

5 / 5

Total

19

/

20

Passed

Description

50%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 concise and names concrete sub-domains, but it omits any "Use when" trigger guidance and leans on the generic phrase "coding patterns and best practices," leaving its activation context and distinctiveness underspecified.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or reviewing OneKey React/TypeScript code involving promises, components, or restricted imports."

Replace the generic "Coding patterns and best practices" lead with concrete verbs (e.g. "Enforces OneKey conventions for...") to sharpen specificity.

Include natural synonyms users would say ("async/await", "floating promises", "React hooks", "import rules") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and three concrete sub-areas ("React components, promise handling, and TypeScript conventions") but leads with the generic umbrella phrase "Coding patterns and best practices," so actions read as topics rather than concrete verbs.

3 / 5

Completeness

Provides a clear "what" (coding patterns and best practices across three areas) but has no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes relevant natural terms ("React components", "promise handling", "TypeScript") but misses common variations and synonyms (e.g. "promises", "async/await", "hooks") and lacks explicit trigger phrasing.

3 / 5

Distinctiveness Conflict Risk

The named sub-areas add some specificity, but "coding patterns and best practices" is broad and the skill shares an ecosystem with many sibling skills (the body lists 8 related skills), creating real overlap risk.

3 / 5

Total

12

/

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: 3 deeper-than-1-level

Warning

referenced_paths_exist

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