CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xvary-stock-research

Thesis-driven equity analysis from public SEC EDGAR and market data; /analyze, /score, /compare workflows with bundled Python tools (Claude Code, Cursor, Codex).

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/xvary-stock-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 a well-organized, token-efficient overview with clearly sequenced workflows, explicit output contracts, and sensible failure-handling rules. Its main weaknesses are executable incompleteness — the bundled Python tools it depends on are missing from the bundle and no run commands appear in the body — and reference paths that lead to nonexistent files.

Suggestions

Ship the missing `tools/edgar.py` and `tools/market.py` in the bundle (or remove the 'bundled Python tools' claims and reference paths) — the /analyze, /score, and /compare workflows currently fail at step 1.

Add concrete invocation examples to the body (e.g. `python3 tools/edgar.py AAPL` and `python3 tools/market.py AAPL`) so the workflow is executable from SKILL.md alone.

Enumerate the 'minimum required EDGAR and market fields' for /score inline or point to the exact section of references/scoring.md that defines them.

DimensionReasoningScore

Conciseness

The ~95-line body is lean: numbered command steps, tight execution rules, and output shapes, with no explanation of concepts Claude already knows (no 'what is EDGAR' or finance tutorials). Minor trimmable bits remain — the intro line duplicates the frontmatter description and the branded footer/compliance sections are overhead — so it sits just below the 'every token earns its place' anchor.

4 / 5

Actionability

Steps are concrete in shape (named files, named references, explicit output sections), but the executable layer is broken: `tools/edgar.py` and `tools/market.py` are referenced throughout yet no tools/ directory exists in the bundle, and the body contains no actual invocation commands or enumeration of the 'minimum required fields' for /score. This is 'some concrete guidance but incomplete; missing key details' rather than mostly-executable level 4.

3 / 5

Workflow Clarity

Each command has a clear numbered sequence, explicit output-format checklists, and an error-recovery rule ('If a tool call fails, state exactly what data is missing and continue with available inputs. Do not hallucinate missing figures'). The operations are read-only research so the destructive-operation cap does not apply, but validation is implicit rather than an explicit checkpointed step, keeping it below level 5.

4 / 5

Progressive Disclosure

The three references (methodology.md, scoring.md, edgar-guide.md) exist, are clearly signaled in dedicated sections, and are one level deep — but scoring against the actual bundle shows the two most load-bearing referenced paths (`tools/edgar.py`, `tools/market.py`) do not exist anywhere in the bundle, and the body never mentions the four bundled PNG assets. Navigation is well-signaled for what exists, but the broken tool references are more than a 'minor organization gap', matching level 3 better than level 4.

3 / 5

Total

14

/

20

Passed

Description

53%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 names a specific data domain and three workflows but reads more like a feature label than a trigger: it lacks any 'use when' guidance, omits the natural terms users would say (stock, ticker, valuation), and does not state the concrete deliverables. It is clearly distinguishable from generic skills, mainly by its EDGAR data source rather than by its trigger phrasing.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks to analyze a stock or ticker, research a company's fundamentals from SEC filings, or compare two stocks.'

Include natural trigger terms users would actually say — 'stock', 'ticker', 'valuation', 'compare stocks' — not just domain jargon like 'equity analysis'.

State the concrete outputs (verdict-style memo, four-pillar scorecard, kill criteria) so the 'what' is comprehensive rather than implied by command names.

DimensionReasoningScore

Specificity

"Thesis-driven equity analysis from public SEC EDGAR and market data" names the domain and data sources, and "/analyze, /score, /compare workflows" hints at actions, but the concrete outputs (verdict memos, four-pillar scorecard, kill criteria) are never stated and "analysis" itself is generic within the domain. It fits the 'names domain and 1-2 concrete actions, but not comprehensive' anchor better than the level-4 anchor, which expects a denser list of specific action verbs.

3 / 5

Completeness

The 'what' is reasonably clear (equity analysis workflows over EDGAR and market data with bundled Python tools), but there is no 'Use when...' clause or equivalent trigger guidance — "(Claude Code, Cursor, Codex)" names environments, not use cases. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "equity analysis", "SEC EDGAR", "market data", and the command names are relevant, but the most natural user vocabulary — "stock", "ticker", "valuation", "compare stocks" — is entirely absent. This matches 'some relevant keywords but missing common variations or synonyms'; it falls short of level 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The SEC EDGAR + market data niche is clear and mostly distinct, but the generic slash-command names "/analyze", "/score", and "/compare" could collide with other skills defining the same commands. This is 'mostly distinct; minor overlap risk with closely related skills' rather than level 5's 'minimal conflict risk'.

4 / 5

Total

13

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/xvary-stock-research/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.