Token导航 LogoToken导航

Agent Skill · 开发

openclaw-essesseff(OpenClaw essesseff 部署)

openclaw-essesseff 用于辅助部署、云资源、容器和基础设施运维,适合在 OpenClaw 中需要检查配置、整理部署步骤或排查环境问题时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

openclaw-essesseff 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 7,960。

总安装 3,421周安装 144GitHub Stars 公开资料未说明下载 1,198核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.2

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:openclaw-essesseff(OpenClaw essesseff 部署)
来源仓库:https://github.com/adamdurst/openclaw-essesseff
安装命令:
openclaw skills install openclaw-essesseff
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install openclaw-essesseff

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

与 essesseff DevOps 平台集成的云原生部署管理工具。调用公共 API 管理模板、应用、镜像生命周期与环境变量。适用于容器化服务的持续交付与基础设施即代码实践。需配置 API 密钥并遵循平台配额限制,高频调用可能受限。操作直接影响线上环境,建议先在 staging 环境测试变更效果。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install openclaw-essesseff;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

openclaw-essesseff 怎么安装?

在终端执行 openclaw skills install openclaw-essesseff。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

openclaw-essesseff 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

openclaw-essesseff 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

openclaw-essesseff 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

openclaw-essesseff 用的人多吗?

公开数据是累计安装 3,421 次,近一周安装 144 次,下载 1,198 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

openclaw-essesseff 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
openclaw-essesseff

OpenClaw essesseff 部署 · 本页

3,421—接触敏感数据MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
openclaw-essesseff
description
Interact with the essesseff DevOps platform — call the essesseff Public API (templates, organizations, apps, deployments, images, image lifecycle, environments, retention policies, packages) and automate app creation and Argo CD setup using the essesseff onboarding utility. Use when the user wants to create essesseff apps, manage deployments, promote images through the DEV→QA→STAGING→PROD lifecycle, configure Argo CD environments, manage retention policies, or run the essesseff-onboard.sh script.
version
1.0.0
metadata
openclaw
emoji
🦞
homepage
https://github.com/essesseff/essesseff-onboarding-utility
primaryEnv
ESSESSEFF_API_KEY
requires
bins
env

essesseff Skill

This skill covers two complementary ways to work with the essesseff DevOps platform:

  1. essesseff Public API — direct HTTP calls for managing templates, organizations, apps, images, deployments, environments, packages, and retention policies.
  2. essesseff Onboarding Utility — shell scripts that automate app creation and Argo CD deployment setup.

Quick Reference

Base URL: https://www.essesseff.com/api/v1 (use www to avoid 307 redirects)

Authentication: All requests require X-API-Key: ess_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx header.

Rate limit: 3 requests per 10 seconds. Headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset.

Path structure:

  • Global (no account needed): /api/v1/global/...
  • Account-specific: /api/v1/accounts/{account_slug}/... — API key must belong to the account_slug in the path or a 403 is returned.

API Reference Files

For full endpoint details, request/response examples, and query parameters, see:

ReferenceContents
references/api-overview.mdAuth, base URL, rate limiting, error codes
references/api-templates.mdGlobal templates, account-specific templates
references/api-organizations.mdList and detail GitHub orgs for an account
references/api-apps.mdCreate, list, get, update apps; list deployments
references/api-images.mdList images, get image by tag
references/api-images.mdImage lifecycle: get state, transition state
references/api-environments.mdGet environment; set Argo CD URL; DEV→QA→STAGING→PROD lifecycle actions
references/api-packages.mdGet GitHub API payloads for expired package deletion
references/api-retention-policies.mdList and update retention policies

API Endpoint Map

Global

MethodPathPurpose
GET/global/templatesList global templates (optional `?language=go\python\node\java\rust\php`)
GET/global/templates/{template_name}Get global template details

Account-Specific (all require matching API key)

