Project Memory Guard

Enforce project boundaries and memory writeback rules before anything enters project memory. Use before: writing notes into project memory, saving outputs/ta...

This instruction-only skill is coherent for enforcing memory writeback rules and is low-risk in itself because it requests no installs or credentials. Before installing or relying on it, verify these practical points: 1) Fix the small naming inconsistency (candidate_project_id vs project_id) so implementations don't treat missing fields incorrectly. 2) Define how 'cross-project ambiguity' is detected (rules/heuristics) and what 'cleanup' entails. 3) Provide an explicit normalized_record schema (which fields are allowed, types, max sizes) and document whether and how sensitive data in raw_content is redacted — storing raw_content can retain PII/sensitive secrets. 4) Ensure the guard is actually enforced in your agent pipeline (SKILL.md are instructions; an integration might not implement them correctly). 5) Expose configuration for the confidence threshold (0.6) and provide test vectors for accept/reroute/reject cases. 6) Add audit/logging guidance so decisions are traceable. If you need stronger guarantees, require the skill to be implemented as code with tests and explicit input validation rather than only prose instructions.

Type: OpenClaw Skill Name: project-memory-guard Version: 1.0.0 The project-memory-guard skill is a data validation and normalization utility designed to enforce schema integrity for project-related records. It defines clear rules for accepting, rejecting, or rerouting content based on metadata presence and confidence scores, with no evidence of malicious intent, data exfiltration, or unauthorized execution.