CtrlK
BlogDocsLog inGet started
Tessl Logo

earnings-flash

Rapid first-read earnings flash for a given company

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/daloopa/skills/earnings-flash/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete tools, code, HTML snippets, and a well-sequenced workflow with explicit fallback handling. It is well-structured with one-level-deep references, with only minor room to tighten comparative rationale prose.

DimensionReasoningScore

Conciseness

The body is mostly lean and instruction-dense, but includes comparative rationale prose such as 'This is lighter than the earnings-review skill (4Q vs 8Q...)' and 'The goal is just enough history to frame the latest quarter's results' that could be tightened.

2 / 3

Actionability

It names specific MCP tools (discover_companies, search_documents, get_stock_prices), gives exact file paths, copy-paste HTML snippets, and a concrete citation format, matching the fully-executable level-3 anchor.

3 / 3

Workflow Clarity

Steps 1-11 are clearly sequenced with explicit fallback logic ('If no document is found, proceed...', 'If that returns nothing, try...') and clear no-data handling, matching the level-3 anchor; no destructive/batch operations require additional validation loops.

3 / 3

Progressive Disclosure

The body points to clearly-signaled one-level-deep references (../data-access.md, ../design-system.md) and is organized into well-numbered sections, matching the level-3 anchor; no nested reference chains exist.

3 / 3

Total

11

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 domain-specific and avoids vague fluff, but it only states what the skill does without an explicit 'when to use' trigger and without listing multiple concrete actions. It also risks overlap with the related earnings-review skill.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants a quick first read of a company's earnings within minutes of a filing.'

List 2-3 concrete actions to lift specificity, e.g. 'pulls core metrics, frames BEAT/MISS verdicts, and saves an HTML flash report.'

Distinguish from the earnings-review skill, e.g. 'Use the earnings-review skill instead for full 8-quarter trend analysis.'

DimensionReasoningScore

Specificity

The phrase 'Rapid first-read earnings flash for a given company' names a clear domain (earnings flash) and a single action (first-read), but does not list multiple concrete actions like the level-3 anchor requires.

2 / 3

Completeness

It answers 'what' (a rapid first-read earnings flash) but provides no 'Use when...' trigger clause, so per the rubric guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

'earnings flash' and 'first-read' are natural finance terms a user might say, but common variations such as 'earnings report', 'earnings reaction', or 'earnings season' are missing, matching the level-2 anchor.

2 / 3

Distinctiveness Conflict Risk

The earnings-flash niche is fairly distinct, but the body reveals a sibling 'earnings-review' skill, so the description does not clearly distinguish this skill from that similar one, matching the level-2 anchor.

2 / 3

Total

8

/

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.