Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Agent Harness Doctor
v1.0.0Automated audit and fix for OpenClaw agent harnesses. Scans your setup, scores on 8 dimensions (Session Bridge, Startup Sequence, Smoke Test, Atomic Checkpoi...
⭐ 0· 33·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
Name/description align with behavior: the skill scans repository files (AGENTS.md, memory/*) and can create agent-progress.json and update AGENTS.md. The actions performed (diagnose and apply fixes to harness files) are coherent with the stated purpose.
Instruction Scope
SKILL.md declares a tool 'harness_check' with permission 'read_only' but the implementation accepts a 'fix_apply' list and will call apply_fix to write files (create agent-progress.json, modify AGENTS.md). SKILL.md also lists fixes like 'inject self-check prompt into system instructions' that are not implemented in the provided code, indicating inconsistency between described and actual behavior. The skill will modify workspace files without prompting for backups — this is expected for an auto-fixer but should be explicit and safeguarded.
Install Mechanism
Instruction-only skill with a small included script and no install spec — nothing is downloaded or installed system-wide.
Credentials
No environment variables, credentials, or external endpoints are requested. The code operates only on local workspace files.
Persistence & Privilege
The skill does not request persistent 'always' inclusion. It does write and edit files in the repository (workspace root and AGENTS.md). This is normal for a repair tool but means it can alter your agent harness and documentation — run on a copy or ensure backups.
What to consider before installing
This skill appears to do what it says (diagnose and auto-fix harness files) but has two important surprises: 1) the 'harness_check' tool is advertised as read-only yet can apply fixes when given fix IDs, and 2) it will create/modify files in your workspace (agent-progress.json, AGENTS.md) without making backups. Before installing or running: (a) run it in a disposable/sandbox copy of your repo, (b) review the created/changed files (agent-progress.json, AGENTS.md) after a diagnostic run and before allowing any auto-fix, (c) prefer invoking apply_fix explicitly rather than relying on harness_check's fix_apply to avoid accidental writes, and (d) if you accept it, ensure you have a VCS snapshot or other backup so changes can be reviewed/reverted. If you need higher assurance, ask the publisher for: explicit backup behavior, a dry-run mode for apply_fix, and correction of the metadata so 'harness_check' is not labeled read-only when it can modify files.Like a lobster shell, security has layers — review code before you run it.
auditvk974d2x9nghw42k8wnpa0tmje1840mqddiagnosticvk974d2x9nghw42k8wnpa0tmje1840mqdharnessvk974d2x9nghw42k8wnpa0tmje1840mqdlatestvk974d2x9nghw42k8wnpa0tmje1840mqdoptimizationvk974d2x9nghw42k8wnpa0tmje1840mqd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.