meta-optimize

Analyze ARIS usage logs to propose evidence-backed SKILL.md patch diffs.

Updated May 29, 2026
One-click install
npx skills add https://github.com/Mang30/myskills --skill meta-optimize-mang30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-optimize
Source: https://github.com/Mang30/myskills/tree/main/skills/meta-optimize
Command: npx skills add https://github.com/Mang30/myskills --skill meta-optimize-mang30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ARIS usage patterns and friction points remain invisible until users manually adjust skill prompts, defaults, and workflow behaviors, even though the system can learn from past runs.

Core Features & Use Cases

  • Log-driven harness improvement: Reads .aris/meta/events.jsonl and turns recurring behaviors, overrides, failures, and convergence signals into targeted improvement proposals.
  • Patch proposals for SKILL.md: Generates minimal diffs to adjust reviewer prompts, thresholds, retry behavior, workflow ordering, and safe defaults based on observed evidence.
  • Reviewer-gated change recommendations: Cross-model reviews patches adversarially and only recommends changes supported by sufficient data, with explicit uncertainty handling.
  • Optional apply with guardrails: Backs up SKILL.md, applies patches only after user approval, and logs the optimization event.

Quick Start

Run the meta-optimize skill after you have at least five logged workflow runs so it can analyze your ARIS event history and propose safe improvements.

Frequently Asked Questions about meta-optimize

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

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

You can optimize skill prompts by analyzing accumulated `.aris/meta/events.jsonl` usage logs to identify recurring overrides and failures, then proposing evidence-backed diff patches to adjust SKILL.md files and workflow defaults for improved convergence.

What is log-driven harness improvement for workflow defaults?

Log-driven harness improvement reads ARIS event history to transform recurring behaviors, convergence signals, and failures into targeted patch proposals for SKILL.md files, retry behavior, and reviewer thresholds.

How many logged workflow runs do I need before tuning ARIS skill defaults?

You need at least five logged workflow runs in your ARIS event history before tuning skill defaults, ensuring sufficient data exists to generate safe, evidence-backed improvement proposals for SKILL.md configurations.

Can I apply diff patches to SKILL.md files automatically with backup guardrails?

Yes, you can apply diff patches to SKILL.md files automatically after user approval, with the system backing up the original file first and logging the optimization event to ensure safe, reversible configuration changes.

Why does the reviewer loop fail to converge across multiple skill invocations?

Reviewer loops fail to converge when SKILL.md prompts and workflow defaults are misconfigured, which you can resolve by analyzing usage logs for convergence signals and applying cross-model adversarially reviewed patches to adjust thresholds and retry behavior.

What are the limitations of using usage logs for skill optimization?

Limitations include requiring at least five logged runs for sufficient data, as the system only recommends changes supported by adequate evidence and handles uncertainty explicitly through cross-model adversarial reviews before proposing any SKILL.md modifications.