T09 · Insecure Skill Coding Practices
- Location
scripts/trajectory-compiler.js:405- Finding
Output Path Traversal Allows Writes Outside the Skills Directory
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill has a coherent trace-to-skill purpose, but it needs Review because untrusted trace content can control generated skill files and persistent skill instructions.
Install only if you are comfortable reviewing generated files before refresh. Use sanitized non-production traces, avoid --latest on sessions that may contain secrets, pass an explicit safe --name and --out directory, and do not load generated skills until their SKILL.md, plan, schema, and run script have been inspected.
scripts/trajectory-compiler.js:405Output Path Traversal Allows Writes Outside the Skills Directory
scripts/trajectory-compiler.js:278Unescaped Trace Metadata Enables Persistent Skill Instruction Injection
scripts/trace-from-session.js:128Session Trace Export Copies Sensitive Tool Data Without Redaction or Restrictive Permissions
Referenced artifact was not completely inspected
Use `scripts/trace-from-session.js` to generate a **real trace** from OpenClaw session JSONL, or `scripts/trace-interceptor.js` for JSONL tool event streams.
Referenced artifact was not completely inspected
Use `scripts/trace-from-session.js` to generate a **real trace** from OpenClaw session JSONL, or `scripts/trace-interceptor.js` for JSONL tool event streams.
Referenced artifact was not completely inspected
Use `scripts/trajectory-compiler.js` to build a DAG and lift variables to inputs.
The skill describes compiler behavior that synthesizes code and writes artifacts, yet the manifest shown does not declare any explicit tool scope or permissions boundary. In a skill that processes session traces and emits runnable code, missing scope declarations increases the chance of unintended environment access or overbroad execution when the skill is invoked.
The skill explicitly states that the compiler writes into the Skills directory and requires refresh, but it does not present a clear user-facing warning that local files will be created or modified. Because this is a self-replicating or self-installing workflow into a trusted skills location, an unsuspecting user could persist generated code or overwrite existing content without informed consent.
The documentation explicitly instructs users to extract real OpenClaw session transcripts, actual tool calls, and tool results, but provides no warning that those traces may contain sensitive prompts, secrets, personal data, or credentials. In a trajectory-compilation skill, this is especially risky because the data is not only viewed but converted into reusable artifacts, increasing the chance of persistent disclosure or unintended propagation.
The documentation says compiler output is written directly into the OpenClaw skills directory, including a default path under the user's workspace, without warning that existing skills may be overwritten or modified. In this skill's context, generating code and registering it for hot reload raises the risk of accidental replacement of trusted skills or persistence of unsafe generated artifacts.
No suspicious patterns detected.