Workflow Crystallizer
v1.0.0Analyze memory logs to detect recurring patterns and suggest automations — cron jobs, skills, or workflow shortcuts. The agent builds its own shortcuts over...
⭐ 0· 43·0 current·0 all-time
byNew Age Investments@newageinvestments25-byte·duplicate of @newageinvestments25-byte/nai-workflow-crystallizer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (detect recurring patterns in memory logs and propose automations) match the implemented behavior: the scripts parse memory/YYYY-MM-DD.md files, cluster events, generate suggestions (cron definitions, skill drafts, saved prompts), and check existing crons and skills to avoid duplicates. File reads and state persistence are expected for this purpose.
Instruction Scope
Runtime instructions and scripts operate on local files (memory files, a state.json next to the skill, ~/.openclaw/cron/jobs.json, and system skill directories). This is consistent with the goal, but the skill will read potentially sensitive 'memory' logs and include extracted snippets in evidence, draft SKILL.md files, and ready-to-approve cron payloads — so outputs may contain sensitive user data. The SKILL.md uses absolute example paths specific to a user; otherwise instructions are concrete and bounded (no vague 'gather any context' clauses).
Install Mechanism
There is no install specification and the package ships only Python scripts and reference files. No network fetches, installers, or archive extraction are used. This is low-risk from install-mechanism perspective.
Credentials
The skill requests no environment variables or credentials. It does enumerate and read local files and directories (memory files, cron jobs JSON, skill directories) which is necessary to de-duplicate suggestions and build evidence. No unrelated secrets or external-service tokens are requested.
Persistence & Privilege
always:false (not force-included) and default model invocation allowed. The skill persists its own state (state.json) in the skill workspace; that is coherent for its purpose. Because the skill is intended to be scheduled (the README suggests weekly cron), be aware autonomous invocation combined with access to local memory files increases privacy sensitivity — but there is no code that autonomously registers system cron jobs or modifies other skills/configs.
Assessment
This skill appears to do what it says: it scans your local memory files, clusters repeated events, and drafts actionable suggestions (cron JSON, skill SKILL.md drafts, saved prompts). Before enabling or scheduling it consider: 1) privacy — memory files often contain sensitive data and the skill includes snippets of those files in its suggestions/evidence; review outputs before approving or creating crons/skills; 2) scope of file access — it reads ~/.openclaw/cron/jobs.json and your skills directories to avoid duplicates; if you prefer isolation, run it in a sandbox or point it to a copy of your memory dir; 3) it does not auto-create cron jobs or push skills, it only writes a local state.json and prints ready-to-approve definitions — you must run openclaw cron create or otherwise apply changes manually; 4) inspect state.json and the generated reports for any sensitive content before sharing. If you want stronger guarantees, run the scripts with a restricted copy of your memory files or increase min_confidence / reduce max_suggestions_per_run in the config.Like a lobster shell, security has layers — review code before you run it.
latestvk97avy9yhhyescr6jc0bkqd7vs83xdb4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.