CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-architecture

OneKey monorepo architecture, project structure, package relationships, and import hierarchy rules.

51

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 well-structured, navigable reference with concrete package relationships, naming conventions, and a strict import hierarchy backed by an analysis protocol and validation checklist. It is held back by generic framework boilerplate and a lack of executable code or verification commands.

Suggestions

Add at least one concrete executable snippet (e.g. a sample import line per hierarchy tier or a `yarn why` / lint command to detect circular or upward imports).

Trim the generic advice in the 'Code Pattern Recognition Framework' (e.g. 'Read surrounding code and imports', 'Match existing code style') that Claude already knows.

Provide a concrete verification step for the import hierarchy, such as a command or grep pattern to catch upward imports before committing.

DimensionReasoningScore

Conciseness

Mostly efficient bullet structure with no padding of basic concepts, but the 'Deep Analysis & Architecture Consistency Framework' restates generic advice Claude already knows ('Read surrounding code', 'Match existing code style'), keeping it at 'mostly efficient with some unnecessary explanation'.

3 / 5

Actionability

Provides concrete package mappings, naming suffixes, and an explicit import hierarchy with ❌ violation examples, but offers no executable code snippets or commands, leaving the guidance instructive rather than copy-paste ready.

3 / 5

Workflow Clarity

The 'Pre-Modification Analysis Protocol' is a clearly numbered 4-step sequence and the 'Architecture Validation Checklist' supplies explicit checkpoints, fitting 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections in a single self-contained file (~120 lines) with no nested references, matching 'good structure; most content appropriately placed' and the simple-skill guidance.

4 / 5

Total

14

/

20

Passed

Description

53%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 clearly identifies the OneKey monorepo architecture niche and enumerates concrete topics, but it omits any explicit 'Use when...' trigger guidance and reads as topic-focused rather than action-focused.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when modifying OneKey monorepo code, resolving import errors, or adding new packages/apps.'

Frame the description around concrete actions (e.g. 'Navigates', 'Validates imports against') rather than only listing topics.

Include a few natural user phrases or synonyms ('monorepo setup', 'package dependencies', 'import rules') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete facets ('project structure, package relationships, import hierarchy rules') but lists topics rather than concrete actions, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.

3 / 5

Completeness

Has a clear 'what' (the four architectural topics) but no explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains relevant terms ('monorepo architecture', 'package relationships', 'import hierarchy') but leans technical and misses common synonyms or variations users would naturally say.

3 / 5

Distinctiveness Conflict Risk

Scoped specifically to the OneKey monorepo with distinct triggers and minimal overlap risk with other skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

13

/

20

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.