Docspring
v1.0.2DocSpring integration. Manage data, records, and automate workflows. Use when the user wants to interact with DocSpring data.
⭐ 0· 120·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
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (DocSpring integration) match the instructions: the skill instructs the agent to use the Membrane CLI to connect to DocSpring, discover actions, run actions, or proxy requests. Requiring a Membrane account (documented in SKILL.md) is proportional to this design.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, logging in, creating/listing connections, listing and running actions, and using a request proxy. It doesn't instruct reading unrelated system files or environment variables. The proxy capability does allow arbitrary requests to DocSpring via a user connection, which is expected for an integration.
Install Mechanism
Install is an npm global install (@membranehq/cli). This is a standard package install from the public npm registry. No arbitrary downloads or archive extraction are recommended in the instructions.
Credentials
The skill requests no environment variables or external credentials in the registry metadata. SKILL.md requires a Membrane account (interactive login flow) — appropriate and proportional for a service-proxy integration. There are no unexplained secret access requests.
Persistence & Privilege
always:false (normal). The skill allows autonomous invocation (platform default). Note: once the Membrane CLI is logged in and a connection established, the agent can run proxied requests and actions via that connection — this is expected but gives the skill the ability to act on DocSpring data through the user's connection.
Assessment
This skill is coherent with its stated purpose, but take these precautions before installing: 1) Verify the @membranehq/cli package (publisher and version) before installing globally. 2) Understand that signing into Membrane and creating a DocSpring connection gives the CLI (and any agent actions using it) the ability to read and modify DocSpring data via your connection; only connect accounts you trust the agent to act on. 3) If you are concerned about automated agent actions, disable autonomous invocation for this skill or require explicit user confirmation before running connector actions. 4) Prefer running the login/connection steps yourself in a browser and verifying connection ids, rather than pasting credentials into prompts from an agent.Like a lobster shell, security has layers — review code before you run it.
latestvk9748n33353nkvfjsqdd30qf89842dzs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.