trader-setup

One-time onboarding for the financial trader workflow — real-time alerts, position-aware relevance, decision journaling with outcome tracking. After successful setup this skill is excluded from selection until the marker file is deleted.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/trader-setup/SKILL.md

Quality

Content

67%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 body is highly actionable with concrete, mostly copy-paste-ready setup calls and a clear sequenced workflow, but it suffers from repeated calibration rules across multiple memory_write blocks and defers part of its content to another skill without local validation of write/mission success.

Suggestions

Deduplicate the operating principles (signal expiry, read-positions rule) so they live in one place — e.g. only in calibration.md — and have AGENTS.md reference it, tightening conciseness.

Add an explicit validation step after the memory_write and mission_create calls (e.g. memory_read the created files, confirm missions registered) before writing the completion marker.

Inline or locally summarize the commitment-setup README schema rather than deferring to another skill, so this skill is self-sufficient for Step 2.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete config with little concept over-explanation, but the same rules (4h market-signal expiry, "read positions.md before scoring relevance") are repeated verbatim across the AGENTS.md, calibration.md, and confirmation blocks, so it could be tightened; matches the 3 anchor and not a 4 due to that noticeable repetition.	3 / 5
Actionability	Provides copy-paste-ready memory_write and mission_create calls with specific file paths, content, and cron cadences, matching the 4 anchor of mostly executable guidance; not a 5 because Step 2.2 defers the README body to another skill ("see commitment-setup skill for the complete content") and several placeholders (<today's UTC date>, <slug>) remain.	4 / 5
Workflow Clarity	A clear 6-step sequence with an explicit read-check gate in Step 2.1 and a user-confirmation checkpoint in Step 5 fits the 4 anchor; not a 5 because there is no explicit validation that the memory_writes or mission_create calls succeeded before marking setup complete.	4 / 5
Progressive Disclosure	Well-organized with clear section headers (Steps 1-6) and a companion-skills table that signals which dependent skills activate when, with config blocks appropriately inline; matches the 4 anchor rather than 5 because the skill is over 50 lines and the README content is deferred to another skill rather than split into a local reference.	4 / 5
	Total	15 / 20 Passed

Description

58%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 and distinct, naming concrete trader-oriented capabilities, but it lacks an explicit "Use when..." trigger clause and has only moderate natural-keyword coverage, which cap completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit trigger clause such as "Use when a trader asks to set up their trading workflow, alerts, or position tracking" to lift completeness above 3.

Include natural user phrasings (e.g. "set up my trading workflow", "track my positions", "alert me on market signals") alongside domain terms to improve trigger-term quality.

Add a distinguishing phrase that separates this onboarding skill from the ongoing commitment-tracking skills it depends on.

Dimension	Reasoning	Score
Specificity	Names the trader domain and several concrete capabilities — "real-time alerts", "position-aware relevance", "decision journaling with outcome tracking", "onboarding" — listing multiple specific actions with only minor gaps, matching the 4 anchor; not a 5 because actions like "position-aware relevance" are still somewhat abstract rather than exhaustively enumerated.	4 / 5
Completeness	The "what" is clear (onboarding with alerts, relevance scoring, journaling) but there is no explicit "Use when..." trigger clause — "when" is only weakly implied via "one-time onboarding" — which per the judging guidelines caps completeness at 3; not a 2 because the what is concrete, not a 4 without an explicit when.	3 / 5
Trigger Term Quality	Relevant domain terms ("financial trader workflow", "real-time alerts", "decision journaling") are present but common natural variations and synonyms a user would actually say are missing, fitting the 3 anchor; not a 4 because coverage of natural trigger phrases is thin.	3 / 5
Distinctiveness Conflict Risk	"financial trader workflow" carve out a clear niche with mostly distinct triggers and only minor overlap risk with adjacent finance/commitment skills, matching the 4 anchor; not a 5 because the phrasing could still overlap with general commitment-tracking skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nearai/ironclaw
Path: skills/trader-setup/SKILL.md
Commit: 2831516

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