How I turned our Marketplace guidelines into three Agent Skills
Three Agent Skills for templates, components and listings that fix what they can and tell you what they couldn’t check.
We wrote the Marketplace guidelines. Creators still submit templates that overflow on mobile, components that keep animating on the Canvas, and listings that call a logo an “integration”.
The guidelines cover all of it. They live in a help article, and you don’t keep a help article open next to your project while you check each recommendation by hand.
When Framer launched Skills, I saw a way to put the guidelines inside the project. I turned them into three: Marketplace Template QA, Marketplace Component QA, and Marketplace Listing.
The first version stopped at a report
The first Template QA and Component QA skills inspected a project and returned a list: things to fix, recommendations, checks that passed.
The output left the creator with a to-do list, even though the Agent had already found the overflow, the broken link, and the property control that did nothing. Stopping there felt like a missed opportunity.
So I changed both skills to fix what has a clear solution and check the result. Bigger design decisions, and changes that could break existing behavior, stay with the creator.
Where the Agent has to stop
Writing the instructions took less time than deciding where the Agent should stop. Three lines took the most work:
Applied versus verified. An edit doesn’t prove the problem is fixed. The report separates fixes the Agent checked from changes that still need testing, and it lists what it couldn’t check.
Repairing versus removing. If an animation drains resources off-screen, the Agent pauses it there. It doesn’t delete the animation to make the problem disappear.
Facts versus guesses. The listing skill drafts from what’s in the project. Pricing, support terms, and URLs come back as questions.
Try them
Marketplace Template QA checks the project and its preview, including desktop, tablet, and phone layouts, and fixes the problems it can. You can remix the template project to try it on the demo.
Marketplace Component QA checks that a component works outside your example. For code components, it looks for problems like animations that run on the Canvas and missing cleanup. You can remix the component project to run it yourself.
Marketplace Listing drafts the name, byline, description, and a screenshot plan from what’s in the project, and it keeps demo content separate from working functionality. It’s included in the template project, so you can run it there after the QA pass.
Run the skills on the demo projects or on your own, and keep building with Framer!