CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

A concept-rich reference with concrete signal-construction code and a strong output template, but it reads more as an encyclopedic body than an actionable skill: mechanics are over-explained, there is no explicit analysis workflow with validation steps, and all reference material is inlined in a single long file.

Suggestions

Move the ETF category tables, thematic ETF lists, and flow-data source listings into a references/ file and keep SKILL.md as a lean overview with one-level-deep pointers.

Replace the conceptual Creation/Redemption explanation with only the non-obvious interpretation rules, and add an explicit numbered workflow (fetch data → compute breadth/C-D ratio → classify signal → render output) with a validation step for missing or stale flow data.

Make etf_flow_signal self-contained by showing how daily_flows and aum are obtained, and note the 5-day vs 15-day window scale mismatch in the momentum calculation.

DimensionReasoningScore

Conciseness

The Creation/Redemption mechanics section re-explains AP basket mechanics Claude already knows, and tables state basics like 'XLK | Technology', while the signal-threshold code and data-source table are genuinely additive — mostly efficient but with trimmable explanation across several sections, fitting the 3 anchor better than 4.

3 / 5

Actionability

Provides executable snippets (yahoo_download('SPY', ...)), complete breadth and cyclical/defensive ratio computations, and a copy-paste output template; however, etf_flow_signal depends on undefined daily_flows/aum structures and the flow-data section concedes flows require web sources it never scripts, leaving minor gaps below the 5 anchor.

4 / 5

Workflow Clarity

Sections imply a data → signals → output sequence but no explicit numbered workflow or validation checkpoints (e.g., sanity-checking flows against volume or handling missing flow data) — the sequence is implicit, matching the 3 anchor rather than 4.

3 / 5

Progressive Disclosure

There are no bundle files at all and the ~270-line body inlines large ETF, thematic, and data-source reference tables that belong in separate reference files; headers are well-organized, but content that should be separate is inline, matching the 3 anchor.

3 / 5

Total

13

/

20

Passed

Description

66%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.

A specific, well-scoped description in third person that names concrete analytical capabilities with good trigger vocabulary. Its main weakness is the absence of any explicit 'when to use' guidance, which caps completeness and leaves triggering to inference.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks about ETF flows, fund flows, sector rotation, or institutional positioning' to raise completeness.

Include a few more natural synonyms users would say (e.g., 'capital flows', 'money moving into ETFs') to broaden trigger coverage.

Tighten the redundant pairing of 'fund flow analysis' and 'track institutional capital movement' into distinct, complementary capability statements.

DimensionReasoningScore

Specificity

Lists several concrete third-person actions — 'US ETF fund flow analysis, sector rotation breadth, and style factor flows' and 'track institutional capital movement via ETF creation/redemption' — but some phrasing is near-synonymous ('flow analysis' / 'track capital movement'), falling just short of the comprehensive 5 anchor.

4 / 5

Completeness

The 'what' is clearly stated (flow analysis, breadth, factor flows) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural user terms like 'ETF', 'fund flow', 'sector rotation', 'breadth', and 'style factor', but misses common variations such as 'capital flows' or 'money moving into ETFs', matching the good-but-not-comprehensive 4 anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — 'US ETF fund flow', 'creation/redemption', 'sector breadth signals' — with only minor overlap risk against adjacent general market-analysis skills, so it fits the 4 rather than the 5 anchor.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.