CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-coding-patterns

OneKey coding patterns for TypeScript, React, promises, date formatting, and error handling.

58

Quality

68%

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

87%

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-structured, token-efficient overview with concrete executable code examples and correctly-resolving one-level-deep references. Its only gap is the absence of any workflow sequence or validation checkpoint, which is acceptable for a reference catalog but caps workflow clarity at the midpoint.

Suggestions

Resolve the duplicate bundle files: date-formatting.md and error-handling.md exist under both references/ and references/rules/ — consolidate to one location and update the table links to avoid divergence.

Add a brief "How to use this skill" line stating the workflow (consult the quick-reference table, apply the ✅ pattern, avoid the ❌ pattern) to give the catalog an explicit sequence.

Consider adding a one-line validation cue for the restricted patterns (e.g. "grep for toLocaleLowerCase / hd-core imports before submitting") so the forbidden-pattern checks have an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is lean: a quick-reference table and terse ❌/✅ code blocks with no padding or explanation of concepts Claude already knows, matching the "lean and efficient; every token earns its place" anchor.

3 / 3

Actionability

Each rule pair gives concrete, executable TypeScript snippets (e.g. `await apiCall()` vs `apiCall()`, `string.toLowerCase()` vs `toLocaleLowerCase()`) that are copy-paste ready, matching the fully-executable anchor.

3 / 3

Workflow Clarity

The content is a catalog of independent rules with clear per-rule guidance but no multi-step sequence or validation checkpoints; there is no workflow to sequence, so it sits at the midpoint rather than the explicit-checkpoint anchor.

2 / 3

Progressive Disclosure

The SKILL.md is a concise overview whose quick-reference table links to one-level-deep reference files, all of which resolve to real files in references/ and references/rules/, matching the clear-overview-with-well-signaled-references anchor.

3 / 3

Total

11

/

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 is concise and third-person with a clear OneKey-scoped domain, but it lists topics rather than concrete actions and omits any explicit "Use when..." trigger guidance. This places it solidly at the midpoint across all four dimensions.

Suggestions

Rewrite the description to lead with concrete actions, e.g. "Apply OneKey coding patterns for promise handling, React components, date formatting, and error handling in TypeScript."

Add an explicit trigger clause such as "Use when writing or reviewing OneKey TypeScript/React code, especially around promises, dates, or error boundaries."

Include natural user phrasings (e.g. "floating promises", "OneKey dateUtils", "hd-core imports") to improve trigger-term coverage and reduce overlap with sibling 1k-* skills.

DimensionReasoningScore

Specificity

The description names a clear domain and five specific topic areas ("TypeScript, React, promises, date formatting, and error handling") but uses the generic phrase "coding patterns for" rather than listing concrete actions, so it matches the anchor that names domain and some actions without being comprehensive.

2 / 3

Completeness

It answers *what* the skill covers (OneKey coding patterns across listed topics) but provides no "Use when..." clause or equivalent trigger guidance, so per the rubric guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Terms like "TypeScript", "React", and "promises" are relevant keywords a developer might say, but coverage lacks common variations and there is no explicit trigger phrasing, fitting the "some relevant keywords but missing common variations" anchor.

2 / 3

Distinctiveness Conflict Risk

The "OneKey" qualifier gives it a distinct niche, but the broad topics (TypeScript, React, promises) overlap with the sibling 1k-* skills listed in the body, matching the "somewhat specific but could still overlap" anchor.

2 / 3

Total

8

/

12

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.