Name: 1k-perps-module
Rating: 64 (1 reviews)
Author: OneKeyHQ

1k-perps-module

OneKey Perps/Hyperliquid development for views/Perp, orders, orderbook, charts, Relay deposits, positions, funding, margin, and liquidation. Excludes generic Swap/Market work.

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-perps-module/SKILL.md

Quality

Content

86%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 an exemplary lean domain router: concrete file/proof targets, a clear triage workflow with verification, and well-structured one-level-deep references. Minor redundancy across routing tables and implicit feedback loops are the only things keeping it from full marks.

Suggestions

Collapse the overlap between Owner Matrix, Quick Reference, and Agent Routing Examples into a single mapping or cross-link them to reduce redundancy.

Make the validate->fix->retry loop explicit in the 60-Second Triage (e.g. 'verify with rg; if mismatch, re-pick owner and re-verify') to lift workflow clarity.

Consider folding the 'Verify Against the Source' bullets into the triage or hard-stops section to avoid a small amount of repeated volatility guidance.

Dimension	Reasoning	Score
Conciseness	The body is dense and table-driven, assumes Claude's competence, and never explains what Perps/Hyperliquid is; however the Owner Matrix, Quick Reference, and Agent Routing Examples tables overlap somewhat on surface-to-reference mappings and could be tightened, so it sits just below the lean/efficient anchor.	4 / 5
Actionability	Highly actionable for an instruction-only router: it names exact owner files (e.g. ServiceHyperliquidExchange.ts), exact reference files to open, exact commands (`rg`), exact SDK paths (node_modules/@nktkas/hyperliquid/src/api/exchange/_methods/), and exact proof methods per surface, with absence of code excused by the instruction-only scoring note.	5 / 5
Workflow Clarity	The '60-Second Triage' gives a clear 4-step sequence with an explicit verify step ('verify anchors with rg before editing') plus a 'Verify Against the Source' section and Hard Stops as checkpoints, but the validate->fix->retry feedback loop is implied rather than spelled out, so it is just below the explicit-feedback-loop anchor.	4 / 5
Progressive Disclosure	SKILL.md is a pure overview/router linking to 10 reference files, all verified to exist and exactly one level deep under references/rules/, with a Quick Reference table and inline markdown links providing easy, well-signaled navigation.	5 / 5
	Total	18 / 20 Passed

Description

70%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 specific and well-scoped to a clear niche with strong natural trigger terms, but it omits an explicit 'Use when...' clause, capping completeness. Adding a concrete when-trigger and a few synonyms would round it out.

Suggestions

Append an explicit trigger clause, e.g. 'Use when working on OneKey Perps/Hyperliquid views, orders, orderbook, charts, Relay deposits, positions, funding, margin, or liquidation.'

Add a couple of natural synonyms a user might say ('perpetual/futures', '永续/合约') to broaden trigger matching.

Replace the generic verb 'development for' with a concrete action phrase like 'edits and reviews ... ' to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the OneKey Perps/Hyperliquid domain and enumerates many concrete surfaces (views/Perp, orders, orderbook, charts, Relay deposits, positions, funding, margin, liquidation), but the single verb 'development for' is generic rather than a set of concrete actions, keeping it just below the comprehensive-action anchor.	4 / 5
Completeness	It clearly states what the skill covers (the enumerated Perps surfaces) but lacks any 'Use when...' trigger clause; the 'Excludes generic Swap/Market work' line is a negative boundary, not an explicit when, so per the rubric cap completeness stays at 3.	3 / 5
Trigger Term Quality	Strong natural keyword coverage ('Perps', 'Hyperliquid', 'orders', 'orderbook', 'positions', 'funding', 'margin', 'liquidation', 'Relay deposits') that users in this domain would actually say, though a few synonyms a user might use ('futures', 'perpetual contracts', the Chinese 永续/合约 that appear only in the body) are absent from the description.	4 / 5
Distinctiveness Conflict Risk	'OneKey Perps/Hyperliquid' is a clear niche and the explicit 'Excludes generic Swap/Market work' boundary actively suppresses the most likely adjacent-skill conflict, giving minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
relative_links	Relative link issues: 13 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 13 deeper-than-1-level	Warning

	Total	13 / 16 Passed

Repository: OneKeyHQ/app-monorepo
Path: .skillshare/skills/1k-perps-module/SKILL.md
Commit: 518bbeb

Reviewed: 4 days 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.