ontology-evolution

Distills session lessons into tiered capability proposals for user approval.

3|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill ontology-evolution-wopal-cn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontology-evolution
Source: https://github.com/wopal-cn/wopal-space-ontology/tree/main/skills/ontology-evolution
Command: npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill ontology-evolution-wopal-cn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Runtime sessions produce a mix of reusable lessons and project-specific noise, and without a disciplined process the wrong knowledge leaks into shared capability pools or useful lessons are lost entirely. This Skill gives the Evolver agent a structured workflow to separate the two and propose durable improvements safely. ## Core Features & Use Cases - Friction Detection: Scans session events for repeated corrections, instructive errors, unclear instructions, wasted effort, and effective patterns worth preserving. - De-contextualization and Generalization Gate: Strips paths, project names, and session IDs, then applies three questions to decide whether a lesson holds beyond the current space. - Three-Tier Triage: Routes each candidate to space-private memory, type-specific assembly, or the public core pool, preventing contamination of shared assets. - Evolution Plan Output: Produces a structured Markdown proposal with evidence, tier justification, risks, and next steps, stopping before any implementation. - Use Case: After a session where the user corrected the same behavior twice, the Evolver loads this Skill, distills the underlying rule, classifies it as type-specific, and emits an Evolution Plan for the user to approve before Fae implements it. ## Quick Start Ask the Evolver agent to distill this session's lessons and corrections into an Evolution Plan for your review.

Frequently Asked Questions about ontology-evolution

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

FAQPage Schema
How do I turn session lessons into reusable agent capabilities?

Load this Skill in the Evolver agent and let it scan the session for friction signals like repeated corrections or instructive errors. It de-contextualizes each candidate, applies a generalization gate, and emits an Evolution Plan for your approval before any change is made.

How do I decide where a learned rule should be stored?

Use the three-tier triage: space-private lessons go to the space's memory or AGENTS.md, type-specific rules go to the type assembly config, and universally true principles go to the public core pool. When uncertain, place the lesson lower in the hierarchy.

Can the Evolver agent edit files or implement changes directly?

No. The Skill enforces a strict read-and-propose-only boundary: the Evolver never edits files, commits, or runs mutating commands. After user approval, Wopal orchestrates and Fae implements the change.

What is de-contextualization in capability distillation?

De-contextualization strips everything tying a lesson to one project: absolute paths, product names, business domain terms, session IDs, and timestamps. The test is whether a reader who has never seen the space could understand and apply the lesson.

When should a lesson not be promoted to the public core pool?

Do not promote a lesson when it only holds in the current space or only for one project type, or when the evidence is thin. A local lesson can be promoted later once proven general, but a polluted shared pool is hard to clean.