Docs

Marketplace

Discover public skills, inspect their sources and add selected packages to your private vault.

The Marketplace helps you discover skills before bringing them into your vault. Browse popular skills, recent trends, dated official selections, packs and observed activity. You can browse the public catalog without signing in.

Open Marketplace from the vault navigation, the Vault home or the Skills page. Import screens offer the same shortcut when you need to find a package. If a Skills search has no matches, Search marketplace carries your search into the catalog. Empty Collections also links to skill packs.

From the public website, use Marketplace in the navigation, homepage introduction, first workflow step or footer. The first step offers Find a skill, Start with a pack and Bring your own. The Quickstart explains how discovery fits into your first release.

Add a skill to your vault

  1. Open a skill and choose Add to vault.
  2. Review the exact source revision, package files and capacity in your selected vault. You can read SKILL.md before confirming.
  3. Choose Add as Draft beside the destination at the top of the review. On mobile, this action stays at the bottom of your screen while you read. The package is saved privately with its source and version history.
  4. Open the vault skill and run its security scan. Organization vaults also require the normal review before the version is Ready.
  5. Use the Ready version through your existing agent connection.

Owners and admins can add marketplace skills. A prepared package is available for 24 hours so you can return to its review page. Saving uses the exact package you reviewed. If a save is interrupted, reopen the review to recover its result.

A source without a supported import URL offers View source. You can also use Skills → Import → GitHub to inspect a public repository directly.

Catalog size and your limits

Browsing and searching the marketplace use none of your vault capacity. Only packages you add count toward your existing skill, source, collection, version and storage limits. Skills from the same repository reuse its source and source collection. Limits are checked again when you save.

A pack lets you choose several skills for one purpose. Review each selected package before confirming. The selection adds a pack collection; shared sources are reused. An identical package already in your vault keeps its version and review status, without using extra version or file storage capacity. New packages are saved as Drafts. Each skill is reviewed independently. If one member fails, your successful imports remain available and you can retry the failed member.

Search and activity

Recommended is the starting view: popular skills are spread across publishers so one publisher's repositories do not fill the list. It is a discovery order, not a security endorsement. Popular, Trending and Hot keep the provider's corresponding order.

Use Description language to choose English, Spanish, Chinese, other languages or Not identified. Language is estimated from the saved description; missing, short or uncertain descriptions stay unidentified. This does not determine the publisher's country or which languages the skill can work in.

Enter all or part of a Publisher name to narrow results. Check Exclude publisher to hide that publisher instead. Import from GitHub shows entries with a compatible source URL; package validation, permissions and vault limits are checked when adding. Combine these filters with Official selection and search. Apply filters updates the list; Clear filters restores the starting view. Filters remain in the URL when you move between pages.

These filters apply to Installskills' saved catalog. The separate Search skills.sh action sends only your search phrase and displays provider results.

Normal search uses the catalog stored by Installskills. If you choose Search skills.sh, only that search phrase is sent to the provider. Avoid entering private information in an external search.

Popular, Trending and Hot are different measurements reported by skills.sh. Observed growth compares completed snapshots of the same measurement. Our history starts when we first collect the data. “New to this catalog” means newly found here; it does not mean the skill was just published.

Official selection shows a dated selection by skills.sh. It does not replace license checks, certify the package or bypass your vault’s security process.

Updates and dependencies

Installskills checks imported GitHub sources for new revisions on a daily schedule. Collections → Sources and the vault skill show Update available and the last successful check. Owners and admins receive an in-app notification once per changed package; open it to review the source in the correct vault.

Choose Review updates to compare files with the packages you last imported. Inspect the exact revision, select packages, then Import selected updates to save new Drafts. You can also run Check updates manually. Checking never adds other skills from the repository. Your current Ready version stays available while a new Draft goes through its scan and any required approval.

Checks run in bounded batches, so use the displayed date to assess freshness. A failed check preserves the last known result and shows Check failed; Check pending means the package has not yet been checked at the observed revision. If the author removes or invalidates a package, your saved version remains in the vault. Popularity changes are separate from package updates.

Skill packages may include scripts or refer to tools, accounts and dependencies that need separate setup. Importing stores files; it does not run scripts or install those dependencies. Downloading a package also does not confirm that an agent installed it locally.