Preview. Some tools run on sample data and say so. Nothing here is legal advice.

SHARED SKILLS / REVIEW BEFORE MIGRATION

Give every skill a clear meaning.

Inspect duplicate labels, contextual ambiguity and proposed mappings without changing existing course, job or profile references.

Reconcile terminology before changing the shared registry.

Paste a small batch of skill labels or CSV. Matching and proposals stay on this device. This is a review tool, not an automatic ontology import; the private legacy attachment is not loaded into this page.

At most 200 rows / 50,000 characters. CSV headers: label (or Tag), kind, context, Class. Legacy Class is retained but never assumed to be a canonical type. Quoted CSV fields are supported.

No local batch analyzed

The shared registry remains unchanged. Start with a small sample and inspect collisions before planning a migration.

What a draft does—and does not—mean

Exact candidates are proposals, not verified synonym claims. A scoped alias must not collide with another concept in that scope. Related concepts remain separate. New concepts receive provisional candidate IDs; a reviewed migration must assign stable IDs and preserve old references through merge/split redirects.

Return to the canonical proposals →