ssot-check

Detect stale duplicated facts in markdown, HTML, and text files.

9|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/conorbronsdon/claude-code-skills --skill ssot-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ssot-check
Source: https://github.com/conorbronsdon/claude-code-skills/tree/main/ssot-check
Command: npx skills add https://github.com/conorbronsdon/claude-code-skills --skill ssot-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds documentation drift caused by the same fact being copied into multiple files and then updated inconsistently, so teams can preserve a single source of truth.

Core Features & Use Cases

  • Discover mode: Scans markdown, HTML, and text files for repeated facts and proposes a draft SSOT manifest.
  • Check mode: Verifies each copied value against its canonical source and reports drift, stale entries, or moved canonicals.
  • Cross-repo awareness: Supports sibling repository copies and fresh-pull validation when a live page or shared doc is the authoritative source.
  • Use case: Ideal for podcast, marketing, and documentation-heavy repositories where counts, prices, subscriber numbers, and other repeated facts often drift over time.

Quick Start

Ask the ssot-check skill to scan the repository for duplicated facts and report any drift against the manifest.

Frequently Asked Questions about ssot-check

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

FAQPage Schema
How do I detect documentation drift in markdown and HTML files?▼

Documentation drift is detected by scanning markdown, HTML, and text files for duplicated facts like prices or counts, then verifying copied values against a canonical source using regex patterns defined in a .ssot.yaml manifest.

What is a single source of truth manifest and when do I need one?▼

A single source of truth manifest is a .ssot.yaml file mapping canonical values to copy regex patterns. You need one to prevent stale facts when documentation-heavy repositories repeatedly copy the same numbers across multiple files.

How do I find and audit duplicated facts across multiple repositories?▼

Audit duplicated facts across multiple repositories by running discover mode to scan files and propose a draft manifest, then using cross-repo awareness to validate sibling repository copies against the canonical source for freshness.

Can I check markdown files for stale prices and subscriber counts without a manifest?▼

You cannot check for stale prices without a manifest, but discover mode scans markdown and text files to find repeated facts and automatically proposes a draft .ssot.yaml manifest with canonical and copy regex patterns.

What's the best way to validate cross-repo freshness for shared documentation?▼

Validate cross-repo freshness by configuring the .ssot.yaml manifest with optional cross-repo awareness to check sibling repository copies, ensuring shared documentation matches the authoritative live page or canonical source exactly.