← Back to Skills Marketplace
107
Downloads
0
Stars
1
Active Installs
7
Versions
Install in OpenClaw
/install outclaw
Description
B2B outreach orchestrator. Entry point for ANY request that mentions reaching out, contacting, emailing, messaging, DMing, following-up, or otherwise engagin...
Usage Guidance
This skill contains serious inconsistencies you should resolve before installing. It expects local scripts and a lead-pulling tool but ships no install or declared credentials — which means it will either fail or rely on external, unverified scripts already on your system. It also requires writing full lead data to /tmp and outputting file contents into the chat, which can expose sensitive contact or company data. Before proceeding: (1) ask the publisher for an explicit install script and a list of required credentials and why each is needed; (2) inspect any scripts referenced (e.g., ~/.openclaw/skills/outclaw/shared/scripts/*) — do not run the skill until you’ve reviewed them; (3) if you must test, do so in a sandbox or with test accounts and non-sensitive sample data; (4) confirm where leadbay credentials are stored and how access is authorized; (5) consider restricting or auditing all /tmp persistence and any automatic execution of shell/python scripts. If the publisher cannot provide clear, verifiable install artifacts and a minimal list of required secrets, treat the skill as unsafe to run in production.
Capability Tags
Capability Assessment
Purpose & Capability
The skill declares itself as a B2B outreach orchestrator, which reasonably requires access to lead data and tooling. However, the SKILL.md calls outspecific local scripts (e.g., ~/.openclaw/skills/outclaw/shared/scripts/outclaw_daily_batch.sh, plan_scaffolder.py, draft_checker.py) and a tool name `leadbay_pull_leads` that imply additional code and credentials. The package contains no install spec and no shipped scripts; it also declares no required environment variables or primary credential. The declared metadata (no env, no install) does not match the capabilities the instructions clearly require.
Instruction Scope
Runtime instructions require: calling `leadbay_pull_leads`, writing the entire MCP response verbatim to /tmp/leadbay-pull.json, running multiple scripts from the user's home path, running validators, and then outputting full file contents into the chat. These steps access filesystem locations, persist full lead payloads (potentially sensitive PII), and execute shell/python scripts. The instructions also mandate exact formatting and full dumps (not summaries), which increases the risk of exposing private data. The SKILL.md also instructs to run scripts that are not included in the skill bundle.
Install Mechanism
There is no install specification and no code files shipped with the skill, yet the instructions assume presence of many scripts under ~/.openclaw/skills/outclaw/shared/scripts and a working `leadbay_pull_leads` tool. This mismatch is risky: either the skill expects a prior manual install/third-party components (not documented) or it will fail. The absence of an install step that would place those scripts is an incoherence that should be clarified.
Credentials
The skill declares no required environment variables or primary credential, but it instructs calls to a lead service (`leadbay_pull_leads`) and to run scripts that likely require API keys or configured credentials. That omission is disproportionate: a lead-pulling orchestration skill should clearly specify which credentials are required and why. Additionally, mandatory dumping of full responses to /tmp increases the chance of exposing sensitive fields that the user may not expect to be persisted or shared.
Persistence & Privilege
Although the skill is not marked always:true, it explicitly writes and reads files in /tmp and in the user's home (~/.openclaw/...), and runs shell/python scripts from those locations. That level of filesystem interaction and execution capability is significant and should be justified and delivered by the skill (via a clear install), but it is not. The instructions therefore request substantial local privilege without corresponding metadata or safety controls.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install outclaw - After installation, invoke the skill by name or use
/outclaw - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.6
v2.1.33: hard sanity gate refuses truncated Leadbay pulls — caps agent's paraphrase-and-summarize failure mode
v1.0.5
v2.1.32: ensure_leadbay_bound self-heal for plugins.allow + entries + agent skills + extensions dir
v1.0.4
v2.1.31: pull count=50, kill stale --n 3, heredoc-write discipline
v1.0.3
v2.1.30: paste-the-file-verbatim rule + sanity gate kills 'see above' bypass
v1.0.2
v2.1.29: first-action scaffolder rule + chat-reply-must-validate + angle-fit detector (kills 'furthers their sustainability goals' class)
v1.0.1
v2.1.28: agent mindset + options-and-choose + coherence checklist + evidence card + per-tenant style + daily launchd cron
v1.0.0
- Initial public release of OutClaw (version 2.1.27), a B2B outreach orchestrator skill.
- Handles all user requests related to business outreach, engagement, campaign setup, research, reply handling, and opt-outs.
- Detects and routes requests to appropriate sibling skills (outclaw-setup, outclaw-style, outclaw-research, outclaw-plan).
- Enforces strict top-level "hardrails," including daily cap limits, explicit per-touchpoint approvals, opt-out/reply handling, and anti-fabrication rules before routing.
- Prevents any generation or use of fabricated lead/contact data; checks for real data sources and connected plugins before proceeding.
- Publishes clear refusal messages when requests violate safety or operational boundaries, and offers compliant alternatives where relevant.
Metadata
Frequently Asked Questions
What is Outclaw?
B2B outreach orchestrator. Entry point for ANY request that mentions reaching out, contacting, emailing, messaging, DMing, following-up, or otherwise engagin... It is an AI Agent Skill for Claude Code / OpenClaw, with 107 downloads so far.
How do I install Outclaw?
Run "/install outclaw" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Outclaw free?
Yes, Outclaw is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Outclaw support?
Outclaw is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Outclaw?
It is built and maintained by milstan (@milstan); the current version is v1.0.6.
More Skills