v1.1.0

Correction Memory

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 6:03 AM.

Analysis

This skill appears purpose-aligned, but it stores corrections persistently and reuses them automatically to steer future agents.

GuidanceThis looks coherent for a correction-memory skill. Before installing, understand that corrections become persistent instructions for future agents, so keep them specific, do not include secrets, and review the workspace correction files if future agents start behaving unexpectedly.

Findings (2)

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.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Unexpected Code Execution

SeverityLowConfidenceHighStatusNote

SKILL.md

cp references/correction-tracker-template.js $OPENCLAW_WORKSPACE/lib/correction-tracker.js
node $OPENCLAW_WORKSPACE/lib/correction-tracker.js

The installation instructions ask the user to copy and run an included JavaScript helper. This is disclosed and central to the skill, but it is still local code execution.

User impactRunning the helper allows it to create and update correction-memory files in the chosen workspace.

RecommendationInstall it only in the intended workspace and inspect the helper before running it if you are concerned about local file changes.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Memory and Context Poisoning

SeverityMediumConfidenceHighStatusNote

SKILL.md

automatically injects it into future spawns of the same agent type

The skill intentionally turns logged corrections into persistent context for future agents, which is useful but means incorrect or overly broad corrections can influence later tasks.

User impactA bad, stale, or too-general correction could steer future agents for up to 30 days, and any sensitive text included in a correction would be stored locally in the workspace.

RecommendationOnly log deliberate corrections, avoid putting secrets in correction text, and periodically review or delete files under $OPENCLAW_WORKSPACE/memory/corrections.