Agent-to-Owner File Bridge
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This file-sharing skill is coherent and permission-gated, but it can upload files to a hosted or publicly tunneled server and may run external server code if you choose autonomous mode.
This skill appears purpose-aligned for sharing files with you. Before installing or using it, decide whether you trust the hosting path, approve only named files, prefer your own reviewed server when possible, protect the API key, and close or delete any temporary tunnel/key after the session.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
64/64 vendors flagged this skill as clean.
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.
If the user approves the wrong file or server destination, that file can leave the agent workspace and be shared through the bridge.
The skill authorizes the agent to transmit files to a server, but it also scopes the action to a named file and requires user confirmation.
Uploading a file | User must confirm file + destination | Named file, single upload ... POST the file to the server URL with `X-API-Key` header and `file` form-data field.
Approve only specific files and destinations, and avoid uploading sensitive files unless you control and trust the server.
The safety of autonomous hosting depends on the external server.py code and its current repository contents.
Autonomous mode depends on external server code that is not bundled or pinned in the provided artifacts, although running it is described as user-approved and purpose-aligned.
copy `server.py` from the open-source repo ... `pip install flask` then `python server.py`
Prefer manual self-hosting or review/pin the repository code before allowing the agent to copy and run it.
Anyone who obtains the bridge API key may be able to upload, list, view, or delete bridge-managed files.
The bridge uses an API key for authorization; this is expected for the service, but query-string or shared-key handling can expose the key if mishandled.
Provide the API Key via one of these methods: - HTTP Header: X-API-Key: YOUR_API_KEY - POST Field: api_key=YOUR_API_KEY - Query Param: ?api_key=YOUR_API_KEY
Use the header method when possible, avoid putting the key in shared URLs, and rotate/delete temporary keys after use.
Uploaded files and the bridge service may be reachable through a public URL for the life of the tunnel.
Autonomous mode can expose the bridge over a public tunnel, which is central to sharing files but crosses a public network/tunnel-provider boundary.
open a temporary public tunnel (via localtunnel or localhost.run). This creates a public URL pointing at my local port 5000.
Use a trusted server or tunnel, close the tunnel when finished, and do not expose highly sensitive files through temporary public links.