CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-perps-module

Use only for explicit OneKey Perps/Hyperliquid (`views/Perp`, ServiceHyperLiquid, perpetuals, 永续/合约, Perps trading). Covers orderbook/L2/BBO, TWAP, scale/TIF/trigger/reduce-only, Perps TradingView/K-line, Perps Relay deposit, token selector, positions/account state/PnL/funding/margin/liquidation. Exclude generic Swap/Market/TradingView; Swap Relay quote/status/pending/requestId alone is not enough unless Perps deposit/Hyperliquid/`views/Perp`/`usePerpDeposit`/`fetchPerpDeposit*`/`perpsDepositOrderAtom` is explicit.

68

Quality

85%

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

78%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 Perps/Hyperliquid domain router with clean triage sequencing, an owner/proof matrix, and excellent one-level-deep progressive disclosure to real reference files. It is efficient and actionable, with only minor tightening possible in the Hard Stops and validation sections.

Suggestions

Trim overlap between the Hard Stops and the Verify-Against-Source section (e.g., surface-freshness rules appear in both) to improve conciseness.

Consider adding one short inline verification snippet (e.g., an example rg invocation for confirming a Perps surface) to push actionability from strong to copy-paste ready.

Make the validation checkpoints in the 60-Second Triage more explicit (e.g., a labeled 'Validate' step) to lift workflow clarity toward the top anchor.

DimensionReasoningScore

Conciseness

A dense, table-driven router that assumes Claude's competence and avoids explaining what Perps/Hyperliquid are; minor trim opportunities exist in the eight Hard Stops and the Verify-Against-Source block, which slightly overlap.

4 / 5

Actionability

Provides concrete, executable routing—specific owner files, proof paths, `rg` verification, SDK dirs ("node_modules/@nktkas/hyperliquid/src/api/exchange/_methods/"), and a docs URL—with only minor gaps since it offers no inline code snippets (appropriate for a router).

4 / 5

Workflow Clarity

The 60-Second Triage gives a clear sequenced procedure with validation gates ("verify anchors with rg before editing") and Hard Stops plus Verify-Against-Source supply feedback loops for destructive trading operations, so the destructive-op cap does not apply.

4 / 5

Progressive Disclosure

The body is an overview router pointing to ten real, one-level-deep reference files in references/rules/, each clearly signaled in the Quick Reference table with "Start With" guidance for easy navigation.

5 / 5

Total

17

/

20

Passed

Description

92%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 a strong, concrete router trigger that clearly states when to use the skill, what it covers, and where it boundaries against adjacent Swap/Market/TradingView skills. Its only weakness is a heavy reliance on code symbols rather than purely natural user phrasing for triggers.

DimensionReasoningScore

Specificity

Lists many specific concrete capabilities—"orderbook/L2/BBO, TWAP, scale/TIF/trigger/reduce-only, Perps TradingView/K-line, Perps Relay deposit, token selector, positions/account state/PnL/funding/margin/liquidation"—giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both what ("Covers…") and when ("Use only for explicit OneKey Perps/Hyperliquid…") with concrete trigger phrases plus exclusion guidance.

5 / 5

Trigger Term Quality

Good keyword coverage with synonyms across languages ("perpetuals, 永续/合约, Perps trading") and file paths ("views/Perp"), but it leans heavily on code symbols (ServiceHyperLiquid, usePerpDeposit, perpsDepositOrderAtom) over natural user phrasing.

4 / 5

Distinctiveness Conflict Risk

Clear Perps/Hyperliquid niche with explicit conflict avoidance—"Exclude generic Swap/Market/TradingView" and disambiguation of Swap Relay requestId alone—minimizing wrong-skill triggers.

5 / 5

Total

19

/

20

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: 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
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.