!
Purpose & Capability
The skill is described as a prompt-only guided journal and requires no credentials or binaries, yet handler.py tries to read a local SKILL.md from a hard-coded absolute path (/Users/jianghaidong/.openclaw/skills/{skill_name}). Reading arbitrary local files is not necessary for a journaling prompt and is disproportionate to the stated purpose.
!
Instruction Scope
SKILL.md's runtime instructions are prompt-only and never mention reading the filesystem. The handler's runtime behavior (opening a SKILL.md from a specific home directory based on skill_name) goes beyond the documented instructions and could expose local file contents. The handler does no sanitization of skill_name, creating a risk of path-traversal reads.
✓
Install Mechanism
There is no install spec (instruction-only style) and no external downloads. The risk comes from the included local code file, not from any installer or network fetch.
!
Credentials
No environment variables or credentials are requested, which is correct for the stated purpose — but the code's hard-coded path to /Users/jianghaidong/... is unexpected and suggests either leftover developer-specific code or a potential privacy leak. The filesystem access is not justified by the skill's description.
✓
Persistence & Privilege
The skill is not marked always:true and does not request persistent platform-wide privileges. The handler does not modify agent configuration. The primary issue is local file reads rather than elevated persistence.
What to consider before installing
This skill appears to be a benign journaling prompt, but the included handler.py contains a hard-coded absolute path (/Users/jianghaidong/.openclaw/skills/{skill_name}) and will open files from the local filesystem based on the provided skill_name. That behavior is unnecessary for a journaling prompt and could be used to read sensitive local files (including via path-traversal if skill_name is attacker-controlled). Before installing or enabling this skill:
- Ask the maintainer why the handler reads a local SKILL.md and why the path is hard-coded to another user's home directory. This may be a leftover developer artifact.
- Request that the code be removed or modified so it does not access arbitrary filesystem locations (e.g., remove file reads, or restrict to packaged resources and sanitize input).
- If you must run it, run in an isolated/sandboxed environment where it cannot access sensitive files.
- Prefer the SKILL.md (prompt-only) behavior over executing the handler; if the platform allows, use the prompt-only implementation instead of executing included code.
Given the mismatch between declared behavior and actual file access, treat this skill as suspicious until the filesystem-read behavior is explained or removed.
