ai-trader-tradesync

Sync your trading positions and trade records to AI-Trader copy trading platform.

Quality

27%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/tradesync/SKILL.md

Quality

Discovery

40%

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 identifies a clear niche (syncing to a specific copy trading platform) which makes it distinctive, but it lacks explicit trigger guidance ('Use when...') and could benefit from more specific capability details and natural keyword variations. The description is too brief to fully inform Claude when to select this skill over others.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to sync, export, or push their trading positions or trade history to the AI-Trader copy trading platform.'

Include natural keyword variations users might say, such as 'portfolio sync', 'mirror trades', 'copy trades', 'position export', or 'trade history upload'.

Expand the 'what' portion with more concrete actions, e.g., 'Syncs open positions, closed trades, and trade records to the AI-Trader copy trading platform, supporting real-time position updates and historical trade uploads.'

Dimension	Reasoning	Score
Specificity	Names the domain (trading) and two actions (sync positions, sync trade records), but doesn't elaborate on specific capabilities like what formats are supported, what APIs are used, or what the sync process entails.	2 / 3
Completeness	Describes what it does (sync positions and trade records) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also fairly thin, placing this at 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'trading positions', 'trade records', 'copy trading', and the platform name 'AI-Trader', but misses common variations users might say such as 'portfolio sync', 'mirror trades', 'copy trades', or 'position tracking'.	2 / 3
Distinctiveness Conflict Risk	The specific platform name 'AI-Trader copy trading platform' and the narrow domain of syncing trading positions make this highly distinctive and unlikely to conflict with other skills.	3 / 3
	Total	8 / 12 Passed

Implementation

14%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a marketing-oriented API documentation page than an actionable skill for Claude. It lacks a clear sequential workflow, mixes promotional content (fees, incentives, best practices) with technical instructions, and is verbose with information Claude doesn't need. Critical operational details like authentication flow and error handling are missing while non-essential content like incentive points and fee tables consume tokens.

Suggestions

Add a clear numbered workflow: 1) Register and obtain token, 2) Configure authentication header, 3) Sync positions with validation of API response, 4) Handle errors and retry. Include explicit validation checkpoints.

Remove promotional/marketing content (fees, incentive system, best practices) that doesn't help Claude execute the task, or move it to a separate reference file.

Standardize all API examples with consistent authentication headers and full base URLs, and show error response handling for each endpoint.

Split the content: keep SKILL.md as a concise quick-start with the core sync workflow, and move API reference details, subscriber management, and price queries into separate referenced files.

Dimension	Reasoning	Score
Conciseness	Significant verbosity throughout. The 'Auto Installation' section with a Python example that just prints content is unnecessary filler. Feature bullet lists, best practices, fee tables, and incentive system details are padding that Claude doesn't need to execute the task. Multiple redundant tables describe signal types and frequencies without adding actionable value.	1 / 3
Actionability	API endpoints are shown with concrete request/response examples, which is good. However, critical details are missing: authentication headers are inconsistently shown (only on the price query), base URL is sometimes included and sometimes not, and the self-registration flow doesn't show how to obtain/use the token from the response. The 'auto-install' code is not genuinely executable.	2 / 3
Workflow Clarity	There is no clear end-to-end workflow sequence. Steps like register → authenticate → sync positions → verify are not laid out in order. There are no validation checkpoints (e.g., verify registration succeeded before syncing, check API response for errors). For a multi-step integration involving API calls and real-time sync, this lack of sequencing and error handling is a significant gap.	1 / 3
Progressive Disclosure	All content is in a single monolithic file with no bundle files. The document mixes installation, API reference, pricing info, fee structures, and incentive systems all inline. API reference details, subscriber management, and incentive/fee information should be in separate referenced files. External links at the bottom are mentioned but the body doesn't organize around them.	1 / 3
	Total	5 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: HKUDS/AI-Trader
Commit: dcdccb2

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