meta-optimize

Analyze ARIS usage logs and propose evidence-backed SKILL.md patches.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Shallow-W/llm-wiki --skill meta-optimize-shallow-w
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-optimize
Source: https://github.com/Shallow-W/llm-wiki/tree/main/.claude/skills/meta-optimize
Command: npx skills add https://github.com/Shallow-W/llm-wiki --skill meta-optimize-shallow-w

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ARIS harness performance and user experience degrade over time when defaults, review prompts, and workflow parameters stop matching how people actually use the system.

Core Features & Use Cases

  • Log-driven harness optimization: Analyzes .aris/meta/events.jsonl to identify which skills, parameters, and prompts correlate with overrides and failures.
  • Evidence-backed patch proposals: Produces minimal diffs to relevant SKILL.md files and workflow defaults, with explicit log evidence and cross-model review gating.
  • Safe, user-approved application: Never auto-applies; backs up changes, records an optimization trail in .aris/meta/optimizations.jsonl, and prompts the user to test.

Quick Start

Run the meta-optimize skill after at least 5 logged workflow runs by using the command "/meta-optimize" to generate recommended SKILL.md and prompt optimizations.

Frequently Asked Questions about meta-optimize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize skill prompts using accumulated usage logs?

To optimize skill prompts, you analyze usage logs to identify failure patterns and generate evidence-backed patches for SKILL.md files. This process requires reading event logs and proposing minimal diffs with frequency and convergence analysis.

What is log-driven prompt tuning for workflow defaults?

Log-driven prompt tuning is the process of analyzing recorded workflow events to identify parameter overrides and failures, then proposing minimal patches to workflow defaults and review prompts to improve system performance.

How many logged workflow runs do I need before I can analyze usage records for skill optimization?

You need at least 5 logged workflow runs before analyzing usage records for skill optimization. The system requires sufficient data in the events log to perform meaningful frequency, failure, and human-intervention analysis.

Does the skill optimization process automatically apply patches to SKILL.md files?

No, skill optimization never auto-applies patches. It backs up changes, runs a cross-model reviewer loop, records an optimization trail, and requires explicit user approval before applying any proposed diffs to SKILL.md files.

What's the best way to identify which workflow parameters correlate with failures in usage logs?

The best way to identify failing parameters is performing frequency and convergence analysis on event logs, specifically looking for correlations between workflow defaults, overrides, and human interventions recorded during execution.

Why do workflow defaults stop matching actual usage over time?

Workflow defaults stop matching actual usage because review prompts and parameters degrade when user behavior evolves. Analyzing event logs for override patterns and generating minimal evidence-backed patches realigns the system with current usage.