Skip to content

README.md

Latest commit

 

History

History
45 lines (33 loc) · 1.57 KB

README.md

File metadata and controls

45 lines (33 loc) · 1.57 KB

OpenClaw example

OpenClaw already has native plugin and skills surfaces. This folder shows the truthful OpenVibeCoding position inside that ecosystem.

Start here

  1. Use the compatible bundle at:

    examples/coding-agents/plugin-bundles/openvibecoding-coding-agent-bundle/

    That bundle now includes skills/openvibecoding-adoption-router/manifest.yaml, so the same repo-owned skill already has ClawHub-style metadata and a matching live ClawHub skill listing, even though this local starter itself is not a published OpenClaw plugin listing.

  2. Pair it with one of the tracked OpenClaw MCP/config examples:

    examples/coding-agents/openclaw/openvibecoding-server.json
examples/coding-agents/openclaw/config.openclaw.example.toml

  3. Keep OpenVibeCoding on the proof / replay / read-only integration side unless a native published OpenClaw path is explicitly shipped and tested.

Expected success

  • the OpenClaw config resolves to your local OpenVibeCoding checkout and the same read-only MCP server
  • the proof target is still the public proof-first loop in docs/use-cases/index.html, not a claim that you are already live on ClawHub
  • the final wording stays bundle-compatible or starter-ready, not published OpenClaw plugin

Boundary

  • This is a compatible local bundle example plus tracked local MCP/config objects, not a published ClawHub item.
  • It helps OpenClaw workflows reuse OpenVibeCoding skills and read-only MCP.
  • It does not upgrade OpenVibeCoding into a hosted operator or write-capable MCP product.