curate-knowledge

Review and promote staged Tier-3 knowledge proposals into curated calibration knowledge stores.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jingtao-lbl/A2MC --skill curate-knowledge-jingtao-lbl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: curate-knowledge
Source: https://github.com/jingtao-lbl/A2MC/tree/main/.claude/skills/curate-knowledge
Command: npx skills add https://github.com/jingtao-lbl/A2MC --skill curate-knowledge-jingtao-lbl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The autonomous calibration agent stages its auto-learned proposals to a pending queue instead of writing them directly to the curated knowledge base, and without a human review step those proposals are silently dropped and the knowledge base stops learning from runs. ## Core Features & Use Cases - Queue Inspection: List open or all staged proposals in auto_discovered_pending.json via the review_pending_knowledge.py tool. - Evidence-Based Vetting: Cross-check each proposal's mechanism, experiment results, and do_not_repeat rules against run data, RAG sources, and existing curated entries before deciding. - Promote or Discard: Promote vetted entries into discoveries.json, failed_approaches.json, or experiments.json with optional confidence overrides, and discard phantoms, duplicates, or overbroad rules. - Use Case: After several autonomous calibration rounds, run the curation pass to review what the agent proposed to learn, promote the verified discoveries, and discard misunderstandings so the curated knowledge base stays accurate. ## Quick Start Ask the agent to review the pending knowledge proposals and promote the ones verified against experiment evidence.

Frequently Asked Questions about curate-knowledge

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

FAQPage Schema
How do I review pending knowledge proposals from autonomous calibration runs?▼

Run review_pending_knowledge.py list to see open proposals staged in auto_discovered_pending.json, then evaluate each against its experiment evidence before promoting or discarding. Use list --all to include already-processed entries.

How do I promote staged auto-learn proposals to the curated knowledge base?▼

Use review_pending_knowledge.py promote --key <name> after verifying the result is real, reproduced, and not a duplicate. You can override confidence with --confidence, but never run promote --all without reviewing every item first.

Why are auto-learned entries not written directly to the curated knowledge base?▼

The autonomous agent runs in propose mode so unverified lessons cannot contaminate curated knowledge. A past incident produced 70 false entries including do_not_repeat rules that forbade the agent's own best fixes, so all proposals now require human vetting.

When should I discard a staged knowledge proposal instead of promoting it?▼

Discard proposals with phantom or missing data, unsupported mechanisms, duplicates of existing curated entries, or overbroad do_not_repeat rules. For partially correct proposals, discard and hand-author a corrected curated entry instead.

What happens if nobody runs the knowledge curation step?▼

The write gate becomes a silent drop: staged proposals never reach the curated stores and the knowledge base stops learning from runs. One case reached thirty experiment cycles with an empty knowledge store for this reason.