Kintent
v1.0.0Kintent integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kintent data.
⭐ 0· 62·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
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (Kintent integration) matches the instructions: all actions are performed via the Membrane CLI and the skill explicitly requires a Membrane account and network access. There are no unrelated credential or binary requests.
Instruction Scope
SKILL.md only instructs installing/using the Membrane CLI, logging in, creating/listing connections, listing/running actions, and proxying requests through Membrane. It does not request reading unrelated files, scanning system state, or exfiltrating data; it also explicitly advises not to ask users for API keys.
Install Mechanism
There is no platform install spec (instruction-only). The doc recommends installing @membranehq/cli via npm (global install) and demonstrates using npx. Installing an npm package is a standard but moderate-risk action because packages execute code on install; the package and GitHub repository are referenced, which is expected for this integration.
Credentials
The skill declares no required environment variables or config paths. The instructions rely on Membrane to manage credentials server-side and explicitly instruct against collecting local API keys or secrets, which is proportionate to the stated purpose.
Persistence & Privilege
Skill metadata does not request permanent or elevated privileges (always:false). It's user-invocable and allows normal autonomous invocation; there is no instruction to modify other skills or global agent config.
Assessment
This skill is instruction-only and uses the Membrane CLI to access Kintent; that is coherent with its description. Before installing/running anything: 1) Verify the @membranehq/cli package and the referenced GitHub repository are legitimate and up‑to‑date. 2) Prefer using npx or a scoped environment (container/VM) instead of a global npm install if you want to limit system-wide changes. 3) Expect a browser-based login flow (or a code-based headless flow) that requires interactive authentication. 4) Understand that installing npm packages runs code on your machine—only proceed if you trust the Membrane project. If you need higher assurance, ask the skill author for a signed release URL or review the CLI source before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97cma2kfnzhjp0ff5f7jp5e0d845536
License
MIT-0
Free to use, modify, and redistribute. No attribution required.