← Back to Skills Marketplace
deanshak

Akeyless IO

by deanshak · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
134
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install akeyless
Description
Akeyless Secrets Management via the official akeyless CLI — install, configure profiles, gateway routing, and safe read/list operations. Use when the user me...
README (SKILL.md)

Akeyless CLI

Teach the agent to use the official Akeyless CLI on the same machine as the OpenClaw gateway. Do not invent URLs, regions, or auth flows—defer to docs and akeyless \x3Ccmd> -h.

References

Load when details are needed:

  • references/cli-notes.md — install (macOS/Linux), profiles, gateway env, list-items, precedence, safety

Prerequisites

  1. akeyless on PATH (akeyless --version).
  2. A configured profile (akeyless configure or ~/.akeyless/profiles/). Auth is not done through chat—user runs configure locally.
  3. For private gateways: AKEYLESS_GATEWAY_URL (and TLS trust PEM if required)—see references.

Workflow

  1. Confirm CLI: akeyless --version / which akeyless.
  2. If commands fail with auth errors: user must fix profile or gateway URL outside the agent; suggest akeyless configure or env vars from references—never ask them to paste Access Keys into chat.
  3. Prefer read-only checks first: akeyless list-items --minimal-view or akeyless list-items --path '\x3Cfolder>' --minimal-view (paths are org-specific).
  4. For JSON: akeyless list-items --json — summarize; do not dump large payloads or possible secret fields into chat.
  5. Region / tenant: do not assume only vault.akeyless.io; follow account and org docs.

OpenClaw-specific

  • Skills live under the agent workspace, e.g. ~/.openclaw/workspace/skills/akeyless/. User enables akeyless in Skills and restarts the gateway after changes.
  • Shell commands run as the gateway host user; that user must have working akeyless credentials.

Guardrails

  • Never paste or request Access Keys, API keys, or secret values in chat, logs, or repos.
  • Least-privilege: only commands the user’s role allows; if access denied, point to Akeyless role and folder path, not “retry with more secret text.”
  • Do not commit ~/.akeyless/ or paste profile TOML into threads.

Contrast with 1Password (op)

Akeyless uses akeyless + profiles + optional AKEYLESS_GATEWAY_URL. There is no 1Password-style desktop app unlock in this workflow.

Usage Guidance
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.
Capability Analysis
Type: OpenClaw Skill Name: akeyless Version: 1.0.0 The akeyless skill bundle provides a legitimate interface for the official Akeyless CLI, focusing on secrets management. It includes strong security guardrails in SKILL.md and references/cli-notes.md, explicitly instructing the agent never to request or display secret values, access keys, or profile contents in the chat, and relies on the user to perform authentication locally.
Capability Assessment
✓ 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.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install akeyless
  3. After installation, invoke the skill by name or use /akeyless
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
# Changelog All notable changes to this OpenClaw skill bundle are documented here. ## [1.0.0] — 2026-03-22 First public release of the **Akeyless IO** OpenClaw skill (drives the official **Akeyless CLI** `akeyless` binary). ### Added — `SKILL.md` - Agent playbook for the official **`akeyless`** CLI on the gateway host. - OpenClaw **`metadata.openclaw`**: emoji, **`requires.bins: ["akeyless"]`**, Homebrew install hint (`akeylesslabs/tap/akeyless`). - Workflow: verify CLI, auth outside chat, read-only checks first, gateway/tenant awareness. - Guardrails: no Access Keys or secret values in chat; JSON summaries without leaking sensitive fields. - OpenClaw-specific notes (workspace `skills/` path, gateway user = CLI user). - Short contrast with the bundled **1Password** skill (`op` vs `akeyless` / profiles / gateway URL). ### Added — `references/cli-notes.md` - Links to Akeyless [CLI](https://docs.akeyless.io/docs/cli), [CLI reference](https://docs.akeyless.io/docs/cli-reference), [authentication methods](https://docs.akeyless.io/docs/access-and-authentication-methods). - Install: **macOS** (Homebrew tap), **Linux** (pointer to official download docs). - Profiles: interactive `configure`, `~/.akeyless/profiles/`, non-interactive API-key example (run outside chat). - **SAML:** `configure` + `auth` with placeholders; **`--use-remote-browser`** for headless/SSH; verification step. - Gateway / SaaS: `AKEYLESS_GATEWAY_URL`, TLS trust PEM env var, region/tenant caution. - **`list-items`:** common read-only examples (`--minimal-view`, `--path`, `--filter`, `-t`, `--json`, pagination). - Flag precedence (CLI → env → profile). - Safety: no committing `~/.akeyless/`; access-denied → role/path/gateway. ### Added — `README.md` - **Purpose:** with-skill vs without-skill; one-sentence mission; how OpenClaw loads and runs the playbook. - **What this skill is not:** table (not hosted, not auto-access, not n8n-style, not a policy substitute). - **Agent guardrails** summary. - **Prerequisites** table (OpenClaw, CLI, Akeyless auth, optional gateway). - **Use cases** (inventory, diagnostics, onboarding, safe summaries). - **Install:** ClawHub (`clawhub install`) and manual copy to `~/.openclaw/workspace/skills/`. - **Example prompts:** smoke tests, inventory variants, named `--profile`, SAML re-auth guidance, post-install checks (`openclaw skills info`, new session). - **Publishing** maintainer steps (`clawhub login`, `clawhub publish`). - **File layout** and links to Akeyless + OpenClaw docs. ### Added — `CHANGELOG.md` - This file (release history for the bundle). ### Notes - The skill **does not** ship credentials or replace Akeyless; users install **`akeyless`** and authenticate locally (SAML, API key, etc.). - Symlinks from `~/.openclaw/workspace/skills/` to paths **outside** the workspace are skipped by OpenClaw — use a **copy** of the folder for testing.
Metadata
Slug akeyless
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Akeyless IO?

Akeyless Secrets Management via the official akeyless CLI — install, configure profiles, gateway routing, and safe read/list operations. Use when the user me... It is an AI Agent Skill for Claude Code / OpenClaw, with 134 downloads so far.

How do I install Akeyless IO?

Run "/install akeyless" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Akeyless IO free?

Yes, Akeyless IO is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Akeyless IO support?

Akeyless IO is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Akeyless IO?

It is built and maintained by deanshak (@deanshak); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments