CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-trader-tradesync

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

36

Quality

31%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/tradesync/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%

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 product marketing page and API overview than an actionable skill for Claude. It lacks a clear end-to-end workflow, omits critical details like authentication token usage across requests, and includes unnecessary promotional content (fees, incentives, best practices). The API examples provide some concrete guidance but are disconnected from a coherent operational sequence.

Suggestions

Remove promotional content (fees, incentive system, best practices) and focus on a clear sequential workflow: register → get token → authenticate → sync positions/trades, with explicit validation at each step.

Add authentication details to every API example (show the X-Claw-Token header consistently) and include error response examples with recovery guidance.

Replace the 'auto-install' pseudocode with either a real executable installation script or remove it entirely—the current example fetches a URL and prints it, which isn't actionable.

Consolidate the three installation/setup paths into one recommended approach with a complete working example from registration to first successful signal sync.

DimensionReasoningScore

Conciseness

The skill is verbose with unnecessary sections like explaining what each feature does in a bullet list, best practices that are generic advice Claude already knows, fee tables, incentive system details, and multiple installation methods including a vague 'auto-install' example that doesn't actually do anything useful. Much of this content is marketing/promotional rather than actionable instruction.

1 / 3

Actionability

API endpoints are shown with concrete request/response examples, which is helpful. However, the installation 'auto-install' code is essentially pseudocode that doesn't actually install anything, the self-registration endpoint lacks response format and token retrieval details, and there's no complete workflow showing how to authenticate and then make API calls end-to-end. Key details like how to obtain and use the auth token are missing from most examples.

2 / 3

Workflow Clarity

There is no clear sequenced workflow for the multi-step process of registering, authenticating, and syncing trades. The skill jumps between installation methods, registration, API reference, and best practices without a coherent sequence. No validation checkpoints exist—there's no guidance on error handling, verifying successful sync, or what to do when API calls fail.

1 / 3

Progressive Disclosure

The content has some structure with headers and sections, and links to external docs/console at the end. However, there are no bundle files to offload detailed content to, and the skill includes inline content that could be separated (fee tables, incentive system, subscriber management) while lacking depth where it matters (authentication flow, error handling).

2 / 3

Total

6

/

12

Passed

Description

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 (AI-Trader copy trading platform) which makes it distinctive, but it lacks explicit trigger guidance ('Use when...') and could benefit from more specific action verbs and natural user keywords. 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, push, or export trading positions or trade history to the AI-Trader copy trading platform.'

Include more natural trigger terms users might say, such as 'copy trades', 'mirror trading', 'portfolio sync', 'export positions', or 'trade history'.

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 exports.'

DimensionReasoningScore

Specificity

Names the domain (trading/copy trading) and some actions (sync positions, trade records), but doesn't list comprehensive specific actions like creating, updating, deleting, or managing specific trade types.

2 / 3

Completeness

Describes what it does (sync trading 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, bringing it to 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'trading positions', 'trade records', 'copy trading', and 'AI-Trader', but misses common variations users might say such as 'portfolio sync', 'mirror trades', 'copy trades', or 'position management'.

2 / 3

Distinctiveness Conflict Risk

The mention of 'AI-Trader copy trading platform' is a very specific niche product reference, making it highly unlikely to conflict with other skills. The combination of syncing + trading + a named platform creates a clear, distinct trigger.

3 / 3

Total

8

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
HKUDS/AI-Trader
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.