Stammerai
v1.0.0Stammer.ai integration. Manage Organizations. Use when the user wants to interact with Stammer.ai data.
⭐ 0· 59·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
Name/description map to the instructions: the skill uses the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to Stammer.ai. All required actions (auth, listing actions, running actions, proxying) are consistent with an integration skill.
Instruction Scope
SKILL.md instructs the agent to run npx @membranehq/cli commands and to create/complete a browser-based login; it does not ask to read unrelated files or environment variables. Note: successful operation depends on credentials stored at ~/.membrane/credentials.json (created by the Membrane CLI) and the CLI will make network requests and proxy arbitrary API calls when requested.
Install Mechanism
There is no install spec in the registry, but the runtime instructions use npx @membranehq/cli@latest which dynamically downloads and executes a package from the npm registry. Using @latest means the code executed can change over time—this is expected but carries the usual risks of running remote packages.
Credentials
The skill declares no required env vars or credentials; this is proportional. However, it relies on Membrane-managed credentials (stored in ~/.membrane/credentials.json) and the Membrane service to perform auth and proxied API requests.
Persistence & Privilege
always is false, the skill is user-invocable, and it does not request persistent system-wide privileges or modify other skills' configs. Its persistence is limited to using the Membrane CLI and the credentials that CLI stores.
Assessment
This skill is coherent for integrating with Stammer.ai via Membrane, but before installing consider: (1) npx @membranehq/cli@latest will download and execute code from npm each time—if you prefer reproducibility, pin a specific version; (2) the Membrane login stores credentials in ~/.membrane/credentials.json and Membrane acts as a proxy for API calls, so the service will see proxied request data; (3) verify you trust the Membrane project and review its privacy/security docs and the npm package source if you have sensitive data; (4) in headless or automated contexts the CLI prints URLs/codes that require manual completion—ensure that authentication flows align with your security policies.Like a lobster shell, security has layers — review code before you run it.
latestvk9712phrm8ay8wn26rmw4qfyc9845anw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.