Project Memory Guard
v1.0.0Enforce project boundaries and memory writeback rules before anything enters project memory. Use before: writing notes into project memory, saving outputs/ta...
⭐ 0· 76·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and required inputs all align with a memory-write validation/guard role. The skill requests no binaries, env vars, or installs that would be unnecessary for this purpose.
Instruction Scope
SKILL.md stays within the guard role and describes inputs, outputs, hard rules, normalization, and failure handling. Minor issues: rule table references 'project_id' while inputs use 'candidate_project_id' (inconsistent naming); 'Cross-project ambiguity' is referenced but not defined (no algorithm or detection criteria); normalized_record schema is underspecified (only some fields described). These should be clarified so implementations cannot misinterpret the guard.
Install Mechanism
No install spec and no code files — lowest disk/installation risk (instruction-only).
Credentials
No credentials, env vars, or config paths are requested; this is proportionate to the stated task.
Persistence & Privilege
always:false, no persistent/system-wide changes requested. The skill does not request autonomous elevation or modify other skills/configs.
Assessment
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.Like a lobster shell, security has layers — review code before you run it.
latestvk974j48yjcmb237hp5gy4rh2a183p76g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.