Name: 1k-feature-guides
Rating: 64.8 (1 reviews)
Author: OneKeyHQ

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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-feature-guides/SKILL.md

Quality

Content

72%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 overview that defers detail to four real reference files with clear navigation and an executable code example. Its main weakness is the absence of validation/verification checkpoints in the multi-step and destructive-operation workflows.

Suggestions

Add explicit validation steps to the chain and socket workflows (e.g., 'Verify the new chain appears in the chain list' or 'Confirm the event is acknowledged before handling'), since these are batch/multi-step operations.

Add a verification checkpoint to the pages section's destructive guidance (e.g., 'Check route uniqueness before adding a new route') rather than only warning after the fact.

Remove the redundant per-section 'See:' links that duplicate the Quick Reference table, or drop the table, to tighten the token budget.

Dimension	Reasoning	Score
Conciseness	The body is efficient, uses tables and a copy-paste TypeScript example, and assumes Claude's competence without explaining concepts; minor trims possible in the throwaway intro line and the per-section 'See:' links that duplicate the Quick Reference table.	4 / 5
Actionability	Provides concrete file paths, a real executable socket-event code example, and mode/type tables; the chain 'Key steps' are outlines rather than executable commands, but the reference files fill the gaps, leaving only minor gaps.	4 / 5
Workflow Clarity	Chain and socket steps are sequenced, but there are no validation or verification checkpoints, and the pages section involves destructive operations ('Never delete pages', 'Route paths must be unique') without a verify step, capping this dimension at 3.	3 / 5
Progressive Disclosure	All four bundle files in references/rules/ are referenced via a Quick Reference table and per-section links, one level deep, clearly signaled, with detail appropriately split into the reference files for easy navigation.	5 / 5
	Total	16 / 20 Passed

Description

83%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 strong: it clearly states the skill's purpose and provides explicit 'Use when' triggers covering four concrete feature areas. Minor improvements would replace the generic verb 'guides' with a more specific action and add synonyms to reduce overlap with related skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete feature additions ('adding new chains, socket events, notifications, pages, or routes') and coverage areas ('blockchain integration, WebSocket subscriptions, push notifications, and navigation patterns'), but the governing verb 'guides' is generic rather than a Claude-performed action, leaving minor gaps.	4 / 5
Completeness	Explicitly answers both what ('Feature development guides for OneKey') and when with concrete triggers ('Use when adding new chains, socket events, notifications, pages, or routes').	5 / 5
Trigger Term Quality	Includes natural trigger phrases a OneKey developer would say ('adding new chains', 'socket events', 'notifications', 'pages, or routes'), with good coverage though a few synonyms (e.g. 'add a blockchain' vs 'chain') are absent.	4 / 5
Distinctiveness Conflict Risk	Tied to OneKey-specific feature additions with distinct triggers, but terms like 'navigation patterns' overlap with the listed related skills (1k-coding-patterns, 1k-architecture), creating minor conflict risk.	4 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: .skillshare/skills/1k-feature-guides/SKILL.md
Commit: 3cff1b4

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

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.