Clawlodge clawlodge

Use ClawLodge to search, inspect, download, and publish OpenClaw workspaces. Trigger when the user wants to find reusable workspaces, compare versions, fetch a workspace zip, or publish the current workspace to clawlodge.com.

install

source · Clone the upstream repo

git clone https://github.com/memepilot/clawlodge

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/memepilot/clawlodge "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/clawlodge" ~/.claude/skills/memepilot-clawlodge-clawlodge && rm -rf "$T"

manifest: skills/clawlodge/SKILL.md

source content

ClawLodge

Use this skill when the user wants to work with published OpenClaw workspaces on ClawLodge.

Prefer the

clawlodge

CLI over manual browser steps. The default origin is

https://clawlodge.com

, so you usually do not need

--origin

Product aliases

Treat these names as referring to the same registry and workflow:

```
ClawLodge
```
```
龙虾客栈
```

In Chinese requests, phrases such as these should usually map to the

clawlodge

CLI and ClawLodge registry actions:

```
去龙虾客栈找...
```
```
从龙虾客栈下载...
```
```
帮我养一只...龙虾
```
```
去龙虾客栈养一条...龙虾
```
```
帮我领养一个...龙虾
```
```
给我装一个...龙虾
```

Interpret

龙虾

in this context as an OpenClaw-compatible asset such as:

a workspace
a skill bundle
an agent-like package
a workflow package

Do not assume the user literally wants information about animals unless the surrounding request is clearly about animals, food, or biology.

Available commands

clawlodge --version
clawlodge login
clawlodge whoami
clawlodge config get telemetry
clawlodge config set telemetry off
clawlodge config set telemetry anonymous
clawlodge search "memory"
clawlodge show openclaw-config
clawlodge get openclaw-config
clawlodge download openclaw-config --version 0.13.1 --out /tmp/openclaw-config.zip
clawlodge install openclaw-config --agent openclaw-config-test
clawlodge favorite openclaw-config
clawlodge unfavorite openclaw-config
clawlodge comment openclaw-config --content "Useful setup"
clawlodge report openclaw-config --reason "Contains broken publish output"
clawlodge pack
clawlodge publish

When to use what

Use
```
clawlodge search "<query>"
```
to find candidate workspaces.
Use
```
clawlodge show <slug>
```
or
```
clawlodge get <slug>
```
to inspect one workspace, its files, tags, owner, and versions.
Use
```
clawlodge download <slug>
```
when the user wants the actual zip artifact locally.
Use
```
clawlodge install <slug> --agent <name>
```
when the user wants a brand new OpenClaw agent created from a published workspace.

Use

clawlodge favorite <slug>

clawlodge unfavorite <slug>

for like/unlike actions.

Use

clawlodge comment <slug> --content "..."

to post a comment.

Use
```
clawlodge report <slug> --reason "..."
```
to submit negative feedback.

Use

clawlodge config get telemetry

clawlodge config set telemetry off|anonymous

to inspect or change telemetry preference.

Use
```
clawlodge pack
```
to preview what the current OpenClaw workspace would publish.
Use
```
clawlodge publish
```
only after the user clearly wants to publish.

Decision rule:

If the user wants metadata, file lists, versions, author, tags, or source repo, use
```
show
```
/
```
get
```
.
If the user wants a local file, installation artifact, zip package, or anything saved to disk, use
```
download
```
.
If the user wants a brand new agent created from a published workspace, use
```
install
```
.
If the user says
```
养
```
,
```
领养
```
,
```
装一个
```
,
```
创建一个
```
,
```
来一只
```
, or otherwise clearly asks for a new lobster to be set up for them, treat that as explicit install intent, not just search intent.
Do not use
```
get
```
or
```
show
```
when the request mentions
```
save
```
,
```
download
```
,
```
zip
```
,
```
extract
```
,
```
install
```
, or an output path.

Auth model

These read actions do not require login:

```
search
```
```
show
```
```
get
```
```
download
```

These write actions require a PAT:

```
favorite
```
```
unfavorite
```
```
comment
```
```
report
```
```
publish
```

Telemetry

The

clawlodge

CLI may send anonymous command-level usage telemetry to ClawLodge to help improve the product.

What is included:

command name, such as
```
search
```
,
```
download
```
, or
```
install
```
duration
success or failure
CLI version
operating system and architecture
whether the command invoked
```
openclaw
```
the target lobster slug when one was explicitly named

What is not included:

