Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Openclaw Diary
v1.0.2Set up and manage OpenClaw auto learning diary. Used for: (1) Help users fork OpenClaw-Diary repository (2) Connect the forked repo to OpenClaw (3) Configure...
⭐ 0· 309·0 current·0 all-time
byYuqiao Tan@trae1oung
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md describes forking a GitHub repo, customizing index.html, scheduling daily pushes, and enabling Pages—these actions match the stated purpose. However, the instructions reference using an 'openclaw cron' command and interacting with GitHub via a PAT, yet the registry metadata lists no required environment variables or declared binaries. That mismatch is unexpected: a setup skill that instructs use of a CLI (openclaw) and a GITHUB_TOKEN should declare those requirements.
Instruction Scope
Runtime instructions are concrete (git clone, sed edits, git push, curl to GitHub API). They require the user to create and use a GitHub PAT and to run a cron/heartbeat task that 'reads latest AI/tech/politics news' and pushes content. The actions are within the diary scope, but the instructions are somewhat vague about how the token is used (no examples of secure usage, no guidance on storing the token for automation), and the 'read latest news' step could imply scraping external sources—acceptable for a diary but should be explicit about data sources and frequency.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, which is the lowest install risk. There is no installer downloading arbitrary code.
Credentials
The SKILL.md's Configuration table lists FORK_URL and GITHUB_TOKEN (and mentions CRON_SCHEDULE), but the skill's registry metadata declares no required environment variables or primary credential. That discrepancy is important: the workflow requires a GitHub PAT (sensitive) for push automation, but the skill manifest does not declare or explain how that secret will be used or stored. Additionally, the instructions reference 'openclaw cron add' (an external CLI) but do not declare it as a required binary.
Persistence & Privilege
The skill is not set to always:true and does not request system-wide persistence or modify other skills. It only provides instructions for user-side configuration and scheduling; no elevated platform privileges are requested.
What to consider before installing
This skill appears to do what it says (help fork and automate a GitHub-based diary), but before installing or following it: (1) note that the SKILL.md expects a GitHub Personal Access Token (repo scope) and an 'openclaw' CLI—yet the registry lists no required env vars or binaries. Ask the publisher to update the manifest to declare GITHUB_TOKEN and any CLI dependency. (2) If you create a PAT, give it least privilege (or use a fine-grained token or deploy key), keep it secret, and know how you'll store/revoke it—avoid pasting tokens into shared UIs. (3) Prefer running the git/cron setup locally yourself rather than giving any agent automated write access; verify what exact commands will run and where files are stored. (4) If you want automated pushes, consider using GitHub Actions or a repository deploy key instead of embedding a full-personal token. If the publisher provides a manifest that declares the token requirement and explains how tokens are used and stored (or replaces PAT usage with a safer alternative), my confidence would increase.Like a lobster shell, security has layers — review code before you run it.
latestvk97fbyzh5fyytmc918wjxzezt5826j80
License
MIT-0
Free to use, modify, and redistribute. No attribution required.