Root Cause Analysis
v1.0.0Use logic tree approach to identify root causes of business problems. Use when diagnosing performance issues, process failures, or customer behavior patterns.
⭐ 0· 124·0 current·0 all-time
by@linuszz
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the content: a methodology for diagnosing business problems. The skill declares no binaries, env vars, or config paths and does not ask for access to unrelated services. (Note: source/homepage are not provided, but that is an administrative/metadata gap rather than an incoherence with capability.)
Instruction Scope
SKILL.md is a structured, prescriptive framework (logic trees, MECE, 5 Whys) and output templates. It contains no commands, no file reads, and no instructions to access environment variables or external endpoints beyond general advice to 'gather data' — which is expected for this kind of analysis but does not itself request specific secrets or paths.
Install Mechanism
There is no install spec and no code files. As an instruction-only skill, nothing is written to disk and no third-party packages are pulled in.
Credentials
The skill requires no environment variables, credentials, or config paths. Its guidance about gathering data is generic and does not request or reference any specific secret or external service credentials.
Persistence & Privilege
The skill is not marked always:true and does not request elevated or persistent system presence. It will run only when invoked and contains no installation steps that modify agent/system configuration.
Assessment
This skill is a harmless, instruction-only framework for performing root cause analysis. Before installing: (1) note that the skill’s source and homepage are missing — if you prefer published/maintained skills, look for one with an identifiable author or repo; (2) the skill will not itself access your data or credentials, but when you use it you may be prompted (by the agent or by your own workflow) to provide business data — avoid pasting secrets or credentials into prompts; (3) validate any conclusions the skill produces against your actual data sources (the skill describes a methodology, not automated data gathering); and (4) if you plan to combine this skill with other skills that do access systems/data, review those other skills’ permissions and env requirements for least privilege.Like a lobster shell, security has layers — review code before you run it.
latestvk97f99zrrgbb5xgv3eg9yanv5s83c2yw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.