CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-tradingview-communication

OneKey TradingView bridge communication for WebView/iframe messages, K-line data, marks, Perps symbols/lines, order events, and websocket recovery.

73

Quality

91%

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

100%

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 high-quality knowledge skill: lean, assumes Claude's competence, and packed with actionable repo-specific detail (grep anchors, exact message contracts, verification commands). Its only soft spot is that the verification feedback loop is implied rather than explicitly written as fix-and-revalidate.

DimensionReasoningScore

Conciseness

The body is dense with unique repo-specific knowledge (symbol anchors, message shapes, URL params) and never explains concepts Claude already knows (TradingView, websockets, K-line); its length reflects genuine bridge complexity rather than padding, so every token earns its place.

3 / 3

Actionability

It gives directly usable guidance throughout — `rg` search anchors with real symbol names, copy-paste-ready TypeScript message-contract blocks, concrete URL parameter lists, and exact verification commands (e.g. `yarn agent:check --profile commit`, `npm run build`, `localhost:5173` / `10.0.2.2:5173`).

3 / 3

Workflow Clarity

The 9-step Change Checklist sequences the multi-step message-change process and the Verification section supplies explicit validation checkpoints for both repos; the fix-and-revalidate loop is implied rather than spelled out, but explicit checkpoints plus a checklist meet the 3 bar.

3 / 3

Progressive Disclosure

Content is organized into clear, navigable sections (Mental Model, Search Anchors, URL Parameters, Message Contracts, Change Checklist, Verification) with no nested references and no wall of text; for a single-purpose cohesive ~196-line knowledge skill, the self-contained single-file structure is appropriate.

3 / 3

Total

12

/

12

Passed

Description

82%

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 concrete, distinctive, and rich in natural domain trigger terms, but it omits an explicit "Use when..." trigger clause, leaving the invocation condition implied rather than stated. Adding a when-to-use clause would raise completeness from 2 to 3.

Suggestions

Append an explicit "Use when..." clause, e.g. "Use when adding or debugging messages between the OneKey app and the TradingView chart (K-line, marks, Perps lines, symbol sync, websocket recovery)."

Mention "Hyperliquid" and "chart" in the description to broaden trigger coverage, since Hyperliquid candles and the chart repo are central to the skill.

Lead with the action the skill performs (e.g. "Documents and locates the OneKey TradingView bridge...") so the description reads as concrete actions rather than a noun list.

DimensionReasoningScore

Specificity

Enumerates six concrete capability domains — "WebView/iframe messages, K-line data, marks, Perps symbols/lines, order events, and websocket recovery" — which is concrete and comprehensive rather than vague, matching the "lists multiple specific concrete" anchor even though the phrasing is verb-light.

3 / 3

Completeness

Clearly states what ("OneKey TradingView bridge communication for ...") but provides no "Use when..." clause or equivalent explicit trigger guidance, so the "when" is only implied and completeness is capped at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Uses the natural domain vocabulary the target users actually say — "TradingView", "K-line", "marks", "Perps", "websocket", "WebView/iframe", "order events" — giving good trigger coverage; only "Hyperliquid"/"chart" are absent.

3 / 3

Distinctiveness Conflict Risk

The pairing of "OneKey TradingView bridge" with these specific message types is a clear, narrow niche that is very unlikely to trigger for or conflict with other skills.

3 / 3

Total

11

/

12

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

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.