skills/marketplace-liquidity/SKILL.md
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.
npx skillsauth add cvillamarp-lgtm/skillspodcast marketplace-liquidityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user build and manage marketplace liquidity using frameworks from 4 product leaders.
When the user asks for help with marketplace liquidity:
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.
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.
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.
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.
For all 4 insights from 4 guests, see references/guest-insights.md
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.