Skillv1.0.1

ClawScan security

Focus Master · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousMar 11, 2026, 1:41 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's purpose (a local CLI Pomodoro/task tool) is plausible, but the package is incomplete and the installation instructions ask you to symlink an executable that is not included — this mismatch and the unclear origin of the executable are concerning.
Guidance: This bundle looks like a CLI Pomodoro/task tracker, but the package is missing the actual 'time-management' executable it tells you to symlink. Do not run the ln -s command or place any binary in your PATH until you verify the executable's source and contents. Recommended steps before installing: - Inspect the skill directory in ~/.openclaw/workspace/skills/focus-master/ to confirm whether a 'time-management' file exists and is the code you expect. - If the file is missing, obtain the source from the referenced GitHub repo (package.json.repository) and review the code before installing. Prefer cloning the repository yourself and inspecting scripts. - If a prebuilt binary is provided, verify its checksum/signature and review what operations it performs (especially anything that modifies system files like /etc/hosts, firewalls, or browser settings) in a sandbox or VM. - Ask the skill author for the missing executable or source code; do not symlink an unknown file into ~/.local/bin. - Because 'focus mode' could change system behavior, confirm exactly how it blocks distractions before granting it broad file or system access. I assessed this as 'suspicious' (not necessarily malicious) because of the incomplete packaging and unclear provenance of the executable; additional information (the missing script or a trustworthy repo snapshot) would likely change the verdict to benign.

Review Dimensions

Purpose & Capability: concernThe name/description indicate a local CLI for Pomodoro and task tracking, which matches the SKILL.md usage examples and data storage location. However package.json declares a binary named "time-management" and the SKILL.md asks you to symlink that file, but no executable or code file named "time-management" is present in the skill bundle. That mismatch suggests the package is incomplete or expects you to obtain a binary from an unspecified place.
Instruction Scope: noteThe runtime instructions are narrowly scoped to installing a symlink, running the CLI, reading/writing local config and an SQLite DB under ~/.openclaw/data/time-management/, and changing settings — all consistent with a local productivity tool. The instructions do not request other system files or external endpoints. The 'focus mode / block distractions' feature is vague and not documented in the SKILL.md; how it blocks distractions (hosts file, notifications, window management, firewall, browser extensions, etc.) is unspecified and should be clarified before trusting it.
Install Mechanism: concernThere is no formal install spec (instruction-only), which is low risk in itself, but the SKILL.md instructs creating a symlink from ~/.openclaw/workspace/skills/focus-master/time-management to ~/.local/bin/time-management. Because the executable file is not included in the bundle, following this instruction would either create a broken symlink or rely on you to place an executable in that path from an unspecified source. package.json points to a GitHub repo, but no automated or documented safe fetch/install step is provided — this is an integrity/ provenance gap.
Credentials: okThe skill declares no required environment variables, no credentials, and stores data locally under ~/.openclaw/data/time-management/. Requesting only local config/db access is proportionate for the stated purpose.
Persistence & Privilege: okThe skill does not request always:true, does not modify other skills, and its only persistent artifact is a local data directory and the optional symlink in ~/.local/bin. Those are normal for a user-installed CLI; still, creating a binary in PATH via symlink is something you should verify the source of before doing.