File Writer
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This skill is coherently limited to writing text files in a scratch folder, with backups and confirmations, but users should still review file paths and avoid unsafe manual shell fallbacks.
Install this only if you want the agent to create and edit text files under /home/alfred/.openclaw/workspace/scratch. Provide relative paths, check overwrite/append prompts and backups, and do not copy any fallback shell command unless you understand and trust the exact content.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
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.
The agent can create, overwrite, append, and back up selected text files in the scratch folder.
The skill directs the agent to use file read/write tools and limited shell execution to create directories. This is expected for the stated file-writing purpose and is bounded to a scratch directory, but it is still local mutation authority.
Base directory: /home/alfred/.openclaw/workspace/scratch... Sanitize: Reject if path contains '../', starts with '/', or has non-text extensions... Primary tools: 'write' for saving, 'read' for checks/backups, 'exec' for mkdir -p
Use only relative scratch paths, review overwrite or append confirmations, and keep important files outside this skill's working area.
If a user manually copies a generated shell command containing untrusted content, the shell could interpret parts of that content unexpectedly.
This is a user-directed fallback command, not automatic execution. However, templating arbitrary content into a shell command can be unsafe if the content contains shell-special characters.
If tools fail, fallback: Message requesting user runs `echo "[content]" > [full_path]` or `>>` for append.
Prefer the built-in write tool. If a manual fallback is needed, review the command carefully or use a safer editor/file-write method instead of copying untrusted content into a shell command.