meta-curator

Generate SKILL.md drafts from pipeline lessons and merged pull-request patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/CleanExpo/Pi-Dev-Ops --skill meta-curator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-curator
Source: https://github.com/CleanExpo/Pi-Dev-Ops/tree/main/skills/meta-curator
Command: npx skills add https://github.com/CleanExpo/Pi-Dev-Ops --skill meta-curator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires anthropic-skills:skill-creator, telegram-draft-for-review.

What problem does it solve?

Meta-curator turns the Pi-CEO engineering system’s accumulated lessons and merged-PR patterns into reusable skill drafts so the skill registry compounds over time instead of staying manually authored.

Core Features & Use Cases

  • Evidence-driven skill proposals: Reads .harness/lessons.jsonl (weekly) and merged-PR diffs (daily) to generate candidate SKILL.md drafts grounded in observed workflows.
  • Cluster-based deduplication: Groups evidence into topic/file/pattern clusters and prevents duplicates by matching against existing skills, optionally proposing amendments instead of new skills.
  • HITL review with consent-gating: Routes each proposed SKILL.md through a review chat flow and writes to Pi-Dev-Ops/skills/<proposed-name>/SKILL.md only after the user approves with 👍.
  • Auditability and loop guards: Persists proposal records, archives rejected/expired clusters, rate-limits proposal frequency, and avoids re-proposing the same rejected evidence within a cooldown window.

Quick Start

Ask an AI agent to run the curator now (via the /curator:run-now command) and then review the proposed SKILL.md drafts surfaced for your approval.

Frequently Asked Questions about meta-curator

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

FAQPage Schema
How do I automatically generate GitHub skills from merged pull-request patterns?

Automatically generating GitHub skills from merged pull-request patterns involves clustering daily PR diffs and weekly pipeline lessons into candidate SKILL.md drafts. The system converts recurring engineering workflows into proposed skill registry entries grounded in observed evidence.

What is evidence clustering for automated skill discovery workflows?

Evidence clustering for automated skill discovery groups recurring pipeline lessons and merged-PR patterns into topic or file-based clusters. This mechanism prevents duplicate skill proposals by matching new clusters against existing skills before generating drafts.

How does HITL approval gating work for proposed SKILL.md drafts?

HITL approval gating routes each proposed SKILL.md through a review chat flow where the user must explicitly approve with a 👍 reaction. The draft is only written to the skill registry after this human-in-the-loop consent is verified.

Can I prevent duplicate skill proposals from recurring pipeline lessons?

Preventing duplicate skill proposals from recurring pipeline lessons is handled through cluster-based deduplication. The system matches evidence clusters against the existing skill registry, optionally proposing amendments to current skills instead of creating duplicates.

Do I need audit trails and rate limiting for automated skill authoring pipelines?

Audit trails and rate limiting are required for automated skill authoring to maintain operational safety. The system persists proposal records to curator JSONL logs, archives rejected clusters, and enforces cooldown windows to prevent re-proposing rejected evidence.

Why does my automated skill proposal keep getting rejected in the review loop?

Automated skill proposals get rejected in the review loop when evidence clusters fail HITL approval gating or match existing skills. Rejected or expired clusters are archived with loop guards to prevent re-proposal within the configured cooldown window.