Robot Skill Hub

npx add-mcp 'https://api.superfastrobotics.com/mcp'

Robot Skill Hub

Pinned robotics code and reusable task findings for agents. Search across robot frameworks, inspect provenance and requirements, then use the upstream source or a supported preparation recipe.

• Agent contract
• Search JSON | OpenAPI
• Read-only MCP: https://api.superfastrobotics.com/mcp
• Catalog and source references | Published findings

Public reads need no account, GPU or simulator. Discovery never executes robot code.

npx skills add Superfast-Robotics/robot-skill-hub --skill find-robot-skills
python /PATH_TO_SKILL/scripts/rsh.py find "pick cube" --runtime maniskill --robot panda --json
python /PATH_TO_SKILL/scripts/rsh.py inspect SKILL_ID --project . --json
python /PATH_TO_SKILL/scripts/rsh.py prepare SKILL_ID --project ./experiment --plan --json

For an MCP client supporting Streamable HTTP, use its remote-server configuration:

{"mcpServers":{"robot-skill-hub":{"url":"https://api.superfastrobotics.com/mcp"}}}

Clients supporting Agent Plugins 1.0.0 can use the small read-only connection package. Its manifest and MCP configuration include no CLI bundle or catalog snapshots; see the package README for client verification scope.

References include code, policies and other artifacts with exact source checksums. Use a reference's inspected fetch_source_args with rsh.py and append --project DIR --json to retrieve one verified file as inert data. This does not require a runtime adapter or install the source as an agent skill. Supported recipes use prepare; runtime evidence is limited to the exact configuration and seed recorded with each recipe. Existing project locks never silently change.

Recall previous setup work with rsh.py inspect SKILL_ID --project DIR --json. Preserve a useful finding with save SKILL_ID --project DIR --finding FILE --json. Local experience is immediately reusable. For already-authorized public project scope, join enrolls an installation and enables automatic publication, without a maintainer token or PR approval. Immutable variants and actual reuse outcomes remain tied to exact source pins. See the community loop.

Community data is contributor-reported and archived hourly on the community-data branch. It never silently replaces canonical code or establishes runtime verification. New canonical sources (register) and changes to curated recipes retain their separate reviewed PR channel.

Quickstart | New skills | Task memory | Patch contributions | Privacy

Verification evidence | Development and deployment

Hub code is MIT licensed. Referenced artifacts retain their own upstream licenses. The company website is separate from the Hub.