CtrlK
BlogDocsLog inGet started
Tessl Logo

alex-hormozi-pitch

Create irresistible offers and pitches using Alex Hormozi's methodology from $100M Offers. Guides through value equation, guarantee frameworks, pricing psychology, and creating offers "too good not to take" for any product or service.

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 ./skills_all/alex-hormozi-pitch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 body is well-organized and token-efficient but stops at describing frameworks rather than giving executable steps, and its single external reference is a non-existent file, weakening both actionability and navigation.

Suggestions

Add a concrete, runnable example of applying the value equation or a guarantee template inline so the skill is actionable without the missing reference.

Provide the actual step-by-step execution sequence with at least one validation checkpoint (e.g. 'verify the offer hits all four value-equation levers before outputting').

Fix the broken reference by shipping create-hormozi-pitch.md in references/ (or inline its essential steps) so the one-level-deep pointer resolves.

DimensionReasoningScore

Conciseness

The body is lean with short bullets and sections and avoids explaining concepts Claude already knows; minor redundancy ('Guides you through...') and framework lists could be tightened.

4 / 5

Actionability

The body delegates execution to a slash command and an external file and only describes the frameworks; there is no executable code or copy-paste-ready steps, leaving guidance incomplete.

3 / 5

Workflow Clarity

A 7-step list appears in 'How to Execute' but it reads as a contents list rather than an ordered procedure, and there are no validation checkpoints or feedback loops.

3 / 5

Progressive Disclosure

Sections are organized and a one-level-deep reference is signaled, but the referenced file (create-hormozi-pitch.md) does not exist in the bundle, breaking navigation, and framework content that could live in the reference is inlined.

3 / 5

Total

13

/

20

Passed

Description

66%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 conveys a clear, distinctive purpose with several concrete capabilities and natural trigger terms, but it lacks an explicit 'when to use' clause that would push completeness and overall score higher.

Suggestions

Add a 'Use when...' sentence naming concrete triggers, e.g. 'Use when the user wants to craft a sales offer, value proposition, guarantee, or pitch.'

Mention the value stack, scarcity/urgency, and MAGIC naming in the description so the capability list is comprehensive.

Include common user phrasings ('sales script', 'closing', 'proposal', 'lead magnet') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('value equation, guarantee frameworks, pricing psychology, and creating offers') but does not enumerate the full framework set, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clear (Hormozi methodology and frameworks) but there is no 'Use when...' trigger clause, which the rubric caps at 3.

3 / 5

Trigger Term Quality

Strong natural terms ('offers', 'pitches', 'pricing', 'guarantees', 'value proposition') users would say, though a few common phrasings ('sales script', 'closing', 'proposal') are missing.

4 / 5

Distinctiveness Conflict Risk

'Alex Hormozi's methodology from $100M Offers' is a distinct niche with minimal conflict risk, though generic terms like 'offers/pitches/pricing' overlap slightly with general sales skills.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Microck/ordinary-claude-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.