Akeyless IO

v1.0.0

Akeyless Secrets Management via the official akeyless CLI — install, configure profiles, gateway routing, and safe read/list operations. Use when the user me...

0· 76·0 current·0 all-time
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
Name/description, required binary (akeyless), and install (Homebrew formula akeylesslabs/tap/akeyless) all match the stated purpose of driving the Akeyless CLI. No unrelated binaries or credentials are requested.
Instruction Scope
SKILL.md confines the agent to invoking the official CLI (version check, list-items, json output, profile usage) and instructs not to request or paste secrets. It does reference profile files (~/.akeyless/profiles/) and gateway env vars for correct operation — these are relevant to the CLI workflow. The file does not instruct the agent to read unrelated system state or to exfiltrate secrets.
Install Mechanism
Install is via a Homebrew tap formula (akeylesslabs/tap/akeyless), a standard package source for macOS/Linux Homebrew users. This is a low-risk, expected install mechanism for a CLI tool.
Credentials
The skill does not require env vars but properly documents common Akeyless envs (AKEYLESS_GATEWAY_URL, AKEYLESS_TRUSTED_TLS_CERTIFICATE_FILE) and the profiles directory. Access to ~/.akeyless profiles is necessary for the CLI to function — this is proportionate, but it means the agent (running commands on the gateway host) can observe whatever credentials the user has stored there, so care is needed.
Persistence & Privilege
The skill is not always-enabled and is user-invocable; it does not request persistent or global privileges. Autonomous invocation by the model is enabled (platform default) but not combined with any concerning permissions in this package.
Assessment
This skill appears coherent and implements an interface to the official Akeyless CLI. Before installing: confirm you trust the Homebrew tap (akeylesslabs/tap), run the CLI and configure profiles locally (do not paste keys into chat), and be aware that any CLI commands executed by the agent run as the gateway host user and can access ~/.akeyless profiles and any credentials stored there. Limit the agent/gateway user's privileges and ensure profiles are created/configured outside of chat. If you need the agent to list or summarize secrets, prefer read-only commands and request redaction of any secret fields.

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

latestvk97cnv6j51akgwt7ehjv5pvtbx83d90c

License

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

Runtime requirements

🔑 Clawdis
Binsakeyless

Install

Install Akeyless CLI (brew tap)
Bins: akeyless
brew install akeylesslabs/tap/akeyless

Comments