Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
corn-manager-master
v1.0.0定时任务创建通用技能。自动提取当前对话上下文，标准化创建和检查OpenClaw定时任务。
⭐ 1· 50·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's stated purpose (standardize OpenClaw cron creation/checks) matches the included scripts and CLI calls to openclaw cron. However, the SKILL.md promises automatic extraction of channel and user_id from session_status; the supplied scripts still contain TODO placeholders and default hard-coded values (CHANNEL="feishu", USER_ID="ou_xxxxxx"), so the claimed auto-extraction is not implemented. This mismatch between documentation and code is incoherent and may lead to unexpected behavior or require additional privileged access that the user wasn't warned about.
Instruction Scope
Runtime instructions tell the agent to call local OpenClaw CLI commands (openclaw cron add, openclaw cron list) and to parse their JSON output; that scope is appropriate for a cron-management skill. The SKILL.md directs automatic extraction from session_status output and storing logs/records in 'memory', but does not give the exact mechanism or safeguards. The validation script parses JSON output with grep/sed rather than robust JSON tools (jq is suggested in SKILL.md), which is brittle. Overall the instructions are not overly broad, but are vague about how session context is obtained and about what 'memory' persistence implies.
Install Mechanism
No install spec is provided (instruction-only plus shippped scripts). Nothing is downloaded or installed automatically by the skill, so install-time risk is low. The scripts are present and would run only when invoked.
Credentials
The skill declares no required environment variables, credentials, or config paths, and the scripts only call local openclaw CLI commands. There are no requests for unrelated secrets or external service tokens. That is proportional to a cron-management utility — but actual automatic extraction of session data (if implemented) may require agent-level access to session state that should be verified before use.
Persistence & Privilege
always:false and no code attempts to modify other skills or global agent configuration. The SKILL.md suggests recording logs/checks into 'memory' (presumably OpenClaw memory) but the provided scripts do not write persistent files other than standard output. There is no evidence of privilege escalation or permanent background processes.
What to consider before installing
This skill is plausible for managing OpenClaw cron tasks, but there are important inconsistencies to resolve before installing or using it in production: (1) SKILL.md claims automatic extraction of channel and user ID from session_status, but both scripts contain TODOs and hard-coded defaults — verify how session context will actually be provided and whether the agent/CLI has permission to read it. (2) Validation script parses JSON with grep/sed (fragile); prefer jq or robust JSON parsing to avoid false positives/negatives. (3) Ensure the OpenClaw CLI (openclaw) and any required gateway/status commands exist in your environment and that invoking them from this skill does not leak sensitive information. (4) Test the scripts in a safe environment with non-production user IDs and validate logging/where 'memory' entries go. If you rely on the promised auto-extraction, ask the author to provide the implementation or remove the misleading claim before deployment.Like a lobster shell, security has layers — review code before you run it.
latestvk97a7zg3bg7kg7c7bkp6v6epen83nxjq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.