CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hierarchy-of-marketplaces

Use when asked about "marketplace strategy", "chicken and egg problem", "liquidity", "two-sided market", "tipping a marketplace", "GMV growth", or "Sarah Tavel marketplaces". Helps founders and product leaders build defensible marketplace businesses by sequencing supply and demand. The Hierarchy of Marketplaces framework (created by Sarah Tavel / Benchmark) provides a progression from focused launch to market dominance.

Quality

74%

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 ./.agents/skills/hierarchy-of-marketplaces/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 a clean, well-sectioned overview of the framework with accurate sequencing of its three levels, but it reads as a summary rather than an operational skill: it tells Claude what the framework is and when to use it, not how to apply or diagnose with it. Cutting the boilerplate sections and replacing abstract level descriptions with concrete metrics, diagnostics, and decision criteria would make it genuinely actionable.

Suggestions

Add concrete application guidance for each level: how to measure "happy GMV" (e.g., repeat-purchase or retention metrics per side), what a 'thimble'-sized market looks like in practice, and explicit criteria for knowing a market has tipped before expanding.

Remove the boilerplate "Domain Context" and generic "Input Requirements" sections — they add tokens without actionable content.

Merge the redundant "Resources" and "Further Reading" sections and link Sarah Tavel's original series directly (the current Further Reading link points to a third-party summary rather than the primary source named in Resources).

DimensionReasoningScore

Conciseness

The core framework content (levels, key insight, when/when-not lists) is tight, but the "Domain Context" paragraph is pure padding ("a proven product management framework... combines best practices from industry leaders") and "Input Requirements" is generic boilerplate. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the noticeably-verbose level 2.

3 / 5

Actionability

The body describes the framework — three named levels with one-line glosses ("Constrain your market to a 'thimble'", "Reach saturation... until it tips") — but gives no executable specifics: no metrics for "happy GMV", no diagnostic steps for a stalling marketplace, no criteria or examples for applying each level. This is high-level hints missing the specific steps to execute, matching anchor 2; it does not reach anchor 3's 'some concrete guidance' because undefined jargon ("minimum viable happiness", "tips in your favor") is never operationalized.

2 / 5

Workflow Clarity

A clear sequence is present ("working through three levels in sequence": Focus → Tip → Dominate, with "Only then expand"), but checkpoints for advancing between levels are entirely missing — there is no guidance on how to know a market has tipped or minimum viable happiness has been reached. Sequence present with implicit/missing checkpoints matches anchor 3.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so all content appropriately lives inline in a short, sectioned body with a clearly signaled one-level-deep external link. Structure is good, but there are minor organizational gaps: "Resources" and "Further Reading" are redundant sections, "Domain Context" is boilerplate, and an H1 ("# Hierarchy of Marketplaces") sits inconsistently among H2 sections — keeping it just below the well-organized level 5.

4 / 5

Total

12

/

20

Passed

Description

90%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 description with explicit 'Use when' trigger guidance and excellent, natural keyword coverage including named-entity triggers. The only weakness is that the 'what' side stays at the level of one or two abstract actions rather than a list of concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain and one to two concrete actions — "build defensible marketplace businesses by sequencing supply and demand" and "provides a progression from focused launch to market dominance" — but does not enumerate several specific capabilities, matching the '1-2 concrete actions, not comprehensive' anchor. It is above a 2 (actions are not purely generic) and below a 4 (no list of several distinct actions).

3 / 5

Completeness

It explicitly answers both questions: what ("Helps founders and product leaders build defensible marketplace businesses by sequencing supply and demand" via the Hierarchy of Marketplaces framework) and when ("Use when asked about..." followed by concrete trigger phrases). A 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive and natural: "marketplace strategy", "chicken and egg problem", "liquidity", "two-sided market", "tipping a marketplace", "GMV growth", and "Sarah Tavel marketplaces" — exact phrases a user would say, including synonyms and named-entity variants. Nothing significant is missing for this domain.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and distinct — marketplace liquidity/tipping strategy tied to a named framework creator ("Sarah Tavel / Benchmark") — so triggers are unlikely to fire for unrelated skills. Terms like "liquidity" and "GMV growth" are marketplace-specific in this combined context.

5 / 5

Total

18

/

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

saski/arnesto

Path

.agents/skills/hierarchy-of-marketplaces/SKILL.md

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.