Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Canonical Data Map
v0.1.1Single source of truth for all paths, naming conventions, and data formats across the OpenClaw Greek Accounting system. Reference document.
⭐ 0· 612·0 current·0 all-time
byStems@satoshistackalotto
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (canonical data map) match the content: a directory layout, naming conventions, and a small bash snippet to initialize the tree. The single required env var (OPENCLAW_DATA_DIR) is appropriate for a filesystem map.
Instruction Scope
The SKILL.md is mainly a reference and contains a bash snippet to create the directories under $OPENCLAW_DATA_DIR. It also mandates that other skills write episodic memory, failure logs, and other state into /data/memory. That is coherent with being a canonical map, but it effectively centralizes agent memory/logging and could increase the impact of any skill that writes there — consider access controls and explicit limits on what other skills may write.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is downloaded or installed by the skill itself.
Credentials
Only OPENCLAW_DATA_DIR is declared as required. That is proportionate and justified by the skill's purpose. No credentials or unrelated env vars are requested.
Persistence & Privilege
The skill does not request always:true or modify other skills. However, it prescribes system-level directories (auth, backups, memory) that all skills may be expected to use. This increases the importance of file permissions, encryption of backups, and governance for which skills can write/read those trees.
Assessment
This is a documentation/reference skill and appears coherent with its stated purpose. Before installing: 1) Ensure OPENCLAW_DATA_DIR points to the intended (safe) location and that directory permissions restrict access to authorized processes only. 2) Review and enforce which skills are allowed to write into the centralized /memory, /auth, and /backups trees — centralizing logs and episodic memory increases blast radius if another skill is compromised. 3) If you run the provided mkdir snippet, check ownership, set restrictive umask/permissions, and consider encrypting backups and GDPR/export handling. 4) Confirm other skills that will read/write these directories are trusted and scoped appropriately.Like a lobster shell, security has layers — review code before you run it.
latestvk976tg140s59118tacartswsb981kw23
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
EnvOPENCLAW_DATA_DIR