Skip to content

Skills Lifecycle (audit, promote, archive)

Over time a project accumulates skills, both hand-written ones and drafts the engine crystallizes from repeated work. Three flags let you keep that library clean: audit it for problems, promote a draft to active, or archive one you do not want.

--skills-audit scans the current project’s skills and reports problems. It writes a machine-readable JSON report to .wayland-core/skills-audit.json and prints a Markdown summary to stdout:

Terminal window
wayland-core --skills-audit

The audit reports three kinds of finding:

FindingMeaning
staleLast modified beyond the staleness threshold (default 180 days).
duplicateDescription close to another skill’s by edit distance.
broken_refA declared artifact path that will not resolve safely.

Change the staleness threshold with --skills-audit-stale-days:

Terminal window
wayland-core --skills-audit --skills-audit-stale-days 90

That flag is only valid alongside --skills-audit.

The engine can draft skills from recurring patterns. A drafted skill starts in a Staged state. Promote it to Active by its procedure ID:

Terminal window
wayland-core --skills-promote <PROCEDURE_ID>

The procedure ID is the UUID emitted in skill_drafted trace events. Promotion reads and writes the project’s .wayland-core/memory/memory.db.

Archive a skill you do not want to keep. Both Staged and Active rows can be archived directly:

Terminal window
wayland-core --skills-archive <PROCEDURE_ID>

Pinned skills cannot be archived from the CLI. Promote or unpin them through the curator first.

These flags are the manual controls on the draft, curate, and evolve pipeline. The engine drafts candidate skills into the Staged state during normal work; you decide which earn promotion to Active and which get archived. The audit report uses the same shape the automatic curator reads, so a CLI audit and the curator agree on what is stale or duplicated.