Skills ask-claude

install

source · Clone the upstream repo

git clone https://github.com/openclaw/skills

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

T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/0xmanel/ask-claude-skill" ~/.claude/skills/clawdbot-skills-ask-claude && rm -rf "$T"

manifest: skills/0xmanel/ask-claude-skill/SKILL.md

source content

Ask Claude — Execute & Report (with persistent sessions)

The Two Modes

New session (default)

Use when starting a fresh task or new topic.

OUTPUT=$(/home/xmanel/.openclaw/workspace/run-claude.sh "prompt" "/workdir")
echo "$OUTPUT"

Continue session (--continue)

Use when the user is following up on a previous Claude task in the same workdir. Claude Code will have full memory of what was done before — files read, edits made, context gathered.

OUTPUT=$(/home/xmanel/.openclaw/workspace/run-claude.sh --continue "prompt" "/workdir")
echo "$OUTPUT"

When to use --continue

Use

--continue

when the user says things like:

"agora corrige o que encontraste"
"continua"
"e o ficheiro X?"
"faz o mesmo para..."
"e agora?"
"ok, e o erro de..."
Anything that clearly references what Claude just did

Use a new session when:

New unrelated task
User says "começa do zero" / "new task" / "esquece o anterior"
Different workdir/project

Session storage

Claude Code stores sessions per-directory in

~/.claude/projects/

. As long as you use the same

workdir

--continue

picks up exactly where it left off — same file context, same conversation history, same edits.

Direct command (alternative to wrapper)

# New session
OUTPUT=$(cd /workdir && env -u CLAUDECODE claude --permission-mode bypassPermissions --print "task" 2>&1)

# Continue session
OUTPUT=$(cd /workdir && env -u CLAUDECODE claude --permission-mode bypassPermissions --print --continue "task" 2>&1)

Common workdirs

Context	Workdir
General/scripts	`/home/xmanel/.openclaw/workspace`
Trading	`/home/xmanel/.openclaw/workspace/hyperliquid`

After receiving output

Summarize in 1-3 lines what Claude did/found
Mention files created or edited
If error: analyze and suggest fix
If output is long: summarize, offer full output on request