CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

1k-trade-swap-market

Implement and debug OneKey Swap, Bridge, Limit, and Stock/Market trades, including quotes, review, execution, fees, and history. Excludes Perps and chart communication.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A well-structured, token-efficient overview that routes precisely to real, one-level-deep references and defines clear ownership boundaries and handoff evidence requirements. The only gaps are implicit mid-workflow validation and the absence of inline concrete identifiers, both appropriately deferred to the reference files.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and entirely project-specific decision guidance ("Trace the affected path", "Compare the actual payload and state before adding a new effect"); it assumes Claude's competence and contains no padding or explanations of known concepts.

5 / 5

Actionability

Concrete artifacts are present — the trace pipeline "selection -> quote -> review -> build/sign/send -> history/settlement", a question-to-reference routing table, explicit ownership rules, and defined handoff deliverables — but no concrete payload, status-field, or file-path identifiers appear inline (specifics are delegated to the reference files), leaving minor gaps.

4 / 5

Workflow Clarity

A clear sequence runs from tracing the entry, to locating the first incorrect transition, to consulting the right reference, to the Handoff section's verification requirements ("Separate tests, real platform interaction, and provider/signing proof"); however, mid-process validation checkpoints are implicit rather than an explicit validate-fix-retry loop.

4 / 5

Progressive Disclosure

The body is a concise overview with a question-keyed table pointing to three one-level-deep reference files; all three referenced paths (app-architecture.md, provider-contracts.md, validation.md) exist in references/, their contents match the table's descriptions, and they contain no nested links — navigation is easy and content is appropriately split.

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.

A distinct, specific description with good natural trigger terms and clear exclusions, but it omits any "Use when..." trigger clause, leaving the activation guidance implicit. Adding an explicit when-to-use sentence with a few more synonyms would raise completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g., "Use when implementing, debugging, or reviewing Swap, Bridge, Limit, or Stock/Market trade flows — quotes, confirmation, execution, fees, or history."

Include a few more natural synonyms users would say, such as "cross-chain" or "bridge transfer" for Bridge and "limit order" for Limit.

State the activation context explicitly (trade/transaction work in the OneKey app) so the 'when' is not merely implied by the product name.

DimensionReasoningScore

Specificity

"Implement and debug" names two concrete actions plus an enumerated scope ("quotes, review, execution, fees, and history") across named trade types — several specific capabilities with minor gaps, matching anchor 4 rather than 5 since the enumerated items are lifecycle stages more than distinct actions.

4 / 5

Completeness

The "what" is clear ("Implement and debug OneKey Swap, Bridge, Limit, and Stock/Market trades..."), but there is no "Use when..." clause or equivalent explicit trigger guidance; the exclusion sentence ("Excludes Perps and chart communication") bounds scope without stating when to use the skill, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural terms users would say are present — "Swap", "Bridge", "Limit", "Stock/Market trades", "quotes", "fees", "Perps" — giving good keyword coverage, though a few common synonyms (e.g., "cross-chain", "spot", "order") are missing.

4 / 5

Distinctiveness Conflict Risk

A clear product-specific niche ("OneKey Swap, Bridge, Limit, and Stock/Market trades") with explicit exclusions ("Excludes Perps and chart communication") gives distinct triggers and minimal conflict risk with adjacent skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

OneKeyHQ/app-monorepo

Path

.skillshare/skills/1k-trade-swap-market/SKILL.md

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.