Clipper
Analysis
Clipper largely matches its clipping purpose, but it should be reviewed because it automatically writes to and Git-pushes your Obsidian vault and uses a browser profile for some pages.
Findings (4)
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.
All saves trigger automatic git sync: `pull --rebase → add → commit → push`
Every save is documented to run a Git command chain that mutates the local repository and pushes to its remote, with no artifact-shown per-save confirmation or opt-out.
`x-reader` for general web: `pipx install 'git+https://github.com/runesleo/x-reader.git'`
The setup points users to install an external CLI directly from a Git repository without a pinned release or commit in the artifacts.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
browser action=open profile=openclaw targetUrl=<url>
The WeChat workflow opens user-provided URLs with a named browser profile; the artifacts do not state that this profile is clean, isolated, or free of session/cookie context.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
r'https://wsrv.nl/?url=\\1'
The code rewrites WeChat image URLs through the third-party wsrv.nl image proxy, creating an external data flow that is not described in SKILL.md.
