CtrlK
BlogDocsLog inGet started
Tessl Logo

bear-research

Use this skill for building the strongest possible bearish case, identifying downside risks, negative technical patterns, and adverse fundamental factors.

55

Quality

61%

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/bear_researcher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 a well-organized, mostly lean analytical framework with a concrete JSON output template, but it reads as an output checklist rather than a sequenced workflow with validation. Adding an explicit analysis-to-synthesis process would lift workflow clarity.

Suggestions

Reframe Section 4 as an ordered process (gather indicators → form core thesis → quantify risks/targets → draft counterarguments → emit JSON) with a checkpoint to re-examine evidence against the thesis before output.

Point to concrete data sources or commands for the indicators (e.g., where to read on-chain active addresses or sentiment indexes) to close the actionability gap.

Trim generic Best Practices items like 'Be intellectually honest' and 'Avoid confirmation bias' that Claude already applies by default.

DimensionReasoningScore

Conciseness

The body is mostly lean bullet checklists that assume Claude knows terms like 'death cross' and 'FOMO' rather than explaining them, with only minor padding in the eight-item Best Practices section.

4 / 5

Actionability

A copy-paste-ready JSON output template plus a structured bear-case framework (thesis, 3-5 risks, price targets, timeline, catalysts) give concrete guidance, though no data sources or retrieval methods are specified for gathering the indicators.

4 / 5

Workflow Clarity

Section 4 lists output components rather than a sequenced process, and there are no explicit validation checkpoints or feedback loops; the sequence of analysis-to-output is only implicit.

3 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and is organized into clearly headed sections (Overview, Instructions, Output Format, Best Practices), though at ~118 lines it exceeds the simple-skill threshold that would allow a 5 on structure alone.

4 / 5

Total

15

/

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 clearly conveys a focused bearish-research purpose with several concrete capabilities, but its trigger guidance is circular rather than scenario-based and it uses second-person voice. It is distinguishable but could be sharpened with explicit 'use when...' scenarios.

Suggestions

Replace the circular trigger with concrete scenarios, e.g. 'Use when evaluating a short position, assessing downside risk on a holding, or stress-testing a bullish thesis.'

Switch to third-person voice ('Builds the strongest possible bearish case...') to avoid the second-person specificity penalty.

Add natural user synonyms such as 'short thesis', 'downside analysis', or 'risk review' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions (building the bearish case, identifying downside risks, negative technical patterns, adverse fundamental factors), but the second-person phrasing 'Use this skill for' triggers a one-point specificity penalty from a base of 4.

3 / 5

Completeness

The 'what' is clear, but the 'when' is circular — 'Use this skill for building the strongest possible bearish case' restates the purpose rather than naming concrete triggering scenarios, so the trigger guidance is only weakly implied.

3 / 5

Trigger Term Quality

Domain keywords like 'bearish case' and 'downside risks' are present but lean technical, and it lacks natural scenario triggers a user would actually say such as 'when evaluating a short' or 'when researching a token to sell'.

3 / 5

Distinctiveness Conflict Risk

The bearish-research niche is clearly distinct with its own triggers, with only minor overlap risk against a possible sibling bull-research or general trading-research skill.

4 / 5

Total

13

/

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.