claw
Skill1 starsChanged 6 months agoMITView on GitHub
Install the claw CLI tool — run ClawBridge agent containers from the command line without opening a chat app.
- Reads credentials
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- microsoft/amplifier-app-nanoclawedited, first seen Jun 12, 2026
- TheKREATORS/my-claude-skillstheir own version, first seen Mar 19, 2026
- mateffy/claw.eventstheir own version, first seen Feb 6, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- microsoft/amplifier-app-nanoclaw★ 589% same
Wrote their own version · 2
- mateffy/claw.events★ 4same name
- TheKREATORS/my-claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- container/AGENTS.mdAGENTS.md
- add-atomic-chat-toolSkill
- add-dashboardSkill
- add-discordSkill
- add-emacsSkill
- add-gcal-toolSkill
- add-gchatSkill
- add-githubSkill
- add-gmail-toolSkill
- add-imessageSkill
- add-karpathy-llm-wikiSkill
- add-linearSkill
- add-macos-statusbarSkill
- add-matrixSkill
- add-ollama-providerSkill
- add-ollama-toolSkill
- add-parallelSkill
- add-resendSkill
- add-signalSkill
- add-slackSkill
- add-teamsSkill
- add-telegramSkill
- add-vercelSkill
- add-webexSkill
- add-wechatSkill
- add-whatsapp-cloudSkill
- add-whatsappSkill
- convert-to-apple-containerSkill
- customizeSkill
- debugSkill
- get-qodo-rulesSkill
- init-first-agentSkill
- manage-channelsSkill
- manage-mountsSkill
- migrate-from-openclawSkill
- migrate-clawbridgeSkill
- qodo-pr-resolverSkill
- setupSkill
- update-clawbridgeSkill
- update-skillsSkill
- x-integrationSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Default target is the main group (no -g needed for most use)
- Very specific: line 15
Read prompts from stdin (--pipe) for scripting and piping
- Distinctive: line 29
Run this skill from within the ClawBridge directory.
- Very specific: line 46
Make sure ~/bin is in PATH.
- Very specific: line 119
Run claw --list-groups to see what's registered.
- Very specific: line 127
If claw can't find your database or .env, set the CLAWBRIDGE_DIR environment variable:
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
claw — ClawBridge CLI
claw is a Python CLI that sends prompts directly to a ClawBridge agent container from the terminal. It reads registered groups from the ClawBridge database, picks up secrets from .env, and pipes a JSON payload into a container run — no chat app required.
What it does
- Send a prompt to any registered group by name, folder, or JID
- Default target is the main group (no
-gneeded for most use) - Resume a previous session with
-s <session-id> - Read prompts from stdin (
--pipe) for scripting and piping - List all registered groups with
--list-groups - Auto-detects
containerordockerruntime (or override with--runtime) - Prints the agent's response to stdout; session ID to stderr
- Verbose mode (
-v) shows the command, redacted payload, and exit code
Prerequisites
- Python 3.8 or later
- ClawBridge installed with a built and tagged container image (
clawbridge-agent:latest) - Either
container(Apple Container, macOS 15+) ordockeravailable inPATH
Install
Run this skill from within the ClawBridge directory. The script auto-detects its location, so the symlink always points to the right place.
1. Copy the script
mkdir -p scripts
cp "${CLAUDE_SKILL_DIR}/scripts/claw" scripts/claw
chmod +x scripts/claw2. Symlink into PATH
mkdir -p ~/bin
ln -sf "$(pwd)/scripts/claw" ~/bin/clawMake sure ~/bin is in PATH. Add this to ~/.zshrc or ~/.bashrc if needed:
export PATH="$HOME/bin:$PATH"Then reload the shell:
source ~/.zshrc # or ~/.bashrc3. Verify
claw --list-groupsYou should see registered groups. If ClawBridge isn't running or the database doesn't exist yet, the list will be empty — that's fine.
Usage Examples
# Send a prompt to the main group
claw "What's on my calendar today?"
# Send to a specific group by name (fuzzy match)
claw -g "family" "Remind everyone about dinner at 7"
# Send to a group by exact JID
claw -j "120363336345536173@g.us" "Hello"
# Resume a previous session
claw -s abc123 "Continue where we left off"
# Read prompt from stdin
echo "Summarize this" | claw --pipe -g dev
# Pipe a file
cat report.txt | claw --pipe "Summarize this report"
# List all registered groups
claw --list-groups
# Force a specific runtime
claw --runtime docker "Hello"
# Use a custom image tag (e.g. after rebuilding with a new tag)
claw --image clawbridge-agent:dev "Hello"
# Verbose mode (debug info, secrets redacted)
claw -v "Hello"
# Custom timeout for long-running tasks
claw --timeout 600 "Run the full analysis"Troubleshooting
"neither 'container' nor 'docker' found"
Install Docker Desktop or Apple Container (macOS 15+), or pass --runtime explicitly.
"no secrets found in .env"
The script auto-detects your ClawBridge directory and reads .env from it. Check that the file exists and contains at least one of: CLAUDE_CODE_OAUTH_TOKEN, ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN.
Container times out
The default timeout is 300 seconds. For longer tasks, pass --timeout 600 (or higher). If the container consistently hangs, check that your clawbridge-agent:latest image is up to date by running ./container/build.sh.
"group not found"
Run claw --list-groups to see what's registered. Group lookup does a fuzzy partial match on name and folder — if your query matches multiple groups, you'll get an error listing the ambiguous matches.
Container crashes mid-stream
Containers run with --rm so they are automatically removed. If the agent crashes before emitting the output sentinel, claw falls back to printing raw stdout. Use -v to see what the container produced. Rebuild the image with ./container/build.sh if crashes are consistent.
Override the ClawBridge directory
If claw can't find your database or .env, set the CLAWBRIDGE_DIR environment variable:
export CLAWBRIDGE_DIR=/path/to/your/clawbridgeDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