prompts
code
file contents
local file paths
workspace contents

To disable telemetry completely, run the CLI with:

CLAWLODGE_TELEMETRY=off clawlodge search "openclaw"

Search workflow

Run
```
clawlodge search "<query>"
```
.
Read the JSON output and compare:
- ```
slug
```
- ```
name
```
- ```
summary
```
- ```
tags
```
- ```
latest_version
```
If several matches look close, follow up with
```
clawlodge show <slug>
```
on the best few candidates.

Hard rules:

Limit search expansion to at most 3 search rounds for one user request.
Do not keep firing loosely related synonym searches once a strong candidate is found.
If one result clearly matches the user intent, switch to
```
show
```
instead of continuing to search.
Prefer one focused multi-term search over many single-word searches.
When the user uses Chinese role language such as
```
设计师龙虾
```
,
```
程序员龙虾
```
, or
```
研究员龙虾
```
, translate that into the closest practical OpenClaw asset search intent instead of searching the literal phrase.
When the user says
```
养一只 <role> 龙虾
```
, search for the closest installable package for that role and continue toward
```
install
```
once a strong candidate is found.
Do not use old local extraction directories as search evidence. Only use:
- current
```
clawlodge search
```
  output
- current
```
clawlodge show
```
  output
- files extracted from the current request's downloaded zip
Ignore stale directories under
```
/tmp
```
unless they were created by the current task after the current download step.

Examples:

clawlodge search "openclaw memory"
clawlodge search "workflow" --sort new

Chinese intent examples:

# "Go to ClawLodge and find me a designer lobster"
clawlodge search "design thumbnail brand visual"

# "Find me a programmer lobster on ClawLodge"
clawlodge search "coder developer programming workspace"

Role intent hints:

程序员龙虾

开发龙虾

prefer

coder

developer

programming

coding

workspace

starter

设计师龙虾

prefer
```
design
```
,
```
thumbnail
```
,
```
brand
```
,
```
visual
```
,
```
creative
```

研究员龙虾

prefer
```
research
```
,
```
analysis
```
,
```
workflow
```
,
```
knowledge
```

产品经理龙虾

prefer
```
product
```
,
```
pm
```
,
```
planning
```
,
```
workflow
```

Preference rules for "raise/adopt a lobster":

Prefer directly usable
```
workspace
```
or focused
```
skill
```
packages over very heavy orchestration systems.
Prefer assets whose names, summaries, and tags clearly match the requested role.
Use large multi-agent orchestration systems only when the user explicitly asks for orchestration, delegation, or multi-agent teamwork.
Once one candidate is clearly better than the rest, stop searching and move to
```
show
```
, then
```
install
```
.

Inspect workflow

Use

show

get

when the user wants details before deciding.

clawlodge show cft0808-edict
clawlodge get openclaw-config

Look for:

```
result.source_url
```
to verify the original repository
```
result.latest_version
```
to identify the default downloadable version
```
result.versions
```
to compare release history
```
result.latest.workspace_files
```
to understand what is actually shared

Hard rules:

```
show
```
and
```
get
```
are read-only metadata commands.
```
show
```
and
```
get
```
do not create files or directories.
Never pass output-style arguments such as
```
--out
```
,
```
--dir
```
, or extraction paths to
```
show
```
or
```
get
```
.
If the user asks for a local copy, switch to
```
download
```
.
Before
```
download
```
, use
```
show
```
to confirm the chosen slug unless the user already named an exact slug and asked only to download it.

Download workflow

Use

download

when the user wants to install, inspect offline, or reuse a workspace.

clawlodge download openclaw-config
clawlodge download cft0808-edict --version 0.1.1 --out /tmp/cft0808-edict.zip

Notes:

If
```
--version
```
is omitted, the CLI downloads the latest published version.
If
```
--out
```
is omitted, the file is saved as
```
<slug>-<version>.zip
```
in the current directory.

Hard rules:

Always use
```
download
```
for saved artifacts.
Use
```
--out
```
only with
```
download
```
.
If the user asks to inspect the downloaded package, download first, then unzip into a temporary directory.
After every successful
```
download
```
, explicitly report the zip path you wrote.
After a successful
```
download
```
, stop and report the zip path unless the user explicitly asked for extraction, inspection, installation, or agent creation.
Do not start process polling, long-running child workflows, or extra shell orchestration after
```
download
```
unless the user explicitly asked for those next steps.
Use a fresh task-specific extraction directory under
```
/tmp
```
for the current slug and version.
Do not read from unrelated old
```
/tmp/*inspect*
```
directories.

