us-etf-flow

US ETF fund flow analysis, sector rotation breadth, and style factor flows — track institutional capital movement via ETF creation/redemption, sector breadth signals, and thematic momentum.

Quality

66%

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 ./agent/src/skills/us-etf-flow/SKILL.md

Quality

Content

50%

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

A thorough, well-organized reference framework for US ETF flow analysis with concrete code and detailed tables. It is held back by explanatory padding, code examples with undefined placeholders, an implicit rather than explicit workflow, and a monolithic structure that could be split across reference files.

Suggestions

Trim concept explanations Claude already knows (creation/redemption mechanics, price-vs-flow distinction) to tighten conciseness.

Make code examples fully executable by defining the placeholder inputs (spy_flow, daily_flows, aum) or wrapping them in runnable functions.

Move the large ETF reference tables (broad market, sector, style, fixed income, thematic) into separate reference files and keep SKILL.md as a concise overview with clearly signaled links.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material, but spends tokens explaining concepts Claude already knows (creation/redemption mechanics, 'ETF price movement ≠ ETF flow') and could be tightened. It is not a verbose score-1 explainer, but not lean enough for 3.	2 / 3
Actionability	Provides concrete code blocks and tables, but several examples rely on undefined variables (spy_flow, iwm_flow, daily_flows, aum) so they are illustrative rather than copy-paste ready, matching the incomplete score-2 anchor.	2 / 3
Workflow Clarity	The Output Format template and section ordering imply a sequence (broad market → sector → style → fixed income → thematic → composite), but no explicit step list or validation checkpoints are given; the analytical context makes a score-1 too harsh but keeps it at 2.	2 / 3
Progressive Disclosure	Sections are well organized, but the ~270-line body is monolithic with large ETF reference tables inlined that would benefit from being split into separate reference files; no external references are used, so it does not reach the well-signaled one-level-deep score-3 anchor.	2 / 3
	Total	8 / 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.

A specific, distinctive description that names multiple concrete actions and uses natural domain trigger terms. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the 'when to use' guidance only implied.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when analyzing US ETF fund flows, sector rotation, or institutional capital positioning.'

Soften the most technical phrasing (e.g. 'creation/redemption', 'style factor flows') with a plainer user-facing term or two to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'fund flow analysis, sector rotation breadth, and style factor flows' and 'track institutional capital movement' — matching the multi-action anchor rather than the single-domain score-2 anchor.	3 / 3
Completeness	The 'what' is clearly stated but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Natural domain terms a user would actually say ('US ETF fund flow', 'sector rotation', 'style factor flows') are well covered, despite some technical phrasing like 'creation/redemption'.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (US ETF flow and sector breadth analysis) with distinct triggers, making conflicts with other skills unlikely.	3 / 3
	Total	11 / 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: HKUDS/Vibe-Trading
Path: agent/src/skills/us-etf-flow/SKILL.md
Commit: 8643fcd

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.