CtrlK
BlogDocsLog inGet started
Tessl Logo

institutional-flow-tracker

Use this skill to track institutional investor ownership changes and portfolio flows using 13F filings data. Analyzes hedge funds, mutual funds, and other institutional holders to identify stocks with significant smart money accumulation or distribution. Helps discover stocks before major moves by following where sophisticated investors are deploying capital.

61

Quality

77%

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 ./skills/institutional-flow-tracker/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A well-structured, highly actionable skill with real commands, documented parameters, quantified decision thresholds, and honest disclosure of the unimplemented script. Weaknesses are moderate redundancy across sections, one inconsistent script path, and interpretive detail inlined in SKILL.md that belongs in the existing references.

Suggestions

Fix the inconsistent path in Step 3 ("institutional-flow-tracker/scripts/analyze_single_stock.py") to match the "scripts/" prefix used everywhere else.

Deduplicate: list the WhaleWisdom/SEC EDGAR/DataRoma external resources once, and merge the Step 5 "Screening workflow integration" list into the "Integration with Other Skills" section.

Move the detailed Signal Strength Framework, Limitations, and Advanced Use Cases into the existing references (e.g., interpretation_framework.md), leaving brief signposts in SKILL.md.

DimensionReasoningScore

Conciseness

Mostly operational and efficient, but there is measurable redundancy: the WhaleWisdom/SEC EDGAR/DataRoma list appears twice (Step 3 and the track_institution_portfolio.py section), "Screening workflow integration" in Step 5 duplicates the "Integration with Other Skills" section, and the "Why coverage, not per-holder reconciliation" paragraph is API-rationale detail that could be trimmed or moved to a reference. Not a 2 because none of it is generic padding or explanation of concepts Claude already knows; not a 4 because the duplication is more than minor.

3 / 5

Actionability

Concrete, copy-paste-ready commands throughout — quick scan, sector scan, custom screening, single-stock deep dive — with full parameter documentation, defaults, output formats, and quantified interpretation thresholds (>15% QoQ, top-10 >50% concentration). Not a 5 because of a minor gap: the Step 3 example invokes "python3 institutional-flow-tracker/scripts/analyze_single_stock.py AAPL" while every other command uses "scripts/...", so one example is not executable as written from the skill directory.

4 / 5

Workflow Clarity

A clearly sequenced 5-step workflow with most checkpoints present: each step's output is specified, and data validation is built in via the A/B/C reliability grades with automatic Grade-C exclusion from screening. Not a 5 because there are no explicit error-recovery loops (e.g., what to do when the API key is missing, rate-limited, or a ticker returns no data); not a 3 because validation checkpoints are explicit and prominent rather than implicit.

4 / 5

Progressive Disclosure

Good structure against the actual bundle: the three reference files exist, are one level deep, and are clearly signaled twice (Step 4 and the References section with per-file descriptions); scripts and their parameters are documented inline. Not a 5 because the SKILL.md is a ~380-line body carrying substantial interpretive bulk — the full Signal Strength Framework, Limitations, and Advanced Use Cases — that overlaps the interpretation_framework.md reference and could be split out.

4 / 5

Total

15

/

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 solid, domain-specific description in third person with multiple concrete actions and natural trigger terms. Its main weakness is that the "when" is a restated "what" rather than explicit user-scenario triggers, and it slightly over-claims "portfolio flows" tracking that the body admits is not implemented.

Suggestions

Add an explicit trigger clause naming user scenarios, e.g. "Use when the user asks about institutional ownership, hedge fund or mutual fund 13F positions, or smart money flows into a stock."

Include natural synonyms users would say — "institutional buying/selling", "SEC filings", "fund holdings" — to strengthen trigger term coverage.

Align the claimed capability with reality: either drop "portfolio flows" (the portfolio-tracking script is not implemented) or qualify it as stock-level holder analysis.

DimensionReasoningScore

Specificity

Lists several concrete actions — "track institutional investor ownership changes and portfolio flows using 13F filings data", "Analyzes hedge funds, mutual funds, and other institutional holders", "identify stocks with significant smart money accumulation or distribution", "discover stocks before major moves". Not a 5 because coverage has minor gaps: no mention of the screening commands, quarterly report generation, or sector filtering that the skill actually provides.

4 / 5

Completeness

Both what and when are present: the opener "Use this skill to track institutional investor ownership changes..." is explicit trigger guidance, and the what is detailed across three sentences. Not a 5 because the when restates the what rather than naming distinct user scenarios (e.g., "Use when the user asks about hedge fund positions or 13F filings"); not a 3 because the "Use this skill to..." clause is equivalent explicit trigger guidance, so the missing-'Use when' cap does not bind.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "institutional investor", "13F filings", "hedge funds", "mutual funds", "smart money", "accumulation or distribution", "ownership changes". Falls short of comprehensive because common variations like "institutional buying/selling", "SEC filings", "fund holdings", or "13Fs" are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers — "13F filings" and "institutional investor ownership changes" are unlikely to fire the wrong skill. Minor overlap risk remains: "portfolio flows" could collide with portfolio-management skills, and within a finance skill suite the generic "analyze" framing slightly overlaps sibling screeners.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tradermonty/claude-trading-skills
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.