OpenClaw Skill Governance (Balanced Dynamic Core Pool)
PassAudited by ClawScan on May 1, 2026.
Overview
This is a disclosed local skill-governance policy, but it can affect which skills are selected or quarantined and it references helper scripts that are not included.
This skill appears purpose-aligned and locally scoped. Before using it, make sure you trust and review any referenced scripts, keep skill-registry.json under version control or backed up, and manually check important quarantine, retirement, or routing changes.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken or premature status change could cause a useful skill to be skipped, quarantined, or deprioritized.
The skill explicitly governs automatic skill routing and status changes, which can influence what the agent does later.
Core pool tuning and automatic promotion/demotion ... Route execution chain (core -> ready -> explore)
Review changes to skill-registry.json, keep a backup or version history, and require human review before important quarantine or retirement decisions.
The reviewed artifact does not include the implementation of the referenced scripts, so users should not assume those scripts have been reviewed as part of this package.
The skill references helper scripts, but the supplied package contains only SKILL.md and no script files or install spec.
`scripts/reconcile-ready.ps1 -Root <workspace>` ... `scripts/weekly-cleanup.ps1 -Root <workspace>`
Only run helper scripts that are present from a trusted source and review their contents separately before use.
If the registry is edited incorrectly or tampered with, future routing decisions may be based on bad status information.
The skill depends on persistent local registry state to make future governance and routing decisions.
Source of truth - `skill-registry.json`
Store the registry in a trusted workspace, protect it from untrusted edits, and review unexpected status changes.
A short run of failures or a stale registry entry could cause a skill to be quarantined or retired from routing.
Failure records and cleanup decisions can propagate into future availability and routing decisions for other skills.
Quarantine after 2 consecutive failures ... Weekly cleanup (retire stale or missing skills)
Use conservative thresholds for important skills and verify failure records before allowing retirement or quarantine to stand.