meta-optimize

Orchestrate end-to-end meta-improvement cycles with PR-based promotions across repositories.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/firefly-events/plugin-hive --skill meta-optimize-firefly-events
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-optimize
Source: https://github.com/firefly-events/plugin-hive/tree/main/skills/hive/skills/meta-optimize
Command: npx skills add https://github.com/firefly-events/plugin-hive --skill meta-optimize-firefly-events

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when a consumer wants to run the public meta-improvement cycle against their target project. This skill is the shipped orchestration surface: it resolves HIVE_TARGET_PROJECT, honors kickoff metrics opt-in, follows the shared meta-team workflow, and promotes retained changes as PR-shaped artifacts against the consumer repo.

Core Features & Use Cases

  • Public-cycle orchestration: coordinates the entire meta-team lifecycle from boot to close using the shared workflow.
  • Target-project governance: resolves the consumer repo target, enforces clean state, and respects metrics opt-in.
  • PR-based promotion: uses PrPromotionAdapter to create PR-shaped artifacts instead of direct commits on the consumer repo.
  • Backlog and metrics-based selection: selects ranked proposals when metrics are enabled, otherwise falls back to backlog entries.
  • Safeguards and validation: uses closure_validator.validate_closable and shared handoffs to baseline/candidate comparison.

Quick Start

Configure HIVE_TARGET_PROJECT and kickoff metrics, then trigger the public meta-optimize cycle against your target project.

Frequently Asked Questions about meta-optimize

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

FAQPage Schema
How do I automate pull request promotions for repository improvements?

Pull request promotion is automated by orchestrating end-to-end meta-improvement cycles that coordinate gated steps and produce PR-shaped artifacts against the target consumer repository.

What is a meta-improvement workflow for target projects?

A meta-improvement workflow coordinates the entire lifecycle from boot to close, covering analysis, proposal, implementation, testing, evaluation, promotion, and close phases using shared runtime handoffs.

Do I need a clean git state to run workflow optimization cycles?

Yes, a clean target git state is required to run workflow optimization cycles, ensuring that baseline and candidate comparisons during the evaluation phase produce valid closure evidence.

How does backlog selection work when metrics opt-in is disabled?

When metrics opt-in is disabled, backlog selection falls back to using backlog entries instead of ranked proposals to drive decisions across the gated implementation phases.

Can I use this to coordinate testing and evaluation phases across consumer repositories?

Yes, you can coordinate testing and evaluation phases across consumer repositories by using shared handoffs that validate candidate comparisons against baselines before promotion.

What safeguards exist for closing meta-improvement cycles?

Closure safeguards use closure validation to verify closable conditions and compare baseline against candidate states, ensuring only retained changes produce PR-shaped close evidence.