Read the Skill contract,then let agents run.
This page explains the production path for SkillHub: discover public Skills, inspect the Skill API contract, install a verified version into a project, create a scoped Project Key, then invoke REST or MCP through the governed runtime gateway.
Docs map
Use this page as an operating sequence.
Start with the public listing, move to the contract, then create project state only when the Skill is worth adopting. That order keeps agents, developers, and operators aligned.
Find Skills
For operators, marketers, founders, and AI agents comparing reusable capabilities before adoption.
- Search by task
- Compare publisher and risk
- Open public detail
Skill API
For developers and agents reading schemas, permission boundaries, runtime type, and review state.
- Read manifest
- Check endpoint
- Confirm review status
Workspace runtime
For teams installing verified Skills, creating Project Keys, and running governed calls.
- Choose project
- Pin version
- Invoke REST or MCP
Publisher flow
For authors packaging skillhub.json, submitting exact versions, and responding to review evidence.
- Prepare manifest
- Run preflight
- Submit version
- You know which surface answers the current question.
- You can explain what is public inspection and what is project-gated runtime.
- You have a stable next step before copying any token or key.
Find the right Skill first
Compare public Skills before adoption. Look at task fit, publisher trust, runtime type, and review state.
Verified public contract with examples and MCP metadata.
Checks CRM records before enrichment workflows run.
Routes support tickets with project policy attached.