Quickstart

1. Browse public Skills

Use Marketplace or Registry to find a Skill by category, runtime, verification state, permissions, or publisher.

2. Inspect the manifest

Open the manifest before installation. Check schema, runtime, permissions, version, examples, and review state.

3. Create a Project Key

Sign in, create a project, and issue a scoped key for approved runtime calls.

4. Call the REST API

Invoke the Skill through the runtime endpoint with Authorization: Bearer PROJECT_KEY and a typed input payload.

5. Configure MCP

Add SkillHub MCP to your Agent workbench so approved Skills appear as callable tools.

6. Review logs

Check runtime logs, policy blocks, rate limits, and preview billing signals after test calls.

Before you start

Choose one low-risk workflow first, such as SEO page review, listing QA, CSV cleanup, or support ticket summary. Avoid customer secrets and production writes during the first test.

• Pick a verified or low-risk Skill.
• Use sample or redacted data for the first invocation.
• Decide who reviews the output before it reaches customers or internal systems.

First REST test

A first REST test should prove that authentication, input schema, response shape, policy checks, and logs all work before you automate anything.

• Send Authorization: Bearer PROJECT_KEY from a trusted environment.
• Use a payload that exactly matches the Skill manifest.
• Save the returned invocation id and verify it appears in logs.

First MCP test

A first MCP test should show that the Agent workbench can discover approved tools, read tool descriptions, and call only the Skills allowed by project policy.

• Confirm the tool list shows only approved project Skills.
• Check that tool names and descriptions are understandable to both humans and Agents.
• Trigger one safe call and verify the policy decision and result.

Common setup problems

Most early failures come from missing Project Keys, wrong environment variables, schema mismatch, policy blocks, or calling a preview-only Skill as if it were production-ready.

• 401 or 403: check login state, Project Key scope, and project membership.
• 422: compare your payload with the manifest input schema.
• 429: slow down retries and check project rate limits.
• Preview block: confirm the Skill review state and paid-readiness boundary.