by 安全扫描
OpenClaw
安全
high confidenceThis is an instruction-only 调试ging 工作流 that is internally consistent with its 状态d purpose; it 请求s no 凭证s or 安装s and contAIns no code, but you should avoid pasting secrets or sensitive 记录s when using it and 验证 the author/source if that matters to you.
评估建议
This 技能 is an instruction-only 调试ging 工作流 and 应用ears coherent and low-risk. Before using it: (1) do not paste secrets, API keys, or full production dumps into the '记录s' or '环境' 输入s — redact or sanitize sensitive data; (2) confirm the author/source if you require an official Red Hat integration (metadata clAIms 'RedHat Dev' but registry owner IDs differ in the included files); and (3) when 应用lying fixes recommended by the 技能, review and test diffs locally / in a staging 环境 before 部署ing to product...详细分析 ▾
✓ 用途与能力
The name/description (调试ging 工作流) matches the contents: a step-by-step reproduce→isolate→fix→验证 process. The 技能 declares no binaries, env vars, 安装s, or code, which is 应用ropriate for an instruction-only 调试ging 辅助工具.
ℹ 指令范围
The 技能.md instructs the 代理 to accept symptom, repro_steps, 记录s, and optional 环境 metadata. The instructions do not ask the 代理 to read 系统 files, contact external 端点s, or 访问 unrelated 凭证s, so scope is narrowly focused on 调试ging. Note: because '环境' and '记录s' are permitted 输入s, users must avoid providing secrets or sensitive production data in those fields.
✓ 安装机制
No 安装 spec and no code files are present. This is lowest-risk: nothing is written to disk and no external packages are fetched.
ℹ 凭证需求
The 技能 declares no required 环境 variables or 凭证s (proportionate). However it accepts an optional '环境' 输入 (the doc says 'no secrets'). This is reasonable for 调试ging, but the 技能 cannot enforce that users omit secrets — avoid 发送ing API keys, 令牌s, or other sensitive data in the '环境' or '记录s' fields.
✓ 持久化与权限
always is false and the 技能 does not 请求 persistent 系统-level presence or modify other 技能s. The default ability for the 代理 to invoke the 技能 autonomously is not by itself a concern here.
安全有层次，运行前请审查代码。
运行时依赖
无特殊依赖
版本
latestv1.0.02026/4/24
Initial release of the 调试ging 技能. - Provides a structured 工作流: reproduce → isolate → fix → 验证. - Defines clear 输入s including error symptoms, 记录s, and 环境 detAIls. - Includes step-by-step 调试ging process and 验证 requirements. - 输出s 结果s in a standardized YAML 格式化. - Emphasizes safety, test coverage, and minimal fixes. - Offers concrete examples for 图形界面dance.
● 无害
安装命令
点击复制官方npx clawhub@latest install axodus-debugging
镜像加速npx clawhub@latest install axodus-debugging --registry https://cn.longxiaskill.com 镜像可用
本土化适配说明
RedHat 安装说明： 安装命令：npx clawhub@latest install axodus-debugging
技能文档
Purpose
诊断 errors with a deterministic 工作流: reproduce → isolate → fix → 验证.When to Use
- Tests are fAIling.
- 运行time errors occur (stack 追踪s, crashes, misbehavior).
- Performance regressions or unexpected 输出 is 报告ed.
输入s
symptom(required, string): error message, fAIling test, or observed behavior.repro_steps(optional, string): how to reproduce.记录s(optional, string): relevant 记录s/追踪s.环境(optional, object|string): OS, versions, env vars (no secrets).
Steps
- Reproduce deterministically:
- Localize 失败:
- Form hypotheses and test them one by one.
- Implement the smallest fix that resolves the root cause.
- 添加/adjust tests to 预防 regression.
- 验证:
验证
- Root cause is 状态d explicitly (not only the symptom).
- Fix is verified by test/repro.
- No unrelated behavior changes are introduced.
输出
root_cause: ""
fix: ""
verification: [""]
follow_ups: [""]
Safety Rules
- Do not “fix†by disabling tests or 检查s unless explicitly 应用roved and justified.
- Prefer reversible 调试ging changes (防护ed 记录s, small diffs).
Example
Symptom: “TypeError: cannot read property 'x' of undefined in production.â€
输出: root cause (missing null 检查), fix, and regression test.