marketplace-liquidity▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Framework for diagnosing and fixing supply-demand imbalances in two-sided marketplaces.
- ›Guides you through understanding your marketplace type, identifying whether you're supply-constrained or demand-constrained, and defining fill rate as your core liquidity metric
- ›Emphasizes that liquidity is fundamentally about reliability: how often buyers find what they want and sellers find buyers
- ›Highlights the \"whac-a-mole\" nature of marketplace management, requiring constant rebalancing of
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:
- Understand the marketplace type - Ask about their supply/demand dynamics, how fragmented the market is, and whether needs are uniform or heterogeneous
- Diagnose the constraint - Determine if they're supply-constrained, demand-constrained, or facing a matching problem
- Define liquidity metrics - Help them establish clear measures of marketplace reliability and fill rates
- 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
How to use marketplace-liquidity on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add marketplace-liquidity
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches marketplace-liquidity from GitHub repository refoundai/lenny-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate marketplace-liquidity. Access the skill through slash commands (e.g., /marketplace-liquidity) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★36 reviews- ★★★★★Noor Abbas· Dec 12, 2024
Useful defaults in marketplace-liquidity — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Chaitanya Patil· Dec 8, 2024
marketplace-liquidity has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Piyush G· Nov 27, 2024
Solid pick for teams standardizing on skills: marketplace-liquidity is focused, and the summary matches what you get after install.
- ★★★★★Layla Shah· Nov 3, 2024
I recommend marketplace-liquidity for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Layla Brown· Oct 22, 2024
marketplace-liquidity reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Shikha Mishra· Oct 18, 2024
We added marketplace-liquidity from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Rahul Santra· Sep 25, 2024
marketplace-liquidity fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★William Jain· Sep 17, 2024
Solid pick for teams standardizing on skills: marketplace-liquidity is focused, and the summary matches what you get after install.
- ★★★★★Mia Jain· Sep 1, 2024
We added marketplace-liquidity from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yuki Rahman· Sep 1, 2024
I recommend marketplace-liquidity for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 36