Pageclip

v1.0.0

Pageclip integration. Manage data, records, and automate workflows. Use when the user wants to interact with Pageclip data.

0· 51·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill advertises Pageclip integration and exclusively instructs the agent to use the Membrane CLI to discover connectors, create connections, run actions, or proxy Pageclip API requests. All requested capabilities align with that purpose.
Instruction Scope
SKILL.md only directs installing and using the Membrane CLI, logging in, creating/listing connections, running actions, and proxying requests to Pageclip via Membrane. It does not ask the agent to read unrelated files, environment variables, or send data to unexpected endpoints.
Install Mechanism
Installation is an npm global install (@membranehq/cli). This is a standard package manager flow (moderate risk vs. no install). Users should verify the npm package identity and trustworthiness before installing global CLI tools.
Credentials
The skill declares no environment variables or credentials. It relies on the Membrane login/connection flow (browser-based OAuth-like user consent) to obtain access to Pageclip, which is appropriate. The user should be aware that Membrane will hold credentials for the connection.
Persistence & Privilege
always is false and there are no install hooks or instructions that modify other skills or system-wide settings. The skill can be invoked autonomously (platform default), which is expected and not excessive here.
Scan Findings in Context
[scanner:no_code_files] expected: The skill is instruction-only (SKILL.md) and contains no code files for the regex scanner to analyze; this is expected for many integration/CLI-guidance skills.
Assessment
This skill uses the Membrane CLI as an intermediary to talk to Pageclip. Before installing, confirm you trust the @membranehq/cli npm package and the Membrane service (they will hold connection credentials and proxy API calls on your behalf). Prefer creating a connector via the documented login/browser flow rather than pasting API keys. Review the connector permissions shown during the Membrane auth flow and avoid installing global CLIs from untrusted sources.

Like a lobster shell, security has layers — review code before you run it.

latestvk9775dxbmdm35ehrg1zdtqhes984fcsh

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments