Todolist Md Clawdbot
Analysis
The skill is purpose-aligned for editing Markdown todos, but it uses broad Google Drive credentials, persistent refresh tokens, and local credential files that users should review carefully before installing.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
const raw = execFileSync(cmd[0], cmd.slice(1), { encoding: 'utf8' });The script executes a local gog CLI command to list Drive files. This is disclosed and purpose-aligned, but it means running the skill depends on a trusted local binary.
const gogBin = process.env.GOG_BIN || '/home/linuxbrew/.linuxbrew/bin/gog';
The helper relies on an external gog executable outside the artifact, while the declared requirements list no required binaries.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
const scopes = ['https://www.googleapis.com/auth/drive'];
The helper requests the broad Google Drive OAuth scope, which can grant access beyond a single todo file or folder even though the skill's stated purpose is limited Markdown todo management.
const refreshTokenFile = args.refreshTokenFile || process.env.REFRESH_TOKEN_FILE || '/root/clawd/.secrets/todolist_drive_oauth.json';
The script persists a reusable OAuth refresh token in a local secrets path, creating ongoing Drive access after the first authorization.
const envFile = '/root/clawd/.secrets/gog.env';
The folder helper reads a local gog credential environment file containing account/keyring settings, but the registry metadata declares no required credentials or config paths.