Self Reflection

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

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.

What this means

Sensitive conversation content may be summarized into long-lived memory or instruction files, and a bad or manipulated session could influence future agent behavior.

Why it was flagged

The skill reads prior session transcripts and persists derived lessons into memory and instruction files, so private or adversarial transcript content could be converted into future context.

Skill content
read the JSONL transcript ... tail -50 ~/.openclaw/agents/main/sessions/<sessionId>.jsonl ... Route them: AGENTS.md ... memory/about-user.md ... skills/<skill-name>/SKILL.md
Recommendation

Use only if you want session history to become persistent memory. Add explicit review before writing, avoid copying user instructions verbatim, and keep a clear audit trail or backup of changed files.

What this means

The agent could change files that steer future behavior, and those changes may be hard to notice if the skill runs periodically.

Why it was flagged

The skill authorizes direct file mutation, including agent and skill instruction files, without requiring a user-visible diff or confirmation before applying changes.

Skill content
For each insight, append or edit the appropriate file. Use the `Edit` tool for surgical changes ... Use append ... for daily memory files.
Recommendation

Require a dry-run summary and user approval before edits, restrict writable paths, and prefer appending reviewed notes over modifying core instruction files automatically.

NoteHigh Confidence
ASI10: Rogue Agents
What this means

If scheduled, it may repeatedly inspect recent sessions and write memory/instruction updates without a user initiating each run.

Why it was flagged

The skill discloses periodic autonomous operation, but the provided artifacts do not include an install spec that creates a cron job.

Skill content
Designed to run as a cron job. ... Runs hourly via cron.
Recommendation

Install cron scheduling only intentionally, document how to disable it, and consider making each run produce a proposed diff instead of applying changes automatically.

What this means

The skill may fail or behave differently depending on the local environment, and users may not realize these runtime dependencies are needed.

Why it was flagged

The helper script relies on bash, openclaw, python3, and tail, while the registry metadata declares no required binaries and no install spec.

Skill content
#!/usr/bin/env bash ... sessions_json=$(openclaw sessions --active "$ACTIVE_MINUTES" --json 2>/dev/null) ... echo "$sessions_json" | python3 -c
Recommendation

Declare required binaries and document exactly how the helper script is intended to be invoked.