Bearer

v1.0.0

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

0· 54·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill is presented as a Bearer integration and its runtime instructions use the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to Bearer. The homepage and repository references point to Membrane-related resources (getmembrane.com / membranedev), which matches the documented implementation (Bearer via Membrane), so required capabilities align with the stated purpose.
Instruction Scope
SKILL.md tells the agent to install and use the Membrane CLI, perform interactive/browser login flows, list actions, run actions, and proxy arbitrary requests to the Bearer API through Membrane. The instructions do not ask the agent to read local files or unrelated environment variables. Note: proxying lets the agent send arbitrary requests to an external API once authenticated, so the agent can transmit user data to Bearer via Membrane if invoked.
Install Mechanism
This is an instruction-only skill (no install spec). It recommends installing the official @membranehq/cli via npm or using npx, which is a common, low-risk mechanism. No downloads from unknown hosts or extracted archives are involved.
Credentials
The skill declares no required environment variables or credentials; authentication is handled interactively by the Membrane service. This is proportionate to the workflow described. Users should be aware that authentication is delegated to Membrane (server-side managed credentials).
Persistence & Privilege
always is false (no forced installation). Model invocation is allowed (default), so the agent can autonomously call the Membrane CLI / Bearer endpoints if the agent is permitted to run commands. That is expected for a skills-based integration but means you should control agent permissions if you don't want autonomous external API calls.
Assessment
This skill is coherent: it uses the Membrane CLI to access Bearer and requires interactive login in a browser. Before installing, verify you trust the Membrane service and the @membranehq/cli npm package (review the package/repo if needed). Be aware that once authenticated the agent can proxy arbitrary requests to Bearer via Membrane — restrict the agent's ability to run external commands or use the skill only in environments/accounts with limited privileges. If you need stricter control, test with a dedicated Membrane/Bearer test account and inspect the npm package source before installing.

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

latestvk97f0jw69vhy1mqr7hpmbhemzd84b6ts

License

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

Comments