/marketplace/skills) indexes reusable method documents. A skill is “how to do it” knowledge — once installed, experts discover and load it on their own, so you never have to remember skill names.
For what skills are and the three ownership tracks, see Skills. This page is about the marketplace itself.
Skills are all free
Marketplace skills have no price field. There is no unlock, subscription, or per-use fee. Installing costs nothing.Installing is free, but using a skill consumes normally — when a skill activates, its text enters the context and is billed by token. Glance at document length when picking: a skill several thousand characters long charges that input on every activation.
Which library it lands in (you choose at install time)
Clicking “Use in Profy” asks for a target, which determines where the skill is visible afterwards:
Installing to an expert requires access to it: platform built-in experts are open to anyone; marketplace experts require that you already have access, otherwise you get a 403.
Installing downloads and stores the skill package. Large packages run as an async job: the endpoint returns a job ID and the frontend polls until it finishes.
Categories grow out of the skills themselves
Categories are not a table you must curate first. Listings group by each skill’s owncategory field; the category table is only a display overlay (localized name, icon, sort order).
Practical consequence: if category metadata is missing, skills still group by code and stay visible — they never disappear as a block. Each category section previews at most 6 skills; click the heading for the full category page.
Browsing and filtering
Detail pages show the skill document (
SKILL.md body), the file tree, evaluation info, and related skills. The file tree lets you see exactly which scripts and reference files a skill ships before you install it.
Where skills come from
Marketplace entries are indexed from GitHub repositories: the system fetchesSKILL.md from the repo root (trying main, then master) and parses its frontmatter.
Failures and fixes
After installing
Skills don’t need to be “turned on.” Experts discover → activate → execute on demand: first they see only names and one-line descriptions (nearly free), then load the full text only if it’s relevant. So installing ten skills doesn’t mean paying for ten documents every conversation — only the activated one enters the context.Keep reading
What skills are
Structure, the three ownership tracks, and progressive disclosure
Skill catalog
Every built-in skill
Expert marketplace
Find an expert instead of a method
Plugins overview
Capability extensions beyond skills