style-migrate-enhance

Migrate CSL 1.0 parent styles into Citum with oracle comparisons and fidelity metrics.

31|Updated Jan 28, 2026

Search Tags:#style migration #batch automation #citation rendering #fidelity testing #CSL 1.0 #YAML styles #oracle verification

Ready to run

npx skills add https://github.com/citum/citum-core --skill style-migrate-enhance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: style-migrate-enhance
Source: https://github.com/citum/citum-core/tree/main/.claude/skills/style-migrate-enhance
Command: npx skills add https://github.com/citum/citum-core --skill style-migrate-enhance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy CSL 1.0 styles often migrate imperfectly into Citum, causing rendering differences that break downstream workflows and erode trust in style results.

Core Features & Use Cases

High-throughput migration waves: Convert priority parent CSL 1.0 styles into Citum style YAML in repeatable batches while tracking evidence consistently.
Before/after/rerun metrics with hard fidelity gates: Re-run apples-to-apples oracle comparisons and only accept changes that do not reduce fidelity.
Engine-gap recommendations: When gaps are observed, produce a structured “code opportunities” table with targeted follow-ups for converter/preset improvements.

Quick Start

Run the style-migrate-enhance workflow to migrate a batch of legacy style paths into Citum styles while generating oracle-structured before/after metrics and gap recommendations.

Frequently Asked Questions about style-migrate-enhance

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

FAQPage Schema

How do I migrate CSL 1.0 styles to Citum YAML without losing rendering fidelity?▼

To migrate CSL 1.0 styles without losing rendering fidelity, run batch conversion waves that generate before/after/rerun metrics and enforce hard fidelity gates using oracle verification. This ensures only changes that do not reduce fidelity are accepted.

What is oracle verification for citation rendering style migration?▼

Oracle verification for citation rendering style migration is an apples-to-apples comparison mechanism that measures before/after rendering fidelity. It runs node scripts to ensure CSL 1.0 to Citum YAML conversions do not introduce rendering differences.

How do I automate batch conversion of legacy CSL 1.0 parent styles?▼

Automate batch conversion of legacy CSL 1.0 parent styles by executing migration waves with provided legacy and target style path inputs. The workflow tracks evidence consistently and generates wave-level summaries across multiple styles.

What happens when style migration introduces rendering differences in Citum?▼

When style migration introduces rendering differences in Citum, the workflow generates an engine-gap recommendations table. This structured code opportunities output provides targeted follow-ups for converter and preset improvements to resolve the gaps.

Do I need to provide legacy and target style paths for batch style migration?▼

Yes, you need to provide legacy and target style path inputs to execute batch style migration waves. These paths are required to run the shared workflow decision and evidence order docs and verify results via oracle.js node scripts.

Why does CSL 1.0 style migration break downstream citation workflows?▼

CSL 1.0 style migration breaks downstream citation workflows because legacy styles often migrate imperfectly into Citum. These rendering differences erode trust in style results and disrupt dependent processes without repeatable evidence and metrics.