Distributed Failure Analyzer
v1.0.0Diagnose distributed system failures caused by network faults, unreliable clocks, or process pauses — and map each to its correct mitigation. Use when: a nod...
⭐ 0· 61·0 current·0 all-time
byHung Quoc To@quochungto
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and tasks (classify network/clock/process faults, scan codebases for timing anti-patterns, recommend mitigations) match the declared inputs (codebase, documents, verbal descriptions) and the declared tools (Read, Write, Grep). Dependencies on other analysis selector skills are reasonable for cross-references.
Instruction Scope
SKILL.md instructs scanning repository files, infra manifests, runbooks, and architecture descriptions — this is within the skill's purpose. Note: because it expects to read project files and incident reports, it will access any sensitive data present in those locations (secrets, credentials, or telemetry) if the agent has Read permission.
Install Mechanism
No install spec and no code files: instruction-only skills present minimal install risk (nothing is written to disk by an installer).
Credentials
The skill requests no environment variables, credentials, or config paths. Its declared tool set (Read/Write/Grep) is appropriate for the intended codebase analysis and report generation.
Persistence & Privilege
always is false and there are no privileged install actions. The skill does not request permanent presence or modifications to other skills or system-wide settings.
Assessment
This is an instruction-only analyzer that will read your repository, manifests, and incident documents to produce a failure-analysis report. That behavior is expected and coherent with its purpose, but before using it: (1) don't run it on directories containing sensitive secrets, credentials, or private telemetry you don't want read; (2) review the report output and any files it writes (it needs Write permission to produce reports); (3) if you need tighter control, run the analysis in a sanitized or isolated copy of the codebase (remove secrets, narrow the filesystem scope) or request an explanation of exactly which files it scanned. Autonomous invocation is allowed by default on the platform — combine that with careful scoping of read/write permissions if you want to limit the agent's access surface.Like a lobster shell, security has layers — review code before you run it.
bookforgevk97aqevny3be8d7xtvv25swt5x84nnmplatestvk97aqevny3be8d7xtvv25swt5x84nnmptags:vk97aqevny3be8d7xtvv25swt5x84nnmp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📚 Clawdis