← 返回 Skills 市场
73
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install ray-delivery-diagnosis
功能描述
Automates delivery lane scans every 4 hours to detect failures, classify issues, update recovery tickets, and attempt specified recovery actions.
安全使用建议
This skill appears to be a runbook that will run local Node scripts and modify mission-control/recovery-ticket files. Before installing or enabling it: 1) Confirm that the runtime environment actually contains the referenced scripts and that you trust their contents — ask for the script sources or inspect them in a safe environment. 2) Verify Node is available and consider declaring it as a required binary. 3) Determine what credentials are needed (Facebook/X tokens, Supabase URL, any posting API keys) and provide them only with least privilege; the skill does not declare these. 4) Run initially in a sandbox/test environment and use dry-run flags as suggested; review the outputs it would write to mission-control and recovery tickets. 5) If you cannot inspect the referenced scripts, treat the skill as untrusted: it could run arbitrary code that reads local dotfiles (~/.openclaw), writes ticket files, or transmits data. 6) Ask the publisher for provenance (source repository, maintainers) and for explicit declarations of required binaries and credentials before using it in production.
功能分析
Type: OpenClaw Skill
Name: ray-delivery-diagnosis
Version: 1.0.0
The skill is classified as suspicious because it utilizes high-risk capabilities such as shell execution and sensitive file access, which are explicitly flagged in the analysis criteria. Specifically, SKILL.md and TEMPLATE.md instruct the agent to execute multiple local scripts (e.g., postiz-publish.mjs, facebook-poster.mjs) and read environment configuration files from other workspaces (~/.openclaw/workspace-jenny/.env). While these actions are aligned with the stated purpose of task recovery and delivery diagnosis, the reliance on shell execution and cross-workspace file access represents a significant security surface.
能力评估
Purpose & Capability
The name/description match the instructions (it is a delivery diagnosis and recovery runbook). However, the SKILL.md repeatedly instructs running Node scripts (e.g., node scripts/tony-blog-publish.mjs, postiz-publish.mjs, facebook-poster.mjs) and accessing local workspaces (e.g., ~/.openclaw/workspace-jenny/.env, mission-control/data/). Despite this, the skill metadata lists no required binaries (node) or environment variables. That mismatch (runs Node but doesn't declare node as required) is an incoherence requiring clarification.
Instruction Scope
Instructions explicitly tell the agent to read and update many local paths (mission-control data, recovery tickets, workspace dotfiles) and to execute platform-publishing scripts that could interact with external services and potentially transmit content. The steps stay within the stated domain (delivery lanes), but they grant broad discretion to run arbitrary local Node scripts and modify persistent ticket files — which is a meaningful scope expansion relative to the minimal metadata provided. The SKILL.md also instructs checking ~/.openclaw/workspace-jenny/.env (a user config file), which is sensitive and is not declared in the skill requirements.
Install Mechanism
This is instruction-only with no install spec and no code files shipped. That minimizes the surface from the skill bundle itself (nothing is downloaded or written by installer). The higher risk is runtime: the agent is instructed to execute local scripts that are expected to exist in the runtime environment.
Credentials
The skill declares no required env vars or primary credentials, yet the instructions expect credentials/config to exist (Facebook/X auth, Supabase URL in ~/.openclaw/workspace-jenny/.env, mission-control ticket write access). Recovery actions will likely require API keys or browser auth. The absence of declared required credentials is disproportionate and obscures what secrets the skill actually needs at runtime.
Persistence & Privilege
always is false and the skill is not requesting any special platform persistence or modification of other skills. It writes/updates local mission-control/recovery ticket files as part of its purpose, which is expected behavior for a recovery runner. No cross-skill or system-wide configuration changes are instructed.
如何使用
- 确保已安装 OpenClaw（本地或 Docker 部署）
- 在对话框中输入安装命令：
/install ray-delivery-diagnosis - 安装完成后，直接呼叫该 Skill 的名称或使用
/ray-delivery-diagnosis触发 - 根据 Skill 的参数说明提供必要输入，即可获得结构化输出
版本历史
v1.0.0
- Initial release of the recovery ticket runner and delivery diagnosis agent.
- Automatically scans all delivery lanes every 4 hours (and on-demand) to detect unresolved blockers, classify failure types, and attempt recovery actions.
- Supports multiple trigger sources, layered lane checks, and detailed failure classification.
- Executes lane-specific recovery actions with capped auto-retries and escalation to human intervention when required.
- Logs actions, updates recovery tickets, and outputs diagnosis reports for each run.
- Implements strict safety and publishing checks to prevent unauthorized or indefinite retries.
元数据
常见问题
Ray Delivery Diagnosis 是什么？
Automates delivery lane scans every 4 hours to detect failures, classify issues, update recovery tickets, and attempt specified recovery actions. 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 73 次。
如何安装 Ray Delivery Diagnosis？
在 OpenClaw 或 Claude Code 对话框中运行命令「/install ray-delivery-diagnosis」即可一键安装，无需额外配置。
Ray Delivery Diagnosis 是免费的吗？
是的，Ray Delivery Diagnosis 完全免费，采用 MIT-0 许可证，可自由下载、安装和使用。
Ray Delivery Diagnosis 支持哪些平台？
Ray Delivery Diagnosis 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。
谁开发了 Ray Delivery Diagnosis？
由 X-RayLuan（@x-rayluan）开发并维护，当前版本 v1.0.0。
推荐 Skills