CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

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

65%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 dense, actionable reference skill with executable code and useful lookup tables, but it is monolithic (no progressive disclosure into bundle files) and lacks an explicit sequenced workflow with validation checkpoints.

Suggestions

Split the large ETF ticker/categorization tables and the data-source table into reference files (e.g. references/etf_catalog.md) and link to them from SKILL.md to improve progressive disclosure.

Add an explicit numbered analysis workflow (pull data → compute breadth & C/D ratio → classify signals → assemble output) with a validation/sanity-check step before producing the report.

Tighten concept explanations (e.g. creation/redemption mechanics) to assume more domain competence and reduce token cost.

DimensionReasoningScore

Conciseness

Mostly lean reference material (ticker tables, AUM figures, cycle-phase mappings, data-source latency) that earns its tokens; only minor stretches of concept explanation could be trimmed, so it sits just below the top anchor.

4 / 5

Actionability

Provides executable Python (yfinance download, sector breadth, cyclical/defensive ratio, an etf_flow_signal function) plus a concrete output template and data-source table, with only minor gaps (e.g. undefined daily_flows/aum variables in the signal snippet).

4 / 5

Workflow Clarity

The body is organized as concepts plus an output template rather than an explicit step sequence, and there are no validation/checkpoint steps; the implicit workflow is present but checkpoints are missing.

3 / 5

Progressive Disclosure

Well-sectioned single file with no bundle files or external references; sizable reference tables (tickers, flow sources) that could live in separate files are inlined, leaving structure good but separation incomplete.

3 / 5

Total

14

/

20

Passed

Description

75%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 with strong capability listing and low conflict risk, but it omits an explicit 'Use when...' trigger clause, capping completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about ETF flows, sector rotation, institutional capital movement, or fund-flow breadth signals.'

Include a few more natural synonyms users might say (e.g. 'fund flows', 'ETF inflows/outflows', 'creation/redemption activity') to lift trigger term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'fund flow analysis, sector rotation breadth, and style factor flows' plus 'track institutional capital movement via ETF creation/redemption, sector breadth signals, and thematic momentum' — giving comprehensive, specific action coverage.

5 / 5

Completeness

The 'what' is clearly stated but there is no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Strong natural keywords a finance user would say ('ETF', 'fund flow', 'sector rotation', 'style factor', 'thematic momentum') but stops short of comprehensive synonyms/ticker-style triggers; a few common variations are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (US ETF flow / sector breadth analysis) with distinct triggers; minimal realistic overlap with other skills.

5 / 5

Total

17

/

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.

Validation15 / 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
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.