CtrlK
BlogDocsLog inGet started
Tessl Logo

bull-bear

Bull/bear/base case scenario framework for a given company

66

Quality

78%

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/daloopa/skills/bull-bear/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 strong, actionable, well-sequenced workflow that respects token budget and delegates shared details to clearly signaled one-level references.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout, assumes Claude's financial competence, and avoids explaining basic concepts; its length is justified by the complexity of a multi-step scenario build.

3 / 3

Actionability

Provides concrete executable guidance: named functions (discover_companies, get_stock_prices), exact calculations (8 quarters back, trailing 4Q totals), specific output path, and a copy-ready Daloopa citation format string.

3 / 3

Workflow Clarity

A clearly numbered sequence (1, 1b, 2-7) with explicit conditional checkpoints such as asking when no ticker is given, falling back to alternative search keywords, and skipping consensus if unavailable.

3 / 3

Progressive Disclosure

Well-organized numbered sections with one-level-deep, clearly signaled external references (../data-access.md, ../design-system.md) repeated with section pointers; no nested/deep references.

3 / 3

Total

12

/

12

Passed

Description

57%

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 communicates a distinct, niche capability but only answers the 'what' and omits an explicit 'when to use' trigger, which limits completeness and trigger coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks for bull/bear/base case scenarios, scenario analysis, or upside/downside for a company.'

Include common trigger variations such as 'scenario analysis', 'upside/downside', and 'price target' to improve natural-term coverage.

Lead with a concrete action verb (e.g. 'Build a bull/bear/base case scenario framework...') to sharpen specificity.

DimensionReasoningScore

Specificity

Names the deliverable ('bull/bear/base case scenario framework') but uses no concrete action verbs and does not enumerate the multiple actions involved (build, quantify, weight, report); closest to the 'names domain and some actions but not comprehensive' anchor.

2 / 3

Completeness

Clearly states what the skill produces, but there is no explicit 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural core terms ('bull/bear/base case', 'scenario') an analyst would say, but omits common variations such as 'scenario analysis', 'upside/downside', 'price target', and 'consensus'.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (equity scenario modeling for a named company) that is unlikely to overlap with other skills; distinct from generic analysis or document skills.

3 / 3

Total

9

/

12

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
openai/plugins
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.