Akana By Perforce

v1.0.0

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

0· 75·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
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name/description (Akana by Perforce integration) matches the instructions: it instructs the agent to use the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to Akana. Nothing requested (no env vars, no unrelated binaries) is inconsistent with that purpose.
Instruction Scope
SKILL.md restricts runtime actions to installing/using the @membranehq/cli, logging in, creating connections, listing actions, running actions, and proxying requests. It does not direct the agent to read unrelated files, environment variables, or system config, nor to exfiltrate data to unexpected endpoints.
Install Mechanism
Installation is via npm (npm install -g @membranehq/cli) or npx. npm global install is a common but higher-privilege install step (may require admin rights); the SKILL.md also suggests npx which avoids global installs. No downloads from arbitrary URLs or extract steps are required.
Credentials
The skill declares no required environment variables or credentials and explicitly tells the user not to provide API keys locally. It relies on Membrane to manage authentication server-side, which is proportional to the integration's needs.
Persistence & Privilege
This is an instruction-only skill with no install spec or persistent components, and always:false. It does not request elevated agent-wide privileges or modify other skills' configs.
Assessment
This skill is instruction-only and coherent: it expects you to install/run the official Membrane CLI and use a Membrane account to connect to Akana by Perforce. Before installing: prefer using npx to avoid a global npm install if you want minimal system changes; verify the @membranehq/cli package and the membranedev repository are the official project (check package authors, GitHub repo, and domain getmembrane.com); be aware that API requests and credentials are proxied through Membrane — review its privacy/hosting policies if you will send sensitive data; and confirm the browser-based login flow and headless code flow meet your environment's security/compliance requirements.

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

latestvk97b83gfzawgbg0tzhecnmv0ks845m30

License

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

Comments