← Back to Skills Marketplace
Pincer
by
panzacoder
· GitHub ↗
· v1.0.1
1412
Downloads
0
Stars
2
Active Installs
2
Versions
Install in OpenClaw
/install pincer
Description
Security-first wrapper for installing agent skills. Scans for malware, prompt injection, and suspicious patterns before installation. Use instead of `clawhub install` for safer skill management.
Usage Guidance
This skill is designed to add a safety layer around 'clawhub install' and its code matches that purpose. Before installing, note: (1) pincer requires clawhub, uvx (mcp-scan), jq and commonly 'file' at runtime — the registry metadata only listed 'pincer', so install those dependencies first; (2) pincer stores config/history in ~/.config/pincer and installs a pincer binary under ~/.local/bin (it will suggest adding that dir to PATH); (3) pincer runs uvx mcp-scan which may contact the uvx/Invariant tooling or download mcp-scan components — if you need fully offline scanning, verify uvx behavior first; (4) pincer reduces risk but cannot make installing arbitrary skills risk-free: it fetches skill files via clawhub and will call through to normal installs when you approve, so you should still review high-risk findings and trust lists. If you want extra assurance, inspect scripts/pincer.sh locally and test pincer in a controlled environment before using it as your default installer.
Capability Analysis
Type: OpenClaw Skill
Name: pincer
Version: 1.0.1
The 'pincer' skill is a security-first wrapper for installing OpenClaw agent skills, designed to scan for malware, prompt injection, and suspicious patterns. Its `SKILL.md` contains standard installation instructions to symlink a shell script to `~/.local/bin`, which is a benign operation. The core logic in `scripts/pincer.sh` implements various security checks, including pattern detection (e.g., base64, `curl|sh`, persistence mechanisms), external URL analysis, and integration with `uvx mcp-scan`. All file system and network operations (e.g., `clawhub inspect`, `uvx mcp-scan`) are directly aligned with its stated security purpose. There is no evidence of intentional harmful behavior, data exfiltration, persistence, or prompt injection against the agent within the skill itself; rather, it actively seeks to prevent these in other skills.
Capability Assessment
Purpose & Capability
The name/description (security wrapper for installing skills) align with the provided code: a shell script that fetches skills via clawhub, scans them (mcp-scan + pattern checks), and optionally installs them. The features (trust lists, audit, pattern checks, history) are implemented in the script and match the SKILL.md.
Instruction Scope
SKILL.md and the install script stay within the stated purpose: they fetch skill files, run pattern checks and mcp-scan, and then (when approved) call through to normal installation. The script reads/writes only user-scoped paths (~/.config/pincer, ~/.local/bin) and does not attempt to read unrelated system config or unrelated credentials. Note: the script depends on clawhub, uvx, jq and uses the 'file' utility — these runtime commands are used for scanning/fetching but are not all listed in the registry 'required binaries' metadata (see environment_proportionality).
Install Mechanism
Installation is a bundled shell script that the SKILL.md symlinks into ~/.local/bin. This is a low-risk, transparent install mechanism: no external arbitrary URL downloads are performed by the installer itself. The script does run uvx (mcp-scan) at runtime which may fetch plugins via the uvx tool, but that behavior is consistent with the declared mcp-scan integration.
Credentials
The skill declares no required environment variables or secrets (primary credential: none), which is appropriate. However, SKILL.md/script rely on other binaries at runtime (clawhub, uvx, jq, and likely 'file') that are not included in the registry 'required binaries' field (metadata only lists 'pincer'). This mismatch is a minor coherence issue: the runtime script will fail unless those dependencies are present, and users should be aware these tools are needed.
Persistence & Privilege
The skill does not request always: true and does not modify system-wide settings. It writes per-user config and history to ~/.config/pincer and creates a symlink under ~/.local/bin — expected for a user-level CLI. It does not attempt to persist beyond the user's home or modify other skills' configs.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install pincer - After installation, invoke the skill by name or use
/pincer - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Improved installer: added clear guidance to ensure ~/.local/bin is in PATH for easier use.
- Installation script label updated for clarity ("Install pincer to PATH").
- Post-install message now includes usage instructions for common commands.
- No functional or feature changes to scanning or skill management logic.
v1.0.0
pincer 1.0.0
- Initial release: security-first wrapper for `clawhub install`
- Scans skills for malware, prompt injection, and suspicious patterns before installation
- Integrates with mcp-scan for advanced threat detection
- Provides commands to install, scan, audit, and manage trust for skills
- Supports detailed risk levels, publisher reputation checks, and configurable security policies
Metadata
Frequently Asked Questions
What is Pincer?
Security-first wrapper for installing agent skills. Scans for malware, prompt injection, and suspicious patterns before installation. Use instead of `clawhub install` for safer skill management. It is an AI Agent Skill for Claude Code / OpenClaw, with 1412 downloads so far.
How do I install Pincer?
Run "/install pincer" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Pincer free?
Yes, Pincer is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Pincer support?
Pincer is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Pincer?
It is built and maintained by panzacoder (@panzacoder); the current version is v1.0.1.
More Skills