CtrlK
BlogDocsLog inGet started
Tessl Logo

earnings-prep

Pre-earnings preparation report for the night before a company reports

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

Quality

Content

77%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.

A detailed, highly actionable earnings-prep workflow with concrete tool calls, search templates, and table schemas, and a clearly sequenced multi-step process with conditional checkpoints. It is let down by verbosity and by referencing external sibling files that do not exist in the evaluated bundle rather than shipping its own reference files.

Suggestions

Tighten repeated emphasis and framing prose (e.g., consolidate the repeated "CRITICAL: Always use Daloopa as the primary data source" statements) to improve token efficiency.

Move detailed, reusable material (e.g., the beat/miss methodology in Section 4, peer search-query templates) into actual references/ files within the bundle instead of relying on external ../data-access.md and ../design-system.md files that are not present.

Add an explicit data-validation checkpoint (e.g., verify a guidance series and its matching actuals series both exist before computing the whisper number) to harden the batch data operations.

DimensionReasoningScore

Conciseness

The ~255-line body is mostly domain-specific actionable guidance that assumes Claude's competence, but repeated emphasis ("CRITICAL", "MUST") and framing prose could be tightened; anchor 2 fits better than 3.

2 / 3

Actionability

Provides concrete tool calls (discover_companies, get_company_fundamentals, search_documents, get_stock_prices), exact search-query templates, table schemas, metric taxonomies, and a citation format — copy-paste ready guidance.

3 / 3

Workflow Clarity

Clear numbered 12-step sequence anchored on latest_calendar_quarter with explicit conditional checkpoints (ask if no ticker, peer-reported checks, WebSearch fallbacks) and a final checklist deliverable; the task is non-destructive so no destructive-ops validation cap applies.

3 / 3

Progressive Disclosure

The body is a monolithic single file; its only references (../data-access.md, ../design-system.md) are external sibling files not present in the bundle, and no references/scripts/assets directories exist, so structure is present but not split into one-level-deep bundle files.

2 / 3

Total

10

/

12

Passed

Description

57%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 clearly identifies a specific niche and deliverable but stops short of listing concrete actions or providing explicit usage triggers, leaving a user unsure when to invoke it. Adding a "Use when..." clause with natural trigger terms would lift the weaker dimensions.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when preparing for an earnings print, building an earnings preview, or the night before a company reports."

List 2-3 concrete actions the report performs (e.g., computes a whisper number from guidance history, pulls peer read-throughs) to raise specificity.

Include common trigger variations users would actually say ("earnings prep", "earnings preview", "earnings call prep").

DimensionReasoningScore

Specificity

Names the domain and deliverable ("Pre-earnings preparation report for the night before a company reports") but lists no concrete actions; not vague enough for 1, not a multi-action list for 3.

2 / 3

Completeness

States what the skill produces and gives timing context, but provides no explicit trigger guidance; per the guidelines a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant terms ("earnings", "report", "company reports") but lacks a "Use when" clause and misses common variations like "earnings preview" or "earnings call prep".

2 / 3

Distinctiveness Conflict Risk

"Pre-earnings preparation" is a narrow, well-defined niche with distinct triggers that is unlikely to overlap with other 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.