agentleFS
mcarmona1064-cellmcarmona1064-cell/clawbridge-codex/.claude/skills/claw/SKILL.md

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

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
  1. Very specific:

    Default target is the main group (no -g needed for most use)

    line 13
  2. Very specific:

    Read prompts from stdin (--pipe) for scripting and piping

    line 15
  3. Distinctive:

    Run this skill from within the ClawBridge directory.

    line 29
  4. Very specific:

    Make sure ~/bin is in PATH.

    line 46
  5. Very specific:

    Run claw --list-groups to see what's registered.

    line 119
  6. Very specific:

    If claw can't find your database or .env, set the CLAWBRIDGE_DIR environment variable:

    line 127

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 -g needed 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 container or docker runtime (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+) or docker available in PATH

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/claw

2. Symlink into PATH

mkdir -p ~/bin
ln -sf "$(pwd)/scripts/claw" ~/bin/claw

Make 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 ~/.bashrc

3. Verify

claw --list-groups

You 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/clawbridge

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.