Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Outbound Auto Setup
v1.0.0自动监听外出关键词，提取日期时间地点事项，自动创建并验证Apple提醒、cron推送及待办任务提醒。
⭐ 0· 44·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill's stated purpose (detect outbound messages and create Apple reminders, cron pushes, and pending-tasks entries) matches the code behavior (parsing messages, running a reminder CLI, appending a pending-tasks file). However the package metadata declares no required binaries or prerequisites even though the code execs external commands (remindctl and a create-cron-job.js script). Also the referenced create-cron-job.js is not present in the repo — a clear mismatch between claimed capabilities and the shipped files.
Instruction Scope
Runtime instructions and code stay within the stated domain (message parsing, creating reminders, writing logs and a pending-tasks file). The skill logs full incoming messages along with userId and channelId to a local log file and appends to ~/.openclaw/workspace/memory/pending-tasks.md — this is expected for its purpose but has privacy implications (it records message content and metadata). The SKILL.md also claims a 'first-use confirmation' but the code defaults to enabled=true, so the claimed user confirmation step is not enforced.
Install Mechanism
No install spec (instruction-only) and the repository contains plain JS files. Nothing in the repo downloads code at runtime or uses obscure external URLs. The risk is limited to the code that will run locally — particularly child_process.exec usage — but there is no high-risk installer URL or archive.
Credentials
The skill requests no credentials/env vars in metadata. It does use process.env.HOME implicitly to locate logs and the pending-tasks file, which is reasonable. No external API keys or unrelated secrets are requested. Still, it reads and records message contents and user/channel IDs — sensitive data but proportional to being a message hook.
Persistence & Privilege
The skill is designed as a message hook (hook-package.json/hook.js) and when enabled will see all incoming messages routed to that hook. 'always' is false (good). The practical effect: if you enable the hook the skill will automatically process messages (potential privacy exposure). It does not appear to alter other skills' configs or require elevated system-wide privileges.
What to consider before installing
This skill largely implements what it claims but has several issues you should address before installing:
- Missing/undeclared dependencies: the code calls external commands (remindctl) and a script node create-cron-job.js, but the registry metadata lists no required binaries and create-cron-job.js is not included — expect runtime failures or silent behavior. Install and verify remindctl yourself or provide the missing cron-creation script.
- Privacy: the hook logs full message text plus userId and channelId to ~/.openclaw/logs/outbound-auto-setup.log and writes to ~/.openclaw/workspace/memory/pending-tasks.md. If you enable this hook, those files will contain message contents and identifiers. Review/logrotate or restrict access if that is sensitive.
- Autonomy vs confirmation: SKILL.md says it will ask first-time users for confirmation, but the code defaults CONFIG.enabled = true (and hook config enabled true). If you want manual approval, set CONFIG.enabled = false or don't enable the hook until you review code.
- child_process.exec usage: the code shells out (exec). That works for integration but can be risky if commands or arguments are constructed from untrusted data. Review the command construction (remindctl arguments) and consider sanitizing inputs.
Recommended steps before enabling:
1. Inspect the code locally and run tests (npm test). 2. Provide or review the missing create-cron-job.js or modify setupOutbound to a safe, included implementation. 3. Install and test remindctl in a controlled environment. 4. Set CONFIG.enabled = false until you're ready, and verify log/pending file locations and access controls. 5. If you need stricter behavior, modify the skill to require explicit user confirmation before creating reminders.index.js:186
Shell command execution detected (child_process).
Patterns worth reviewing
These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97b60zbes9w5ewkmvtskkqe8n84ebpq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.