MethodPathPurpose
GET/accounts/{account_slug}/templatesList account templates
GET/accounts/{account_slug}/templates/{template_name}Get account template details
GET/accounts/{account_slug}/organizationsList orgs for account
GET/accounts/{account_slug}/organizations/{org_login}Get org detail + app list
GET/accounts/{account_slug}/organizations/{org_login}/appsList apps
POST/accounts/{account_slug}/organizations/{org_login}/apps?app_name={name}Create app
GET/accounts/{account_slug}/organizations/{org_login}/apps/{app_name}Get app detail
PATCH/accounts/{account_slug}/organizations/{org_login}/apps/{app_name}Update app
GET.../apps/{app_name}/deploymentsList deployments
GET.../apps/{app_name}/imagesList images
GET.../apps/{app_name}/images/{image_tag}Get image by tag
GET.../apps/{app_name}/images/{image_tag}/lifecycleGet image lifecycle state
POST.../apps/{app_name}/images/{image_tag}/lifecycleTransition image lifecycle state
GET.../apps/{app_name}/environments/{env}Get current env deployment
POST.../apps/{app_name}/environments/{env}/set-argocd-application-urlSet/clear Argo CD URL
POST.../apps/{app_name}/environments/DEV/declare-rcMark DEV image as RC
POST.../apps/{app_name}/environments/QA/accept-rcAccept RC → deploy to QA
POST.../apps/{app_name}/environments/QA/reject-rcReject RC
POST.../apps/{app_name}/environments/QA/declare-stableMark QA image as STABLE
POST.../apps/{app_name}/environments/QA/declare-rejectedMark QA image as REJECTED
POST.../apps/{app_name}/environments/STAGING/deploy-stableDeploy STABLE to STAGING
POST.../apps/{app_name}/environments/PROD/deploy-stableDeploy STABLE to PROD (no OTP)
GET.../apps/{app_name}/notifications-secretGet notifications-secret.yaml for Argo CD
GET.../apps/{app_name}/packages/delete-packagesGet expired package deletion payloads
GET.../apps/{app_name}/retention-policiesList retention policies (filter by ?state=)
PATCH.../apps/{app_name}/retention-policies?state={state}Create or update a retention policy for a lifecycle state

Image Lifecycle State Machine

Images progress through states in this order:

BUILD → DEV → RC → QA → STABLE → STAGING → PROD
              ↑  ↓  ↓
            REJECTED

Key transitions via API:

  • DEV/declare-rc — promotes current DEV image to RC (no body)
  • QA/accept-rc — body: {"image_tag": "v1.2.3"} → sets QA, deploys to QA
  • QA/reject-rc — body: {"image_tag": "v1.2.3"} → sets REJECTED
  • QA/declare-stable — no body → sets STABLE on current QA image
  • QA/declare-rejected — no body → sets REJECTED on current QA image
  • STAGING/deploy-stable — body: {"image_tag": "v1.2.3"} → deploys to STAGING
  • PROD/deploy-stable — body: {"image_tag": "v1.2.3", "deployment_note": "CR#123"} → deploys to PROD (no OTP required via API)

Alternatively, use POST .../images/{image_tag}/lifecycle with body {"state": "QA"} for direct lifecycle transitions.

Onboarding Utility Reference

For shell-script-based automation (no API calls required), see:

ReferenceContents
references/onboarding-utility.mdFull guide: setup, commands, how it works
references/prerequisites.mdSystem binaries, PATs, K8s/Argo CD prereqs
references/non-subscriber-mode.mdClone/replace/push workflow without a subscription

The utility (essesseff-onboard.sh) accepts:

  • --list-templates — list available templates
  • --create-app — create all 9 repos (via API for subscribers, clone/replace/push for non-subscribers)
  • --setup-argocd dev,qa,staging,prod — configure Argo CD for each environment
  • --non-essesseff-subscriber-mode — no essesseff API required
  • --config-file .essesseff — path to config file
  • --verbose — debug output

Common Errors

CodeMeaning
400Invalid request parameters
401Invalid or missing API key
403API key does not match the account_slug in the path
404Resource not found
429Rate limit exceeded — wait and retry
500Server error

平台分布

OpenClaw

82.51%
按下载量换算988

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills