CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-feature-guides

Feature development guides for OneKey. Use when adding new chains, socket events, notifications, pages, or routes. Covers blockchain integration, WebSocket subscriptions, push notifications, and navigation patterns.

74

Quality

93%

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

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.

A well-organized, actionable, and token-efficient overview that delegates detail to real reference files. Its main weakness is workflow clarity: the step lists lack explicit validation checkpoints and feedback loops for the riskier operations (chain integration, route changes).

Suggestions

Add an explicit validation checkpoint to the 'Adding New Chains' workflow, e.g. after step 4: 'Run the chain tests; only proceed to UI wiring when they pass.'

For 'Pages & Routes', add a verify step such as 'Confirm the new route path is unique across packages/kit/src/routes/ before navigating' to turn the ⚠️ warnings into a checkable feedback loop.

For socket events, add a short error-recovery note (e.g. what to do if `ackNotificationMessage` fails) so the handler includes a feedback path rather than only the happy path.

DimensionReasoningScore

Conciseness

The body is lean — exact package paths, short numbered step lists, and a minimal code snippet — with no explanation of concepts Claude already knows; the only mild redundancy is the Quick Reference table echoing each section's guide link, but every token largely earns its place.

3 / 3

Actionability

Provides concrete executable guidance: real file paths (e.g. `packages/core/src/chains/mychain/`), a specific enum (`EAppSocketEventNames`), a complete TypeScript socket-handler snippet, and a notification-mode action table — copy-paste ready rather than abstract.

3 / 3

Workflow Clarity

Multi-step processes are sequenced (numbered 'Key steps' for chains and socket events) and include guardrail warnings, but there are no explicit validate-then-proceed checkpoints or error-recovery feedback loops; checkpoints are implicit rather than stated.

2 / 3

Progressive Disclosure

SKILL.md is a clear overview that splits detail into four one-level-deep, well-signaled reference files under references/rules/ (all verified to exist), with a Quick Reference table providing easy navigation.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly states what the skill covers and when to invoke it using natural trigger terms. It is concise, uses third person, and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'adding new chains, socket events, notifications, pages, or routes' plus 'blockchain integration, WebSocket subscriptions, push notifications, and navigation patterns' — matching the anchor for several specific concrete actions.

3 / 3

Completeness

Explicitly answers both 'what' ('Feature development guides for OneKey ... Covers blockchain integration ...') and 'when' ('Use when adding new chains, socket events, notifications, pages, or routes'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

'Use when adding new chains, socket events, notifications, pages, or routes' are natural terms a OneKey developer would actually say, giving good coverage of common variations rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to OneKey feature development with distinct triggers (chains, socket events, notifications, pages, routes), making it unlikely to fire for the sibling coding-patterns or architecture skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 12 deeper-than-1-level

Warning

Total

14

/

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.