CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

uzi

A-share, Hong Kong, and US stock analysis skill for deep research, quick scans, investor panel review, hot-money/LHB analysis, trap detection, valuation, IC memos, and Bloomberg-style HTML reports.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is an exemplary lean router: concise, unambiguous dispatch rules and executable commands with no wasted tokens. Its one real weakness is that the bundle as shipped does not contain most of the files it routes to, so progressive disclosure fails in practice even though it is well designed on paper.

Suggestions

Ship the referenced sub-skills (skills/deep-analysis/SKILL.md, skills/investor-panel/SKILL.md, skills/lhb-analyzer/SKILL.md, skills/trap-detector/SKILL.md), the commands/ directory, and run.py alongside this root file, or correct the paths so every routed reference resolves in the published bundle.

Add a one-line fallback instruction for requests that match no listed workflow (e.g. default to the deep-analysis skill) so dispatch never dead-ends.

Briefly note what run.py produces (report location or output format) so the execution commands are self-explanatory without opening the sub-skills.

DimensionReasoningScore

Conciseness

The ~50-line body is lean and every section earns its place: a routing table, three one-line executable commands, and six terse agent rules, with no explanation of concepts Claude already knows; the single contextual sentence about being the repository-root entry is functional, matching anchor 5.

5 / 5

Actionability

Concrete, copy-paste-ready commands ("python3 run.py <ticker> --no-browser", "--remote", "--school F") and unambiguous file-level routing provide mostly executable guidance, matching anchor 4; it falls short of anchor 5 because run.py and most routed targets are not present in the bundle, leaving key execution details unverifiable.

4 / 5

Workflow Clarity

This is a simple router skill whose single action (dispatch to the narrowest matching workflow) is unambiguous: each request category maps to exactly one target file with an explicit tiebreak rule ("Use the narrowest matching workflow"), so per the simple-skill exception it scores 5; no destructive or batch operations require validation checkpoints here.

5 / 5

Progressive Disclosure

The written structure is well-signaled with one-level references and would merit a higher score, but scored against the actual bundle only references/macro-calendar.md resolves, while all four skills/*/SKILL.md paths, commands/, and run.py referenced in the body are absent, so navigation breaks for most entry points — moderate structural problems matching anchor 3 rather than the fully resolvable navigation of anchor 4/5.

3 / 5

Total

17

/

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.

The description is specific and domain-distinct with a strong capability list, but it entirely lacks a "Use when..." trigger clause, capping completeness at 3 and weakening its value for skill selection. Adding explicit usage triggers and a few natural synonyms would lift it substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks for stock research, valuation, earnings review, or a research report on A-share, Hong Kong, or US listed companies."

Add natural synonym trigger terms users actually say, such as "equity research", "initiation report", "price target", "DCF", and 龙虎榜/LHB, to improve trigger-term coverage from good to comprehensive.

Consider trimming jargon-heavy items (e.g. "IC memos") or pairing them with a plain-language equivalent so the description reads as concrete actions rather than a feature-name list.

DimensionReasoningScore

Specificity

The description lists several specific capabilities in a clearly named domain ("deep research, quick scans, investor panel review, hot-money/LHB analysis, trap detection, valuation, IC memos, and Bloomberg-style HTML reports"), matching anchor 4's several specific actions with minor gaps; it falls short of anchor 5 because the items are feature names rather than fully spelled-out concrete operations and coverage of the workflow is not comprehensive.

4 / 5

Completeness

The "what" is clear (an analysis skill with enumerated capabilities) but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3; it cannot be 4 because anchor 4 requires both a what and a when.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("stock analysis", "valuation", "trap detection", "investor panel", "A-share", "US stock") that users would plausibly say, matching anchor 4; it is not anchor 5 because common variations like "equity research", "earnings review", "price target", "DCF", or localized terms (e.g. 龙虎榜) are missing.

4 / 5

Distinctiveness Conflict Risk

Specialized triggers like "hot-money/LHB analysis", "IC memos", and "A-share" carve a distinct niche, but the broad core phrasing "stock analysis... valuation... deep research" overlaps generic equity-research and valuation skills, fitting anchor 4 (mostly distinct, minor overlap risk) rather than anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

wbh604/UZI-Skill

Path

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.