CtrlK
BlogDocsLog inGet started
Tessl Logo

alphagbm-earnings-crush

Full earnings-season IV analysis: historical crush, implied move forecast, IV Rank strategy tag, and a priced Iron Condor quote ready to trade. Triggers: "earnings crush AAPL", "NVDA IV before earnings", "implied move MSFT", "iron condor for META", "IV rank AAPL earnings", "earnings play TSLA", "should I short premium before AMZN earnings", "post-earnings IV drop", "straddle before earnings", "pre-earnings strategy"

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable skill body built around a concrete API spec with clear input/output and good section navigation. It scores solidly rather than perfectly because of minor fluff, the absence of a concrete call example, missing edge-case handling, and referenced mock-data files that are not bundled.

Suggestions

Add a concrete call example (e.g., a curl or fetch snippet hitting GET /api/options/earnings-crush/AAPL) so the guidance is copy-paste ready.

Drop the promotional footer line ('10K+ users.') and de-duplicate the IV Crush / Implied Move definitions that appear in both the table and the Output list.

Include brief guidance for failure cases (API error, no scheduled earnings, symbol not found) to round out the workflow, and ensure the referenced mock-data/earnings-crush/*.json files are actually bundled.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes domain competence, but the promotional footer ('Powered by AlphaGBM ... 10K+ users.') and slight redundancy between the 'What This Skill Does' table and the 'Output' list are minor trim opportunities.

4 / 5

Actionability

Concrete endpoint ('GET /api/options/earnings-crush/{symbol}'), named query parameters, and a full response-field spec give mostly executable guidance, but no actual call example (curl/fetch) leaves a small gap.

4 / 5

Workflow Clarity

Input/output is clearly specified and the single read-only API action is unambiguous, but there is no guidance on handling API errors, missing earnings dates, or edge cases — minor gaps in an otherwise clear flow.

4 / 5

Progressive Disclosure

Sections are well organized with clear navigation and one-level-deep mock-data references, but the referenced 'mock-data/earnings-crush/' files are not present in the bundle, a minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

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

A strong, specific description with concrete capabilities and an explicit, well-populated trigger list; it clearly answers both what the skill does and when to use it. The only mild risk is overlap with related IV-rank/options-strategy skills.

DimensionReasoningScore

Specificity

Names the domain and four concrete actions — 'historical crush, implied move forecast, IV Rank strategy tag, and a priced Iron Condor quote ready to trade' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both 'what' (full earnings-season IV analysis with its four components) and 'when' via an explicit 'Triggers:' clause with concrete phrases.

5 / 5

Trigger Term Quality

Ten natural trigger phrases users would actually say ('earnings crush AAPL', 'NVDA IV before earnings', 'implied move MSFT', 'iron condor for META', 'straddle before earnings', 'pre-earnings strategy') cover the space with synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear earnings-IV niche with distinct triggers, but the explicit 'IV Rank' framing creates minor overlap risk with a sibling iv-rank skill rather than being wholly isolated.

4 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 suspicious

Warning

Total

14

/

16

Passed

Repository
AlphaGBM/skills
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.