Developer workspace

Manage the skills your agents use.

A focused workspace for teams that install and run skills inside agent projects: create projects, watch keys and budgets, open buyer requests, and keep billing ready.

Developer install journey

The developer path proves SkillHub is more than a directory: discovery becomes project install state, runtime governance, logs, cost, and updates.

CurrentDeveloper workspaceNextProject command
  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.
Open project
Developer evidence chain

A copied install command becomes controlled project state.

A developer should see how discovery turns into project policy, project keys, governed invocation, cost, updates, and runtime evidence.

Projects0
Installed skills0
Runtime calls0
Monthly budget$0
Live rows stay live: empty production data is shown as empty, not replaced by demo supply.
Workspace session
Sign in
Environment fallbackservice
Roleservice / super_admin / admin / finance
Tokence32e4...addf
Current session

Developer workspace access

Developer operations cover projects, installs, runtime keys, project policy, governed tests, billing readiness, team access, notifications, and webhooks.

Workspace readyOpen account
OrganizationServer fallback
Current rolesservice / super_admin / admin / finance / reviewer / publisher / developer / owner
Required rolesdeveloper / owner / admin / super_admin
Session tokence32e4...addf
API actions remain role-enforcedThis panel explains access before a user clicks a control. The gateway still enforces organization membership and role checks for every write.
Projects0
Installed skills0
Runtime calls0
Monthly budget$0
Developer operations queue

What should the agent team handle next?

The developer workspace should behave like an operating queue: project setup, runtime keys, installs, approvals, updates, billing, notifications, team access, and webhooks all point to one next move.

Create project
Projects0
Key gaps0
Install gaps0
Runtime watch0
Unread inbox0
Agent project operations
New agent project
ProjectInstalledKeysBudgetRuntime / next step
No developer projects yet. Create a project to start installing and approving skills.
Developer request board
My buyer requests0
No buyer requests opened by this workspace.