← Back to Skills Marketplace
Qclaw Workbuddy Bridge
by
liuboacean
· GitHub ↗
· v1.2.0
· MIT-0
109
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install qclaw-workbuddy-bridge
Description
QClaw 与 WorkBuddy 任务分发集成桥。当用户想要: - 通过微信让 QClaw 发送任务给 WorkBuddy 执行 - QClaw 写任务 → WorkBuddy 执行 → 微信推送结果 - 打通 QClaw(微信入口)和 WorkBuddy(执行引擎) - 远程任务分发、跨客户端任务执行 触发词...
Usage Guidance
What to check and do before installing:
- Fix the path/filename inconsistency: SKILL.md sometimes tells QClaw to run python3 ~/.workbuddy/queue/qclaw_tasks.py, but the shipped script is scripts/qclaw_queue.py under ~/.workbuddy/skills/qclaw-workbuddy-bridge/. Confirm which path will be installed and update all commands to the same, correct path. A mismatched path can cause failed runs or accidental execution of a different script placed in the queue directory.
- Review and limit what QClaw will automatically enqueue. The provided prompt encourages automatic queuing for many conditions (including tasks that access local files). Consider restricting automatic enqueuing to explicit user consent, or require a confirmation step before writing tasks that include local file paths or sensitive context.
- Restrict file paths and privileges for WorkBuddy execution. Because tasks may include local paths, ensure WorkBuddy runs in a sandbox, or add validation to prevent reading sensitive system files. Use least privilege for any automations that process queue entries.
- Protect the queue directory: set tight filesystem permissions (owner-only) and monitor/validate files placed in ~/.workbuddy/queue. Because some doc commands reference executing scripts under ~/.workbuddy/queue, ensure no untrusted files can be executed from that location.
- Test in a safe environment first: run the scripts locally on a non-production account to validate behavior (add/list/poll/done) and confirm triggers and file writes behave as expected.
- If you need higher assurance, request the author to (a) correct documentation inconsistencies, (b) include optional safeguards (confirmation prompts, path whitelists), and (c) sign or package the script in a predictable install location so QClaw/WorkBuddy run the intended code.
Capability Analysis
Type: OpenClaw Skill
Name: qclaw-workbuddy-bridge
Version: 1.2.0
The skill bundle implements a task queue bridge between QClaw and WorkBuddy using a local JSON file (~/.workbuddy/queue/qclaw_tasks.json). The Python script (qclaw_queue.py) is a standard CLI utility for managing task states (add, list, poll, done), and the SKILL.md instructions correctly define the agent's role in dispatching complex tasks to the execution engine without any evidence of malicious intent, data exfiltration, or unauthorized system access.
Capability Tags
Capability Assessment
Purpose & Capability
The stated purpose (a simple QClaw ↔ WorkBuddy bridge using a shared JSON queue) matches the included Python queue manager and the documented file-based architecture. Nothing in the code requires cloud credentials or unrelated system access. However, SKILL.md contains inconsistent command paths (references to qclaw_tasks.py in ~/.workbuddy/queue vs the actual script qclaw_queue.py located in ~/.workbuddy/skills/...), which is an incoherence between documentation and shipped files.
Instruction Scope
The runtime instructions tell QClaw to proactively write tasks into the queue whenever many broad conditions are met (including when tasks require access to local files). That behavior is plausible for a delegation bridge, but it expands the agent's authority and can lead to unintended exposure of local file paths and data. The WorkBuddy side is instructed to "自主执行任务(调用所有需要的工具、Skill 完成工作)", granting broad discretion to use other tools/skills when executing tasks. Also the docs inconsistently reference different script paths/filenames (qclaw_tasks.py vs qclaw_queue.py), which could cause misconfiguration and unintended execution of files in the queue directory.
Install Mechanism
No install spec (instruction-only with a helper script) — lowest-risk install behavior. The only code is a small Python script that reads/writes JSON files under ~/.workbuddy; no downloads or external installers are included.
Credentials
The skill requests no environment variables or credentials, which is proportionate. However, the design intentionally passes file paths and user/context information through the queue; if users or QClaw supply sensitive local paths, WorkBuddy (or any automation processing the queue) may access those files. The SKILL.md instructs QClaw to ask for local file paths and include them in the task context, which is functionally necessary but increases data-exposure risk.
Persistence & Privilege
The skill does not request always:true and does not modify other skills’ configurations. It writes files under the user's home (~/.workbuddy) which is expected for a user-space queue bridge. No privileged system changes are performed.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install qclaw-workbuddy-bridge - After installation, invoke the skill by name or use
/qclaw-workbuddy-bridge - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.0
v1.2.0: watch --once支持launchd事件驱动,WorkBuddy自动化已停用,完全无轮询零Token
v1.1.0
v1.1.0: 触发机制优化——add命令自动写.trigger信号,自动化改为30分钟兜底轮询,大幅节省Token
v1.0.0
初始版本:QClaw与WorkBuddy双向任务管道核心,支持队列管理、轮询自动化、结果写入
Metadata
Frequently Asked Questions
What is Qclaw Workbuddy Bridge?
QClaw 与 WorkBuddy 任务分发集成桥。当用户想要: - 通过微信让 QClaw 发送任务给 WorkBuddy 执行 - QClaw 写任务 → WorkBuddy 执行 → 微信推送结果 - 打通 QClaw(微信入口)和 WorkBuddy(执行引擎) - 远程任务分发、跨客户端任务执行 触发词... It is an AI Agent Skill for Claude Code / OpenClaw, with 109 downloads so far.
How do I install Qclaw Workbuddy Bridge?
Run "/install qclaw-workbuddy-bridge" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Qclaw Workbuddy Bridge free?
Yes, Qclaw Workbuddy Bridge is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Qclaw Workbuddy Bridge support?
Qclaw Workbuddy Bridge is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Qclaw Workbuddy Bridge?
It is built and maintained by liuboacean (@liuboacean); the current version is v1.2.0.
More Skills