marketplace-liquidity
Help users build and manage marketplace liquidity. Use when someone is working on a marketplace business, struggling with supply/demand balance, trying to improve match rates, or asking how to reach critical mass in a two-sided market.
Best use case
marketplace-liquidity is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Help users build and manage marketplace liquidity. Use when someone is working on a marketplace business, struggling with supply/demand balance, trying to improve match rates, or asking how to reach critical mass in a two-sided market.
Teams using marketplace-liquidity should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/marketplace-liquidity/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How marketplace-liquidity Compares
| Feature / Agent | marketplace-liquidity | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Help users build and manage marketplace liquidity. Use when someone is working on a marketplace business, struggling with supply/demand balance, trying to improve match rates, or asking how to reach critical mass in a two-sided market.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Marketplace Liquidity Management Help the user build and manage marketplace liquidity using frameworks from 4 product leaders. ## How to Help When the user asks for help with marketplace liquidity: 1. **Understand the marketplace type** - Ask about their supply/demand dynamics, how fragmented the market is, and whether needs are uniform or heterogeneous 2. **Diagnose the constraint** - Determine if they're supply-constrained, demand-constrained, or facing a matching problem 3. **Define liquidity metrics** - Help them establish clear measures of marketplace reliability and fill rates 4. **Design interventions** - Guide them on where to focus to improve liquidity (geographic focus, supply acquisition, demand generation, matching quality) ## Core Principles ### Liquidity is how marketplaces win Benjamin Lauzier: "Liquidity is how marketplaces win. It's this measure of your ability to match buyers and sellers efficiently." Focus on the core metric of how reliably you can connect supply with demand. This is the foundational metric that determines marketplace success or failure. ### Liquidity = reliability of the marketplace Dan Hockenmaier: "How reliable is the marketplace? If the consumer is looking for something or supplier is looking to sell something, how often can they do that thing they're trying to do?" Define liquidity as fill rate - the percentage of times buyers find what they want and sellers find buyers. Make this your number one metric. ### Marketplace management is whac-a-mole Ramesh Johari: "Marketplaces are a little bit like a game of whac-a-mole... a lot of marketplace management is moving attention and inventory around." Expect constant rebalancing between supply and demand across different segments and geographies. Build systems to reallocate attention and inventory dynamically. ### No supply without demand, no demand without supply Tim Holley: "If you've got supply without demand, then you don't really have a marketplace. If you've got demand and no supply to meet it, then you also don't have a marketplace." Watch for the "graduation problem" where successful sellers leave the platform. Use data to guide supply toward areas of unmet demand. ## Questions to Help Users - "How do you define liquidity for your marketplace? What's your fill rate?" - "Are you currently supply-constrained or demand-constrained? Does this vary by geography or category?" - "How fragmented are the needs in your marketplace - are they uniform or highly heterogeneous?" - "What happens when you add more supply? Does it immediately get absorbed by demand?" - "Are you seeing a 'graduation problem' where successful suppliers leave your platform?" ## Common Mistakes to Flag - **Growing both sides equally** - Usually one side is the constraint. Focus resources on the bottleneck - **Ignoring geographic/category fragmentation** - National liquidity metrics can hide severe local imbalances - **Not measuring fill rate** - Without a clear liquidity metric, you can't manage toward it - **Over-expanding before reaching local density** - It's better to be highly liquid in one market than illiquid across many ## Deep Dive For all 4 insights from 4 guests, see `references/guest-insights.md` ## Related Skills - Measuring Product-Market Fit - Designing Growth Loops - Pricing Strategy - Retention & Engagement
Related Skills
jetbrains-marketplace-reviews
Fetch and visualize reviews for any JetBrains Marketplace plugin. Use when (1) analyzing plugin review trends, (2) getting review statistics for a time period, (3) visualizing rating distributions, (4) monitoring user feedback. Triggers on requests like "get JetBrains reviews", "copilot plugin feedback", "JetBrains marketplace reviews", "visualize plugin ratings", "analyze JetBrains plugin reviews".
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
acc-create-bulkhead
Generates Bulkhead pattern for PHP 8.5. Creates resource isolation with semaphore-based concurrency limiting and thread pool isolation. Includes unit tests.
acc-create-anti-corruption-layer
Generates DDD Anti-Corruption Layer for PHP 8.5. Creates translation layer between bounded contexts or external systems. Includes adapters, translators, facades, and unit tests.
acc-create-action
Generates ADR Action classes for PHP 8.5. Creates single-responsibility HTTP endpoint handlers with PSR-7 support. Includes unit tests.
acc-clean-arch-knowledge
Clean Architecture knowledge base. Provides patterns, antipatterns, and PHP-specific guidelines for Clean Architecture and Hexagonal Architecture audits.
acc-claude-code-knowledge
Knowledge base for Claude Code formats and patterns. Use when creating or improving commands, agents, skills, or hooks.
acc-check-leaky-abstractions
Detects leaky abstractions in PHP code. Identifies implementation details exposed in interfaces, concrete returns from abstract methods, framework leakage into domain, and infrastructure concerns in application layer.
acc-check-encapsulation
Analyzes PHP code for encapsulation violations. Detects public mutable state, exposed internals, Tell Don't Ask violations, getter/setter abuse, and information hiding breaches.
acc-check-bounded-contexts
Analyzes bounded context boundaries in DDD projects. Detects cross-context coupling, shared kernel violations, context mapping issues, and ubiquitous language inconsistencies. Generates context map diagrams and boundary recommendations.
acc-architecture-doc-template
Generates ARCHITECTURE.md files for PHP projects. Creates layer documentation, component descriptions, and architectural diagrams.
acc-api-doc-template
Generates API documentation for PHP projects. Creates endpoint documentation with parameters, responses, and examples.