Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
- Clarified that `/sc fallback` now performs a config file audit only: it checks fallback entries exist in your config, but does not make network calls or test real connectivity. - Updated usage documentation for `/sc fallback` to reflect its new scope and clarify validated config structure. - Adjusted fallback output examples and logic section to match config-audit behavior. - No functional logic changes outside fallback validation scope.
What This Skill Does
Runtime safety verification suite that consolidates model version pinning, fallback chain validation, cache staleness detection, and cross-session state checks. All operations are local file and metadata reads with no external API calls or data transmission. Consolidates four separate skills into a single aliased command.
Replaces four separate skill invocations with a single aliased suite that integrates directly with HEARTBEAT for automated periodic verification.
When to use it
- Catching model version drift before a scheduled agent run
- Verifying fallback config entries exist after modifying agent settings
- Clearing stale cache entries during periodic workspace maintenance
- Detecting orphaned lock files left by a previously crashed session
- Running automated pre-flight safety checks on every session start via HEARTBEAT
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: run a full safety check before starting the agent workflow
- 1Run /sc model to compare active model version string against the pinned value in config
- 2Run /sc fallback to confirm fallback chain entries are declared in safety-checks.yaml
- 3Run /sc cache to identify cache entries older than the configured TTL
- 4Run /sc session to check for stale lock files or orphaned temp artifacts in output/safety/
Four-check report with pass/warn/fail status per check; results written to output/safety/ logs