CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-trade-swap-market

App-side OneKey Trade/Swap/Market guide for Swap core, Swap Pro, Wallet Home and Home Token entries, Send/Earn/Market/Buy handoffs, native/mobile host differences, K-line/chart, token selectors, cold-start frame-by-frame validation, quote/build/send flows, history/status, provider channels, PrivateSend-like channels, stock-trading channels, limit/order flows, fees, slippage, ETA, and cross-module funding handoffs.

63

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-trade-swap-market/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 content is a lean, actionable, well-sequenced App-development skill with strong validation checkpoints and a clean reference structure. The main gap is a broken reference to templates/feature-packet.md, which slightly weakens progressive disclosure.

Suggestions

Create templates/feature-packet.md (or fix the path) so the two references to it resolve, restoring a fully one-level-deep reference structure.

Consolidate overlapping guidance between Hard Stops and the Default Workflow to tighten conciseness toward a 5.

Add one or two short copy-paste command/code snippets (e.g. a readiness-check invocation with expected pass/fail output) to push actionability toward 5.

DimensionReasoningScore

Conciseness

The body is dense and signal-heavy with no padding or explanation of basic concepts (e.g. 'Treat Swap as the execution spine below visible surfaces', the ordered triage list), assuming Claude's competence; it is not a 5 because a few Hard Stops overlap with Default Workflow guidance and could be tightened further.

4 / 5

Actionability

It gives concrete executable guidance — the readiness script path ('node .skillshare/skills/1k-trade-swap-market/scripts/check-readiness.mjs'), an 11-step Default Workflow, and an 8-point provider/channel contract — with minor gaps; it is not a 5 because most guidance is process/instruction rather than copy-paste code beyond the single readiness command.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints and feedback loops: the readiness check 'intentionally fails ... do not bypass the failure', the ordered framework/state-machine/hooks triage, and Hard Stops as gates, matching the anchor for explicit validation steps with error-recovery loops.

5 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with a Reference Map table pointing one level deep to real reference files and the readiness script; it is not a 5 because 'templates/feature-packet.md' is referenced twice but the templates/ directory does not exist, so one signaled reference is broken.

4 / 5

Total

17

/

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, distinct, and rich in domain trigger terms, but it omits any explicit 'Use when...' trigger clause, which caps completeness. Adding a concise 'when to use' clause would lift the completeness and trigger-term dimensions.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases (e.g. 'Use when App code touches Swap panels, K-line/chart, token selectors, or funding handoffs into Swap').

Frame a few items as concrete actions rather than only topics (e.g. 'quote, build, send, and validate swap transactions') to push specificity toward 5.

Include common synonyms / surface aliases users actually say to round out trigger-term coverage.

DimensionReasoningScore

Specificity

The description enumerates many concrete surfaces and flows ('Swap core, Swap Pro, Wallet Home and Home Token entries', 'K-line/chart, token selectors', 'quote/build/send flows, history/status, provider channels', 'fees, slippage, ETA'), giving comprehensive topic coverage; it stops short of score 5 because it lists domains/topics the guide covers rather than distinct concrete actions performed.

4 / 5

Completeness

It clearly states what the skill covers ('App-side OneKey Trade/Swap/Market guide for ...'), but provides no 'when' / 'Use when...' trigger clause, and the rubric caps completeness at 3 when explicit trigger guidance is missing.

3 / 5

Trigger Term Quality

It includes natural terms a developer would say ('Trade/Swap/Market', 'Wallet Home', 'Send/Earn/Market/Buy', 'K-line/chart', 'token selectors', 'quote/build/send'), with good keyword coverage; it is not a 5 because some common synonyms and the explicit 'Use when...' phrasing are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific (OneKey App Trade/Swap/Market surfaces, PrivateSend-like and stock-trading channels) with distinct triggers and minimal overlap risk with other skills; it is clearly distinguishable.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

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.