CtrlK
BlogDocsLog inGet started
Tessl Logo

bull-research

Use this skill for building the strongest possible bullish case for positions, identifying upside catalysts, positive technical patterns, and favorable fundamental factors.

59

Quality

67%

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 ./packages/tentacles/Trading/Mode/ai_trading_mode/resources/skills/bull_researcher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 content is well-structured and actionable, with a clear bull-case workflow and a concrete JSON output schema. Its main weakness is conciseness: much of it catalogs basic technical-analysis concepts Claude already knows instead of adding skill-specific structure.

Suggestions

Trim or collapse the basic indicator explanations (e.g. golden cross, higher highs/lows, Fear & Greed) into terse checklists, assuming Claude's domain knowledge.

Move the lengthy technical/fundamental/sentiment indicator lists into a reference file and keep SKILL.md as an overview pointing to it.

Add a light validation step for the thesis (e.g. 'confirm each catalyst has a concrete data source') to lift workflow clarity toward the top anchor.

DimensionReasoningScore

Conciseness

Much of the body restates well-known technical-analysis concepts Claude already knows (e.g. 'Golden cross (50 MA crosses above 200 MA)', 'Higher highs and higher lows', 'Fear & Greed showing extreme fear'), which is padded explanation rather than novel structure.

2 / 5

Actionability

The 'Bull Case Structure' gives a concrete 5-step framework and the JSON 'Output Format' is a copy-paste-ready schema with a worked example, providing mostly executable guidance with only minor gaps in the analytical checklists.

4 / 5

Workflow Clarity

There is a clear sequence (thesis → catalysts → price targets → timeline → risk factors → counter-bear arguments), and the task is informational rather than destructive/batch so the validation cap does not apply; it falls short of 5 only because there are no explicit validation or feedback checkpoints.

4 / 5

Progressive Disclosure

The body is well-organized into clearly headed sections with no nested external references, but at over 50 lines it inlines lengthy indicator checklists that could be split into reference material, leaving it just below the lean one-level-deep 5.

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

The description is specific and reasonably complete, naming several concrete actions and natural trigger terms with a clear 'Use this skill for...' clause. It stops short of the top anchor because a few terms are generic and the trigger is action-based rather than a distinct 'when' condition.

Suggestions

Add explicit trigger phrasing tied to user intent, e.g. 'Use when the user wants a buy/long thesis or a bullish argument for an asset'.

Include common synonyms (e.g. 'long position', 'buy case', 'bull thesis') to broaden natural trigger coverage.

Tighten generic terms like 'favorable fundamental factors' into concrete actions such as 'evaluating on-chain growth, adoption, and competitive moat'.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'building the strongest possible bullish case for positions, identifying upside catalysts, positive technical patterns, and favorable fundamental factors' — but 'favorable fundamental factors' stays somewhat generic, so it does not reach the comprehensive coverage of a 5.

4 / 5

Completeness

It gives a clear 'what' (building the bullish case, identifying catalysts/patterns/factors) and a 'when' via 'Use this skill for...', but the trigger restates the action rather than naming distinct user-request conditions, leaving it below the explicit-anchor 5.

4 / 5

Trigger Term Quality

It surfaces natural trading-domain phrases a user would say ('bullish case', 'upside catalysts', 'positions', 'technical patterns'), but misses common synonyms like 'long position' or 'buy thesis' that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

The bullish-research niche is clearly distinct with low conflict risk, yet phrases like 'positive technical patterns' and 'favorable fundamental factors' are broad enough to overlap slightly with related analysis skills, capping it at 4 rather than 5.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Drakkar-Software/OctoBot
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.