← Back to Skills Marketplace
596
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install meta-skill
Description
Trajectory compiler that converts real OpenClaw session traces (or raw_trajectory_log) into a parameterized, reusable Skill via 4 stages: trace interception...
Usage Guidance
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).
Capability Analysis
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.
Capability Assessment
Purpose & Capability
The name/description (trajectory compiler → skill generator) matches the included scripts: they parse OpenClaw JSONL sessions/events, build a DAG, synthesize schema and code, and write a Skill folder. Reading session logs and writing into a skills directory is coherent with the stated purpose.
Instruction Scope
Runtime instructions and the scripts instruct the agent to read real OpenClaw session JSONL (~/.openclaw/agents/<agentId>/sessions) or arbitrary event inputs, normalize tool calls/results, synthesize code/schema, and write files into the Skills directory. Because session transcripts often contain tool outputs and possibly secrets, the pipeline will process and may embed those values (as defaults or constants) into generated files; the instructions give the agent broad discretion to pick sessions and write new skill files without explicit per-output confirmation.
Install Mechanism
No external install or remote downloads; this is instruction-plus-local-scripts only. All code is bundled in the skill package (no network install), so there is no third-party fetch risk in the install step.
Credentials
The skill declares no required environment variables or credentials, which is consistent. The scripts do read process.env.HOME (and optionally respect OPENCLAW_SKILLS_DIR in docs), and they will read/write files under the user's home (session and skills paths). That file-system access is necessary for the compiler but means sensitive session data can be captured into generated artifacts.
Persistence & Privilege
The compiler writes new Skill folders into the OpenClaw skills directory (default ~/.openclaw/workspace/skills/<skill-name>) and the README/instructions expect a hot reload. While 'always' is false, model invocation is allowed (normal), so an autonomously-invoked run could create or modify skill code on disk, enabling persistent, executable artifacts. Combined with the ability to embed scene defaults from traces, this increases blast radius if misused or invoked without human review.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install meta-skill - After installation, invoke the skill by name or use
/meta-skill - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release—introduces the meta-skill trajectory compiler.
- Converts OpenClaw session traces or raw logs into reusable, parameterized Skills.
- Implements a 4-stage pipeline: trace interception, DAG abstraction, schema & code synthesis, and registration.
- Outputs dynamic input Skills, schemas, synthesized code, and documentation.
- Includes scripts for each compilation stage and integration into the Skills directory.
Metadata
Frequently Asked Questions
What is Meta-Skill?
Trajectory compiler that converts real OpenClaw session traces (or raw_trajectory_log) into a parameterized, reusable Skill via 4 stages: trace interception... It is an AI Agent Skill for Claude Code / OpenClaw, with 596 downloads so far.
How do I install Meta-Skill?
Run "/install meta-skill" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Meta-Skill free?
Yes, Meta-Skill is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Meta-Skill support?
Meta-Skill is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Meta-Skill?
It is built and maintained by la1850 (@la1850); the current version is v1.0.0.
More Skills