Nm Leyline Content Sanitization
v1.0.0Sanitization guidelines for external content
⭐ 0· 42·1 current·1 all-time
by@athola
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name and description match the content of SKILL.md: a checklist for sanitizing external content. However, the file references an automated PostToolUse hook (sanitize_external_content.py) and lists version 1.8.2 while the registry metadata is 1.0.0; since no code is bundled, the enforcement behavior is external to this skill and should be verified in the runtime environment.
Instruction Scope
The instructions stay within scope (sanitizing external inputs): size limits, removal of tags/patterns/zero-width characters, HTML/CSS hiding detection, and explicit bans on dangerous operations (eval/exec/shell=True/pickle/yaml.load). The guidance does not ask for unrelated file reads, credentials, or system access.
Install Mechanism
No install spec or code files are present (instruction-only). This minimizes on-disk risk. The SKILL.md mentions a hook filename but provides no installation artifacts — the presence of that hook is outside the skill.
Credentials
No environment variables, credentials, or config paths are requested. That is proportionate for a sanitization guideline.
Persistence & Privilege
The skill is not always-enabled and does not request persistent system privileges. Autonomous invocation is allowed by platform default but the skill itself does not request elevated presence or modify other skills' configs.
Assessment
This is a guidelines-only skill (no code, no credentials) that sensibly describes how to sanitize external content. Before relying on it: 1) confirm your agent runtime actually implements the referenced PostToolUse hook (sanitize_external_content.py) or otherwise enforces these rules, because the skill does not include that implementation; 2) note the file header version (1.8.2) differs from registry version (1.0.0) — confirm which version you'll follow; 3) test the sanitization rules against adversarial inputs (zero-width chars, hidden HTML/CSS, obfuscated instruction patterns) to ensure your environment's implementation is robust; and 4) remember these are guidelines — they reduce risk but do not guarantee safety on their own.Like a lobster shell, security has layers — review code before you run it.
latestvk97179rkhhj5am8kbazz4dzmg184sc2h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🦞 Clawdis