"Agent skills" as a purchasable category is barely a year old, and there's no single marketplace for them yet — general creator platforms, official prompt libraries, and dedicated storefronts all sell into the same space with none of the accountability structures older plugin ecosystems eventually built (think a VS Code Marketplace review queue, or npm's download stats and maintainer history).
That gap means the checking is on you. Here's what actually predicts whether a skill, MCP server, or prompt pack you install today still works — and is still maintained — six months from now.
1. Is there one accountable seller, or many independent ones behind one storefront?
A general marketplace aggregates listings from lots of individual authors. Quality varies listing to listing, because nobody but that one author is responsible for keeping it current. A single-vendor storefront ties every item's upkeep to one team, for better or worse — check which structure you're actually looking at, because "marketplace" gets used for both and they carry very different maintenance guarantees.
This matters most for anything that wraps a third-party API. APIs deprecate endpoints, change auth, get acquired. A listing that hasn't been touched since it went up is a bet that nothing upstream has changed — check the last-updated date before assuming it has.
2. Can you read it before you pay?
A skill is a Markdown file. A prompt pack is text. An MCP server's source is usually public. None of that requires you to buy first — if a seller won't let you see at least one complete example before checkout, that's the finding, not a minor inconvenience. Read the actual file: does it have a specific trigger condition, or a vague description that hopes the model guesses when to load it? Does it check for failure states, or does it assume the happy path every time?
3. Do you keep it, or does it keep you?
There's a real difference between buying a file and buying access. A file you download runs forever, even if the seller disappears tomorrow — it's just Markdown, nothing about using it depends on a server staying up. Access gated behind a platform is a different product: it stops working the moment you stop paying or the platform shuts down. Neither is automatically the wrong choice, but check which one you're getting, because the pricing should reflect it. A subscription for something that doesn't change is a rental with extra steps.
4. What happens when the thing it wraps changes?
This is the check almost everyone skips. If a skill or kit integrates a specific API, go look at that API's own changelog or status page before you buy the wrapper. An integration built against a service that rebrands, deprecates a free tier, or shuts down an endpoint is selling you something that's already breaking — you just haven't hit the error yet. A seller who's serious about upkeep will usually say, somewhere, when they last verified the integration still works. If that date is missing entirely, treat it as unverified.
None of this is marketplace-specific
Every one of these checks applies whether you're buying an agent skill, installing a VS Code extension, or picking an npm package: who's accountable, can you inspect it first, do you keep what you paid for, and does it still match what it wraps. The five minutes it takes to run through them is cheaper than finding out the hard way after the thing silently stops working.
Top comments (0)