Agent skill registry preview

Find, inspect, and prepare governed agent skills.

Developer Preview: search public skills, inspect permissions, and use registry/gateway discovery now. Paid marketplace, payment capture, and payout automation remain prelaunch.

Browse catalogPublisher directorySign in for publisher workspace
What works without login
  • Search public skills.
  • Inspect public manifests, schemas, permissions, runtime type, pricing intent, review state, and publisher profile.
  • Copy public REST inspection commands.
  • Compare verified and submitted skills before adopting them.
What requires login
  • Save or install a verified skill to a project.
  • Create project runtime keys.
  • Run login-gated runtime tests through project policy checks.
  • Approve project policy, budget, subscription, billing, or ledger actions where the paid-preview role allows them.
  • Submit feedback or trust reports.
Public catalog preview2
Public publishers1
Verified publishers0
Review gatesSchema + Runtime + Human
Paid workflowPrelaunch model
SkillHub Catalog
2 results
Discovery filters
Category
Pricing intent
Permission risk
Runtime
Verification
Sort
Research

Browser Research

by SkillHub
medium

Research a web topic and return concise findings with source URLs.

verifiedn/a successn/a latency
Recommendation reasons
Verified reviewReviewed permissions
researchbrowsercitations
curl "https://api.useskillhub.com/v1/skills/browser-research"
After sign-inProject install, policy gate, runtime log, and runtime evidence require sign-in and project policy checks.
Project installPolicy gateRuntime logRuntime evidence
FreeVerified
Details
Data

Dataset Summarizer

by SkillHub Publisher
medium

Convert tabular data into structured notes, anomalies, and next actions.

reviewn/a successn/a latency
Recommendation reasons
Reviewed permissions
dataanalysissummary
Inspection onlyThis skill is submitted but not verified yet. You can inspect its manifest, schemas, permissions, publisher, and review state. Project adoption, runtime test, subscription, billing, and ledger actions unlock only after verified approval.
After verified approvalProject install, runtime test, billing, and ledger actions may unlock only after review approval.
Project installRuntime testBillingLedger actions
FreeSubmitted
Details
Authenticated project path

The developer path proves SkillHub is more than a directory: public discovery can become authenticated project state, runtime governance, logs, cost, and updates after sign-in and policy checks.

CurrentMarketplaceNextSkill detail
  1. MarketplaceSearch, filter, and compare trust, runtime, pricing, and publisher signals.
  2. Skill detailReview manifest, permissions, examples, feedback, incidents, and alternatives.
  3. Developer workspaceCreate projects, manage team, billing, webhooks, and buyer requests.
  4. Project commandPin versions, approve policy, create keys, and manage updates.
  5. Runtime testUse REST or MCP through the same policy, budget, subscription, and log path.
Inspect a skill
Operating reference - Developer Preview model

The catalog points to the governed path behind it.

Discovery is credible only when a public listing connects to publisher trust, availability, login-gated runtime governance, and prelaunch paid-marketplace modeling.

01Publish contractPublisherDraft -> submittedManifest, version, permissions, runtime, examples, and pricing intent are saved as an organization-scoped draft.02Review gateTrust operatorQueued -> decidedAutomated manifest, runtime, example, and security checks feed a human review decision with notes and SLA.03Project adoptionDeveloperInspect -> sign inApproved supply becomes searchable listing data with availability, publisher trust, pricing intent, feedback, and alternatives.04Runtime governanceAgent builderInvoke -> logProject keys, policy approval, budget, rate limit, subscription state, REST, and MCP calls share the same gateway path.05Prelaunch ledgerFinance adminModeled -> gatedFuture paid usage and subscription periods will post immutable transactions, commission splits, balance rows, refunds, and disputes after launch gates.06Paid readinessPublisher + adminPrelaunchPaid marketplace payout movement remains prelaunch and finance-gated; public pages show only readiness state.
Public catalog preview2
Public publishers1
Recorded calls0
Submitted skills1
Live rows stay live: empty production data is shown as empty, not replaced by demo supply.
Architecture preview

The catalog is tied to buyer, publisher, and operator state without claiming paid launch.

These preview signals come from the platform overview API. They explain the discovery-to-runtime architecture while paid marketplace operations remain prelaunch.

Developers

Projects return for policies, version changes, budgets, keys, and runtime evidence.

Projects0
Adopted skills0
Update inbox0
No installed-skill updates.
Developers

Publishers

Authors return for review feedback, runtime checks, demand signals, and paid-readiness blockers.

Submitted versions0
Failed checks0
Paid previewPrelaunch
No publisher actions.
Publishers

Operator controls

Review, payout, notification, and incident queues are protected inside the admin console.

Review queueAdmin gated
Finance review governancePrelaunch
Notification governanceAdmin gated
No active risk signals.
Operator only
Why teams come back
Approve and update adopted skills per project.Watch cost, failures, latency, incidents, and budget state.Compare better verified alternatives as the catalog grows.Repair review and runtime issues before losing distribution.Turn buyer requests and feedback into improved versions.Prepare paid-readiness metadata and finance-review details before real paid usage launches.
Supplier trust is part of discovery

Every marketplace card links to the supplier behind the skill. The public directory lets teams compare profile state, verified listings, public review status, adoption evidence, and runtime evidence before adopting.

Browse publishers
Verified skill adoption path

The marketplace keeps a gated path after sign-in.

A useful skill registry is not finished when an agent copies a command. Verified skills can move into project policy and runtime evidence; submitted skills stay inspection-only until review passes.

Schema + Runtime + Human
Callable skills1
Recorded calls0
Feedback signals0
Submitted skills1
Public contract
Inspect

Manifest, permissions, runtime, pricing intent, and publisher profile are visible before adoption.

Project gate
Adopt

Signed-in teams attach a verified skill to a project key or MCP server with explicit policy context.

Runtime evidence
Invoke

Verified runtime calls carry typed input, project policy checks, success signals, and reviewable output.

Retention loop
Return

Feedback, incidents, changelog updates, and paid-readiness blockers create the next publisher action.

Example skill requests - not live data

These are example demand scenarios for the future paid marketplace. Live buyer requests stay empty until real users submit them.

Figma change request to Linear issueNot liveExample state: Open | 7 days
Sample budget$600
Shopify product operations skillNot liveExample state: Spec review | 12 days
Sample budget$900
Slack incident summarizerNot liveExample state: Matched | 5 days
Sample budget$450
Publisher review path
01Draft manifest
02Runtime checks
03Human review
04Paid-readiness metadata
05Public listing
06Prelaunch ledger model
07Future paid review
Launch requirements
ManifestTyped input/output, runtime, permissions, version, author.
SecurityPermission classification, runtime checks, secret handling, data retention.
MoneyPrelaunch commission and ledger model; no general payment capture.
SupportChangelog, deprecation policy, issue channel, response expectations.

Found the right skill?

Sign up for a developer account to start integrating, or browse the publisher directory.

Developer workspacePublisher directory