ClawHub Retry & Fallback
v1.0.1ClawHub平台工具调用失败自动重试与降级处理Skill | Automatic retry and fallback handling for ClawHub Agent task failures
⭐ 0· 218·1 current·1 all-time
byLv Lancer@kaiyuelv
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (retry, fallback, degradation for ClawHub agents) match the provided modules: retry_handler, exception_classifier, fallback_manager, degradation_handler, audit_logger, and config_manager. There are no unrelated required binaries, env vars, or config paths declared.
Instruction Scope
SKILL.md and examples restrict actions to configuring and invoking local retry/fallback/degradation logic and exporting logs. Example code shows calling external APIs (placeholder https://api.example.com) but that is user-driven sample code — the skill itself does not embed hidden remote endpoints or instruct the agent to read unrelated system state. The skill will write logs and configs to disk (./logs and configurable paths) and can export files; consider where those files are stored.
Install Mechanism
No install spec in metadata (instruction-only install via pip -r requirements.txt is recommended in SKILL.md). requirements.txt lists small, well-known Python packages (retry, pyyaml, python-json-logger). Nothing indicates an unsafe external installer or arbitrary download URL.
Credentials
The skill declares no required environment variables or credentials. Code interacts with local filesystem (logs, config) and loads a local YAML config; that aligns with purpose. There are no unexpected credential accesses in the reviewed files.
Persistence & Privilege
The skill does not request always: true or other elevated platform privileges. It persists logs and optionally writes config files (save_config) under provided paths; this is consistent with an audit/config manager and not a privilege escalation.
Assessment
This skill appears coherent with its stated purpose. Before installing, do the following: 1) Run the test suite and examples in an isolated environment to confirm runtime behavior (the package writes audit logs and may create config files under ./logs and config/). 2) Review/confirm any backup functions you register (fallback.register_backup) do not themselves call untrusted remote endpoints or handle secrets — the fallback manager executes user-provided functions. 3) Note minor implementation issues in the included files (missing imports/typos in truncated code paths) — expect potential runtime errors; run in a sandbox first. 4) If you will store logs in a shared location, ensure sensitive data is not logged or is redacted. If you want higher assurance, request the full untruncated source or run a security code review focusing on any file I/O and any user-supplied callback execution paths.Like a lobster shell, security has layers — review code before you run it.
latestvk9790kks1jmawyddgsazbpc8b982xm3h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.