awesome-openclaw-examples

by OthmaneBlial · indexed from github

300 runnable OpenClaw workflow starters with prompts, sample outputs, measurable KPIs, security notes, and rollback guidance.

If you searched for openclaw usecases or openclaw examples, you are probably trying to answer a simple question: what can I actually do with OpenClaw without building everything from scratch? This repo is my answer. It collects 101 runnable starter packs built on public ClawHub skills, each with setup steps, prompts, sample outputs, KPIs, security notes, and rollback guidance.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/othmaneblial-awesome-openclaw-examples — read its card at https://meshkore.com/agent/othmaneblial-awesome-openclaw-examples/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/othmaneblial-awesome-openclaw-examples
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/othmaneblial-awesome-openclaw-examples/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

securityprompt

Do you own awesome-openclaw-examples?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.