← Back to Skills Marketplace
122
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install stuck-session-diagnosis
Description
Use when another Claude Code session appears frozen, stuck, or abnormally slow and needs process-level diagnosis and reporting.
Usage Guidance
This skill appears to be a straightforward helper for inspecting local agent processes and assembling a diagnosis report. Before installing or invoking it, be aware that diagnosing a process often requires reading process tables and debug logs — those logs can contain sensitive information. If you run this on a multi-user machine or a system with sensitive application logs, consider: (1) running diagnostics interactively rather than allowing autonomous invocation, (2) restricting which log directories the agent may read, and (3) ensuring the agent runs with the minimum necessary permissions. If you need more assurance, ask the skill author to (a) list the exact commands/paths it will read, or (b) scope log inspection to specific known agent log locations.
Capability Analysis
Type: OpenClaw Skill
Name: stuck-session-diagnosis
Version: 1.0.0
The skill bundle is designed for diagnosing frozen or slow Claude Code sessions by inspecting process metrics (CPU, RSS) and logs. The instructions in SKILL.md are purely diagnostic, include explicit guardrails against unauthorized process termination, and show no signs of malicious intent, data exfiltration, or prompt injection.
Capability Assessment
Purpose & Capability
The name/description (diagnose frozen or slow local agent sessions) match the SKILL.md workflow steps (list processes, check CPU/RSS/state/children, sample, inspect debug logs, produce report). No unrelated credentials, binaries, or installs are requested.
Instruction Scope
Instructions stay on-topic (process inspection and log review) and include guardrails (do not kill processes by default). However, they are permissive about which debug logs to inspect ('when possible') and do not explicitly constrain file paths or data collection — this could lead the agent to read broader system or user logs while diagnosing.
Install Mechanism
Instruction-only skill with no install spec and no code files. Lowest-risk delivery: nothing is written to disk by an installer.
Credentials
No environment variables, credentials, or config paths are required. This is proportionate to a local diagnostic skill.
Persistence & Privilege
always is false and the skill does not request persistent/system-wide configuration or elevated/ongoing privileges. The agent may run it autonomously per platform defaults, which is expected for skills.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install stuck-session-diagnosis - After installation, invoke the skill by name or use
/stuck-session-diagnosis - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial extraction from local Claude Code source
Metadata
Frequently Asked Questions
What is Stuck Session Diagnosis?
Use when another Claude Code session appears frozen, stuck, or abnormally slow and needs process-level diagnosis and reporting. It is an AI Agent Skill for Claude Code / OpenClaw, with 122 downloads so far.
How do I install Stuck Session Diagnosis?
Run "/install stuck-session-diagnosis" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Stuck Session Diagnosis free?
Yes, Stuck Session Diagnosis is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Stuck Session Diagnosis support?
Stuck Session Diagnosis is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Stuck Session Diagnosis?
It is built and maintained by wimi321 (@wimi321); the current version is v1.0.0.
More Skills