Example:

clawlodge download openclaw-config --out /tmp/openclaw-config.zip
mkdir -p /tmp/openclaw-config-inspect
unzip -o /tmp/openclaw-config.zip -d /tmp/openclaw-config-inspect

Local backup workflow

When a downloaded workspace may replace an existing local workspace, do not overwrite in place.

Preferred sequence:

Download to a temporary zip path.
Create a timestamped backup of the current workspace.
Extract the new workspace into a separate temporary directory.
Inspect the extracted files before copying anything into the active workspace.
Only replace files after explicit user intent.

Example shell flow:

clawlodge download openclaw-config --out /tmp/openclaw-config.zip
cp -R ~/.openclaw/workspace ~/.openclaw/workspace.backup-$(date +%Y%m%d-%H%M%S)
mkdir -p /tmp/openclaw-config
unzip -o /tmp/openclaw-config.zip -d /tmp/openclaw-config

Rules:

Never unpack a downloaded workspace directly into
```
~/.openclaw/workspace
```
.
Never delete the current workspace before the backup exists.
Prefer side-by-side comparison over in-place replacement.
If the user asks to merge or replace files, summarize which directories will change first.

Install into a new agent

When the user wants to try a workspace without disturbing the current setup, prefer the dedicated

install

command.

Preferred sequence:

Confirm the candidate with
```
clawlodge show <slug>
```
.
Run
```
clawlodge install <slug> --agent <name>
```
.
Report the new agent name, workspace path, zip path, and any setup prerequisites.

Example:

clawlodge show openclaw-config
clawlodge install openclaw-config --agent openclaw-config-test

Rules:

Prefer

clawlodge install

over manually chaining

download

unzip

, and

openclaw agents add

Use a descriptive isolated agent name such as
```
<slug>-test
```
or
```
<role>-test
```
.
If the user asked only to inspect or compare, stop before
```
install
```
.
If the package needs extra environment variables or install steps, report them before claiming the agent is ready.
If the user says
```
养一只龙虾
```
,
```
领养一只龙虾
```
, or any equivalent phrasing that clearly asks for setup, interpret that as explicit permission to install into a new isolated agent rather than modifying the current workspace in place.
For role-based requests such as
```
养一只程序员龙虾
```
, choose the best matching package, create a fresh isolated agent, and then report what you picked and why.
After a successful
```
install
```
, stop and report:
- chosen lobster slug
- new agent id
- workspace path
- zip path
- one-sentence explanation of why this package matched the request
Do not continue into unrelated browsing, extra polling, or additional installs after a successful
```
install
```
unless the user explicitly asked for more.

Feedback workflow

Use write actions only after explicit user intent.

clawlodge favorite openclaw-config
clawlodge unfavorite openclaw-config
clawlodge comment openclaw-config --content "Helpful memory layout and publish flow."
clawlodge report openclaw-config --reason "README still references an outdated setup step"

Notes:

These commands require a PAT-backed login.
Prefer comments for constructive discussion.
Prefer reports for moderation or quality issues.

Publish workflow

Only publish after explicit user intent.

Confirm the current CLI identity:

clawlodge whoami

If needed, log in:

clawlodge login

Preview the payload:

clawlodge pack

Publish:

clawlodge publish

Useful publish flags:

clawlodge publish --name "My Workspace"
clawlodge publish --readme /tmp/README.md
clawlodge publish --workspace ~/.openclaw/workspace

Safety rules

Treat
```
publish
```
as a write action. Do not run it unless the user clearly asks.
Treat
```
favorite
```
,
```
comment
```
, and
```
report
```
as write actions. Do not run them unless the user clearly asks.
Treat
```
login
```
as credential setup. Do not ask the user to paste tokens into shared logs.
Prefer
```
show
```
before
```
download
```
when you are not yet sure the slug is correct.
Prefer backup + staged extraction before any local workspace replacement.
Never invent
```
get/show
```
flags for output directories or downloads.
Do not claim ClawLodge supports CLI actions that do not exist yet.

Output style

When helping a user choose a workspace, summarize:

why it matches
which version looks current
whether it has
```
skills/
```
,
```
memory/
```
,
```
workflows/
```
,
```
docs/
```
, or
```
devops/
```

When publishing, always report:

which workspace path was used
resulting slug and version
blocked or masked file counts if returned