Nm Leyline Error Patterns
v1.0.0Standardized error handling patterns with classification, recovery, and logging strategies. error handling, error recovery, graceful degradation, resilience.
⭐ 0· 50·1 current·1 all-time
by@athola
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (error handling, recovery, logging, resilience) align with the actual content: classification, recovery strategies, agent-level escalation, and logging patterns. The single declared config requirement (night-market.usage-logging) is relevant to logging behavior. Examples referencing services (gemini, Qwen) are illustrative and reasonable for a cross-service error-patterns library.
Instruction Scope
SKILL.md is instruction-only and stays within error-classification and recovery guidance. It includes patterns that mention writing summaries to files, logging full context, and calling send_alert(log_entry) — these are reasonable for a logging/recovery library but imply file I/O and external alerting. The docs also reference user config paths (e.g. ~/.claude/leyline/) which are outside the declared night-market.usage-logging config and should be reviewed for scope.
Install Mechanism
No install spec and no code files — lowest-risk distribution model. Nothing is downloaded or written to disk by the skill itself beyond the guidance in the text.
Credentials
No environment variables or credentials are requested. The declared config path (night-market.usage-logging) is proportionate to a logging/alerting skill. No unrelated secrets or broad credential access are required.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent or elevated platform presence. The guidance includes writing to files or checkpoints as recovery patterns, which is normal for a resilience library but not a platform-level privilege escalation.
Assessment
This skill is a documentation-only set of error-handling patterns and appears coherent with its purpose. Before installing or enabling it, check: (1) where logs/alerts will be sent (the snippets call send_alert and log full context but don't specify destinations), (2) what the night-market.usage-logging config controls and who can read it, and (3) any filesystem paths referenced in your deployments (e.g. ~/.claude/leyline/ or checkpoint files) to ensure you’re comfortable with the skill's suggested file I/O. No credentials or installs are required, and there are no code files — the main risk is accidental logging of sensitive context if you wire up alerts/logging without review.Like a lobster shell, security has layers — review code before you run it.
latestvk97b3rxeyrcj54kwy9t42sxkh984rm5e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🦞 Clawdis
Confignight-market.usage-logging