Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Prepublish Privacy Scrub
v1.0.0Scan and remove sensitive data before publishing skills. Detect API keys, tokens, secrets, and personal info.
⭐ 0· 331·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
Name/description align with the instructions: the SKILL.md contains scanning and scrubbing routines intended to detect and redact keys, tokens, emails, and internal URLs. No unrelated credentials, binaries, or install steps are requested.
Instruction Scope
The instructions read and overwrite files recursively in a working tree and would modify content in place, but they claim 'original files backed up before scrub' while the Invoke-PrivacyScrub implementation does not create backups. Detection patterns include bearer tokens, sk- keys, and OPENCLAW_* patterns, yet the scrubbing replacement table only covers a few simple name=value cases (apiKey, token, secret). Test-PrivacyScan only searches files with selected extensions (.md, .ps1, .json, .txt) while scrubbing operates on all files, introducing a risk of modifying unintended files (binary files, other extensions) and missing detections in un-scanned extensions. The functions are PowerShell-specific but the skill metadata does not state a platform requirement, which may lead to failures or unexpected behavior on non-Windows systems.
Install Mechanism
Instruction-only skill with no install steps or downloaded artifacts — low installation risk. No archives or external downloads.
Credentials
No environment variables, credentials, or config paths are requested. The detection patterns reference OPENCLAW_* and other token forms only for identification; no secret access is requested.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modify other skills. It does perform potentially destructive local file writes, but does not attempt to change system-wide configuration or store long-lived credentials.
What to consider before installing
Do not run this scrubbing code on your primary working directory yet. Main issues to address before using: (1) Implement reliable backups (e.g., copy files to a timestamped backup folder or use git to create a branch) — the current Invoke-PrivacyScrub overwrites files without backups despite claiming otherwise. (2) Make scrubbing coverage consistent with detection: add replacers for bearer tokens, sk- keys, OPENCLAW_* matches, and other patterns you detect (or ensure the scan only reports and requires manual removal). (3) Limit the set of files you modify to text files (avoid altering binaries) and ensure the scan and scrub operate on the same file-extension whitelist. (4) Add a dry-run mode that reports matches without changing files, and produce a summarized report rather than only in-place edits. (5) Declare platform requirements (PowerShell) so users on Linux/macOS know how to run it. (6) Test on a copy or in a disposable environment (and/or on a git branch) to avoid irreversible changes. After those changes the skill would be much safer; as written, it is coherent with its purpose but contains risky gaps and mismatches that make it unsafe to run directly.Like a lobster shell, security has layers — review code before you run it.
latestvk97238thsb3j75tpyz0nqt3gy5822trd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.