← Back to Skills Marketplace
Stringclaw
by
Oscar W. Halland
· GitHub ↗
· v0.0.9
371
Downloads
0
Stars
0
Active Installs
9
Versions
Install in OpenClaw
/install stringclaw
Description
Make real phone calls via Stringclaw. Use when the user says 'call me', 'give me a call', 'phone me', or wants to talk by voice. Initiates an outbound voice...
Usage Guidance
This skill appears to do what it says (install a bridge and place outbound calls), but exercise caution before installing. Key points to consider:
- The npm package @stringclaw/bridge is the only install step; verify its source, maintainer, and code before installing (no homepage/source is provided in the skill metadata).
- The instructions will change OpenClaw gateway settings and create a voice agent; these are global changes that affect your environment—make sure you want that.
- The bridge is started with the OpenClaw gateway token set in its environment; the skill reads that token from your OpenClaw config but did not declare it as a required credential. Confirm you are comfortable with a third-party binary/process getting that token.
- Review the npm package contents (or run in an isolated/test environment) and check logs (/tmp/stringclaw-bridge.log) during initial runs.
- If you need lower risk, ask the author for a homepage/source repository and a minimal install artifact you can audit, or request that the skill declare any local secrets/config paths it reads.
Capability Analysis
Type: OpenClaw Skill
Name: stringclaw
Version: 0.0.9
The 'stringclaw' skill is designed to enable outbound voice calls by bridging the OpenClaw agent with the Stringclaw service. The instructions in SKILL.md guide the agent through configuring the local OpenClaw gateway, generating an authentication token, and running a bridge process (installed via the @stringclaw/bridge npm package). The behavior is consistent with the stated purpose of the skill, and the security configurations (like setting a random hex token for the gateway) are standard practices for local service integration.
Capability Assessment
Purpose & Capability
Name, description, required binary (stringclaw-bridge) and required env var (STRINGCLAW_API_KEY) align with a bridge-based outbound-calling capability. The install (npm @stringclaw/bridge -> stringclaw-bridge) is consistent with the declared purpose.
Instruction Scope
The runtime instructions modify global OpenClaw gateway configuration (enable chatCompletions, set gateway.mode, set gateway.auth.mode) and create a voice agent. They also instruct reading the gateway auth token from OpenClaw config and writing it into the environment for the bridge. Those actions are operationally necessary for the bridge but are system-wide changes and involve reading a local secret (gateway token) that is not listed in the skill's declared requirements.
Install Mechanism
Installation is via an npm package (@stringclaw/bridge) which is a normal distribution mechanism but carries the usual moderate risk of running third-party JavaScript. There is no homepage or source listed in metadata, so you cannot easily inspect the package upstream before install.
Credentials
The skill declares only STRINGCLAW_API_KEY as a required credential (reasonable). However, the instructions read and rely on the OpenClaw gateway auth token (created or read via openclaw config) which is a local secret not declared in requires.env or required config paths. The bridge is started with that token in its environment, meaning the bridge process will have access to the gateway token.
Persistence & Privilege
The skill does not request always:true, but its instructions modify global OpenClaw gateway settings and create an agent (system-wide changes). Those modifications may be required for functionality but should be made consciously since they affect the whole agent environment.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install stringclaw - After installation, invoke the skill by name or use
/stringclaw - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.0.9
stringclaw 0.0.9 streamlines setup instructions:
- Simplified and updated setup steps using new openclaw config commands for gateway and authentication.
- Rewrote agent creation instructions to use a one-line CLI command.
- Combined troubleshooting and requirements for easier reference.
- Clarified guidance for reading tokens and handling call errors.
- Enhanced description and output/error documentation for greater clarity.
v0.0.8
- Added required setup instructions for an OpenClaw "voice" agent to handle calls.
- Updated usage steps to include creation and configuration of the "voice" agent before making calls.
- Clarified troubleshooting for chat completions not enabled (now notes HTTP 405 error).
- Example interactions revised to include new agent setup step.
- Version bumped to 0.0.8.
v0.0.7
Expanded setup instructions with new requirements for the OpenClaw gateway token and chat completions endpoint.
- Added steps to obtain and configure the OpenClaw gateway token.
- Included guidance for enabling chat completions in the OpenClaw config.
- Updated bridge startup instructions to require gateway token and URL environment variables.
- Expanded troubleshooting section with solutions for common errors related to gateway and bridge connectivity.
- Clarified error messages and example usage to cover new configuration steps.
v0.0.6
- Clarified that the Stringclaw bridge creates a secure tunnel and must show "Bridge ready" before calls.
- Updated call preparation instructions: start the bridge with `stringclaw-bridge serve &` and wait 5 seconds.
- Added a new possible error: `"Bridge is not running. Start it with: stringclaw-bridge serve"`.
- Improved the step-by-step example to reflect updated setup and error handling.
v0.0.5
- Added a section on model requirements for voice calls, specifying recommended fast models for natural conversation.
- Instructs users to ensure they are running a sufficiently fast model, or to ask the user to switch if not.
v0.0.4
- Updated setup instructions to use the `stringclaw-bridge` CLI directly instead of an HTTP API.
- Changed process check and launch commands to use `stringclaw-bridge serve`.
- Calls are now made using the CLI (`stringclaw-bridge call`) with phone number configured in the Stringclaw dashboard.
- Error handling and example responses are now based on CLI output (JSON on stderr).
- Clarified prerequisite and error messaging for users with no configured phone number.
v0.0.3
- Updated the Stringclaw API endpoint URL in instructions.
- Changed error messaging: "Insufficient credits" is now "No minutes remaining," and responses reflect this update.
v0.0.2
- Moved the install instructions for the Stringclaw bridge from top-level to under the "metadata.openclaw" section in SKILL.md.
- No functional changes to skill usage or API documentation.
v0.0.1
Initial release of stringclaw.
- Make real phone calls to users via Stringclaw voice AI.
- Requires running the Stringclaw bridge locally and an API key.
- Supports calling specified phone numbers or defaults to user's configured number.
- Handles success and error responses, including insufficient credits and missing information.
Metadata
Frequently Asked Questions
What is Stringclaw?
Make real phone calls via Stringclaw. Use when the user says 'call me', 'give me a call', 'phone me', or wants to talk by voice. Initiates an outbound voice... It is an AI Agent Skill for Claude Code / OpenClaw, with 371 downloads so far.
How do I install Stringclaw?
Run "/install stringclaw" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Stringclaw free?
Yes, Stringclaw is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Stringclaw support?
Stringclaw is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Stringclaw?
It is built and maintained by Oscar W. Halland (@oscarwoha); the current version is v0.0.9.
More Skills