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

55%

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

65%

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 complete executable memory_write/mission_create blocks and a clear step sequence, but it is held back by repeated principle text across sections, missing write/creation verification on batch operations, and an external reference to commitment-setup content not present in the bundle.

Suggestions

De-duplicate the operating principles: state them once in AGENTS.md and have missions/calibration.md reference that source instead of restating them verbatim.

Add verification checkpoints after batch operations (e.g., memory_read back the written files, confirm each mission_create succeeded) with a fix-and-retry loop.

Either inline the commitment-setup README schema content or ship it as a bundled reference file so the skill is self-contained rather than depending on an external skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude already knows, but the operating principles are repeated nearly verbatim across the AGENTS.md content, the triage mission goal, and calibration.md, so it could be tightened rather than earning the every-token-earns-its-place level 3.	2 / 3
Actionability	It provides complete, copy-paste-ready memory_write and mission_create blocks with full content and cadences, matching the fully-executable anchor rather than the pseudocode level 2.	3 / 3
Workflow Clarity	Steps are clearly sequenced (1–6) with some checkpoints (read-before-write README check, companion-skill-missing check, user confirmation before marking complete), but batch file/mission creation has no post-write verification or error-recovery loop, which per the guidelines caps batch-operation workflows at 2.	2 / 3
Progressive Disclosure	No bundle reference files exist (references/, scripts/, assets/ are absent) and the body inlines long mission goals and calibration content while pointing to an external commitment-setup skill for the README schema, so structure is present but content that could be split is inline and the key reference is external rather than one-level-deep in the bundle.	2 / 3
	Total	9 / 12 Passed

Description

45%

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 third-person about what the skill does, but omits any "Use when..." trigger guidance and natural user keywords, leaving the when-to-activate question only implied. It is distinguishable but not maximally distinct from sibling commitment skills.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers a trader would say (e.g., 'Use when a trader asks to set up their trading workflow, position tracking, or trade journaling').

Include concrete trigger phrases users naturally utter ('track my trades', 'set up my trading workflow') so the description itself surfaces activation terms, not just frontmatter keywords.

Clarify what distinguishes this from the sibling commitment-setup skill to reduce overlap/conflict risk.

Dimension	Reasoning	Score
Specificity	Names multiple concrete capabilities — "real-time alerts", "position-aware relevance", "decision journaling with outcome tracking" — and uses third person, so it clears the multiple-specific-actions bar rather than the domain-only level 2.	3 / 3
Completeness	It clearly answers "what" (trader onboarding with alerts/journaling) but provides no "Use when..." clause or explicit when-to-activate guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	The description contains no natural user-facing trigger terms; it leans on jargon ("onboarding", "marker file", "excluded from selection") rather than phrases a trader would actually say, matching the no-natural-keywords anchor.	1 / 3
Distinctiveness Conflict Risk	The financial-trader niche is identifiable, but without explicit triggers and given the referenced sibling commitment-setup skill, it could still overlap with related commitment skills rather than occupying a fully distinct niche.	2 / 3
	Total	8 / 12 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: 800b781

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