CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

57

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/xvary-stock-research/SKILL.md

The canonical home for this skill is xvary-stock-research in administrakt0r/AI-Agents-Safe-Coding-Skills

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.

The skill body is well-structured, concise, and gives clear per-command workflows with sensible error-handling rules, but its actionability is undercut by references to Python tools that are not present in the bundle. Providing the tooling (or exact invocation syntax) would lift it materially.

Suggestions

Ship the referenced tooling by adding tools/edgar.py and tools/market.py (or move them into scripts/) so the workflow steps are actually executable.

Add concrete example invocations for each command, e.g. `python tools/edgar.py AAPL` and the expected output fields, instead of only describing the steps.

Either remove the duplicate 'Data Tooling' reference list or reconcile it with the 'Scoring + Methodology References' section to avoid the reader chasing the same paths twice.

DimensionReasoningScore

Conciseness

The body is lean and decision-oriented using short lists and tables; it assumes Claude's competence and avoids explaining finance concepts, with only minor redundancy between the workflow steps and the references section.

4 / 5

Actionability

It names specific scripts and reference files and defines concrete output shapes, but the workflow steps are high-level ('Pull SEC fundamentals from tools/edgar.py') with no exact invocations, and the referenced tools/edgar.py and tools/market.py do not exist in the bundle.

3 / 5

Workflow Clarity

Each command has a clearly numbered, sequenced workflow and the Execution Rules supply an error-handling fallback ('If a tool call fails, state exactly what data is missing and continue'); this is an analysis skill, not a destructive/batch op, so the validation cap does not apply.

4 / 5

Progressive Disclosure

The body is a clear overview with a dedicated 'Scoring + Methodology References' section pointing one level deep to real files (methodology.md, scoring.md, edgar-guide.md), but the broken references to tools/edgar.py and tools/market.py keep it from a 5.

4 / 5

Total

15

/

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 well-scoped to equity research with concrete named workflows, but it omits an explicit 'Use when...' trigger clause, which caps its completeness. Adding natural-language trigger guidance would round it out.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when you need thesis-driven stock analysis, a verdict-style equity memo, or a side-by-side ticker comparison from public filings.'

Add common user-facing synonyms such as 'stock research', 'ticker', and 'earnings/filings' to broaden natural trigger coverage.

Clarify the value of the bundled Python tools in the description itself (what they fetch/compute) rather than only naming the host IDEs.

DimensionReasoningScore

Specificity

Names the domain ('equity analysis from public SEC EDGAR and market data') and several concrete workflows ('/analyze, /score, /compare') plus bundled Python tools, so it lists multiple specific actions with only minor coverage gaps.

4 / 5

Completeness

It clearly states what the skill does but provides no explicit 'Use when...' trigger clause, so per the guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('equity analysis', 'SEC EDGAR', '/analyze', '/score', '/compare') with good coverage; a few common synonyms (e.g. 'stock research', 'ticker') are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

The equity-research niche with named slash-command workflows ('/analyze, /score, /compare') and SEC EDGAR data source is mostly distinct with only minor overlap risk against other finance skills.

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
administrakt0r/AI-Agents-Safe-Coding-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.