← 返回 Skills 市场
40
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install ops-issue-followup
功能描述
Use when the user asks Codex to follow up, analyze, investigate, or is @mentioned for a project/system maintenance or operations issue. Guides Codex to clari...
使用说明 (SKILL.md)
Ops Issue Follow-up
Use this skill as a daily maintenance and operations assistant for project or system issues. The goal is to keep investigation aligned before going deep.
Workflow
- Confirm the issue
- Restate the observed symptom, expected behavior, impact, time range, and examples.
- Separate confirmed facts from assumptions, memory, and unverified clues.
- If key facts are missing, ask concise follow-up questions.
- Identify ownership and related projects
- Determine which project, service, system, table, queue, job, or external dependency is involved.
- If ownership cannot be inferred from the request or current context, ask the user before investigating deeply.
- Gather project context
- Prefer project-local context first:
AGENTS.md, README, architecture docs, runbooks, config examples, tests, and relevant source paths. - If available, use llm wiki or similar knowledge base for historical decisions and operational context.
- Treat wiki/history as context, not proof; verify against code, logs, configs, or current runtime evidence when possible.
- Align on the analysis direction
- Summarize the likely investigation branches.
- Call out the recommended branch and why.
- Ask for confirmation when multiple plausible directions could lead to very different work.
- Investigate in the project
- Switch into the relevant project/workspace before reading code or running commands.
- Enumerate entrypoints before tracing implementation details.
- For operational data issues, map: data record -> producer -> input source -> transport/proxy/dependency -> persistence/reporting.
- When uncertain, ask the user instead of inventing missing runtime facts.
- Resolve or narrow the issue
- Provide confirmed findings, likely causes, and remaining unknowns.
- If code/config changes are needed, state target files and intent before editing.
- If validation is possible, run concrete verification commands and report actual results.
- Summarize and preserve
- End with a concise incident-style summary: symptom, scope, root cause or likely cause, evidence, fix/next steps.
- When useful, propose writing the summary to llm wiki, including a suggested title and structure.
安全使用建议
Install this if you want a disciplined checklist for operational issue follow-up. Be aware it may guide Codex to inspect project materials and propose saving an incident summary, so use it in workspaces where that level of investigation is appropriate.
能力评估
Purpose & Capability
The artifact coherently supports its stated purpose: helping Codex clarify, investigate, verify, and summarize project or system maintenance issues.
Instruction Scope
Instructions emphasize confirming facts, asking when ownership or facts are unclear, using project-local evidence, and reporting confirmed findings; no prompt override, deception, or unrelated authority was found.
Install Mechanism
The package contains only SKILL.md and a small agent YAML metadata file; no installer, dependency, script, or automatic execution mechanism is present.
Credentials
The workflow may lead an agent to read project docs, code, configs, logs, or runtime evidence when investigating an operations issue, which is expected for this purpose and should remain user-directed.
Persistence & Privilege
The only persistence-like behavior is proposing an incident summary for llm wiki archival when useful; it does not direct automatic writing, privilege escalation, background execution, or credential use.
如何使用
- 确保已安装 OpenClaw（本地或 Docker 部署）
- 在对话框中输入安装命令：
/install ops-issue-followup - 安装完成后，直接呼叫该 Skill 的名称或使用
/ops-issue-followup触发 - 根据 Skill 的参数说明提供必要输入，即可获得结构化输出
版本历史
v1.0.0
- Initial release of ops-issue-followup skill
- Guides investigation and follow-up for project/system maintenance and operations issues
- Structured workflow: confirm issue, identify ownership, gather context, align analysis, investigate, resolve, and summarize
- Emphasizes clarifying facts, verifying evidence, and asking for missing information
- Designed to enable consistent, accountable, and well-documented incident follow-up and analysis
元数据
常见问题
ops-issue-followup 是什么？
Use when the user asks Codex to follow up, analyze, investigate, or is @mentioned for a project/system maintenance or operations issue. Guides Codex to clari... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件，目前累计下载 40 次。
如何安装 ops-issue-followup？
在 OpenClaw 或 Claude Code 对话框中运行命令「/install ops-issue-followup」即可一键安装，无需额外配置。
ops-issue-followup 是免费的吗？
是的，ops-issue-followup 完全免费，采用 MIT-0 许可证，可自由下载、安装和使用。
ops-issue-followup 支持哪些平台？
ops-issue-followup 跨平台运行，可在任意部署了 OpenClaw / Claude Code 的环境中使用（cross-platform）。
谁开发了 ops-issue-followup？
由 xiluoduyu（@xiluoduyu）开发并维护，当前版本 v1.0.0。
推荐 Skills