light-consistency

Audit project materials against a central glossary for terminology and metric consistency.

514|67|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/Light0305/Light-skills --skill light-consistency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: light-consistency
Source: https://github.com/Light0305/Light-skills/tree/main/skills/light-consistency
Command: npx skills add https://github.com/Light0305/Light-skills --skill light-consistency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

Unified style and consistency maintenance across manuscripts, PPTs, charts, code, and project docs; prevents drift in terminology, metrics, and phrasing by enforcing a single source of truth and background checks.

Core Features & Use Cases

  • Background, continuous consistency checks across all materials to ensure standard terminology, symbols, and design language are used.
  • Automated audit of cross-material coherence including terminology substitutions, metric name/value alignment, and coverage gaps using a central glossary (SSOT).
  • Use Case: a research team runs scans over papers, slides, and reports to ensure the same innovation points and metrics are described identically in every artifact.

Quick Start

Run the consistency_audit.py script against your project materials to detect terminology substitutions, metric mismatches, and coverage gaps and then apply the recommended fixes.

Frequently Asked Questions about light-consistency

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

FAQPage Schema
How do I maintain consistent terminology across research manuscripts and presentation slides?

To maintain consistent terminology across research manuscripts and slides, you can use this Skill to enforce a central glossary and run automated audits for terminology substitutions and metric mismatches across all project artifacts.

How do I audit research materials for terminology drift and coverage gaps?

You audit research materials for terminology drift by running the consistency audit script against your project files, which detects coverage gaps, metric value mismatches, and contribution drift using a central single source of truth glossary.

Can I check cross-material coherence for academic writing workflows and software documentation?

Yes, you can check cross-material coherence for academic writing workflows and software documentation, as the Skill targets manuscripts, slides, code, and reports to ensure standard terminology and design language are used identically.

Do I need a central glossary to unify visual design tokens and messaging across project artifacts?

Yes, you need a central glossary to unify visual design tokens and messaging across project artifacts, because the Skill uses this single source of truth to validate terminology substitutions, metric names, and harmonize outputs.

What is the best way to prevent style and phrasing drift across research papers and PPTs?

The best way to prevent style and phrasing drift across research papers and PPTs is to run continuous background consistency checks that validate definitions and enforce unified messaging against a single source of truth glossary.

What are the limitations of using automated scripts for terminology consistency in research reports?

A limitation of using automated scripts for terminology consistency in research reports is that the audit relies entirely on predefined glossary entries, meaning unmapped innovation points or undefined terms may still require manual review.