Memory Curator
Analysis
Memory Curator is a local memory-digest tool, but its helper script builds read/write paths from an unvalidated date argument, so malformed input could access or overwrite files outside the intended digest area.
Findings (3)
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.
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.
DATE="${1:-$(date -u +%Y-%m-%d)}"
LOG_FILE="$MEMORY_DIR/$DATE.md"
DIGEST_FILE="$MEMORY_DIR/digests/$DATE-digest.md"
...
cat > "$DIGEST_FILE" << EOFThe first script argument is inserted directly into both input and output file paths, and the output file is overwritten, without validating that the value is actually a date or rejecting path separators.
Set up end-of-day cron to auto-generate skeletons: ... Task: Run generate-digest.sh, fill Summary/Learnings/Tomorrow, commit
The artifact suggests optional scheduled automation that would keep generating and committing memory artifacts after setup.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
memory/ ├── INDEX.md ├── digests/ ├── topics/ └── daily/ ... Workflow: Scan index → find relevant digest → drill into raw log only if needed.
The skill is designed to create persistent memory digests and indexes that future agent sessions may read and rely on.
