Meta-Skill

Trajectory compiler that converts real OpenClaw session traces (or raw_trajectory_log) into a parameterized, reusable Skill via 4 stages: trace interception...

This skill is functionally coherent but carries real risks you should consider before running it on real session data. Key recommendations: - Review the included scripts (they are provided in full) and the generated outputs before performing a hot-reload. - Do not point the compiler at session logs that contain secrets or sensitive outputs. Instead, operate on sanitized copies of session JSONL. - Prefer using the --out option to write generated skills to a safe sandbox directory first; inspect the generated SKILL.md, schema.json, run script, and any default values before placing them in your real skills directory. - Be aware generated schemas may include defaults copied from trace values (which can leak API keys or tokens present in traces); remove such defaults if found. - If you are uncomfortable with an agent autonomously running this compiler and writing skill files, restrict invocation (run it manually) or run it in an isolated environment/container. - If you plan to use it, run static/code review of produced scripts and consider running them with least privilege and on sanitized data. If you want, I can (1) point out exact lines where files are read/written and where defaults are set so you can audit them, or (2) suggest a safe invocation sequence that minimizes exposure (e.g., using --out to a temporary dir and manual inspection).

Type: OpenClaw Skill Name: meta-skill Version: 1.0.0 The bundle implements a 'meta-skill' compiler that allows an agent to generate new skills from its own execution history. It is classified as suspicious because it requires high-privilege access to read sensitive session logs from `~/.openclaw/agents/` (via `scripts/trace-from-session.js`) and has the capability to write new executable code and instructions into the system's skills directory (via `scripts/trajectory-compiler.js`). While these functions are consistent with the stated purpose of a trajectory compiler, the ability to self-modify and access historical transcripts represents a significant security risk if the input traces are manipulated.