Consolidates scattered facts into a single canonical home and replaces duplicates with references.
Install
mkdir -p .claude/skills/ssotize && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16858" && unzip -o skill.zip -d .claude/skills/ssotize && rm skill.zipInstalls to .claude/skills/ssotize
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Consolidate a fact that's scattered across places into one canonical source and replace the rest with references — mutating. Use when the user asks to deduplicate, consolidate, unify, or establish a single source of truth across artifacts or platforms; or when the same fact lives in many places and copies are drifting. Folds unique details into the canonical home and reconciles contradictions before removing any copy.Key capabilities
- →Audit for scattered facts using `ssotchk` workflow
- →Extract or make a canonical home complete and current
- →Reconcile contradictions in the canonical home
- →Replace duplicate facts with live references to the canonical home
- →Remove now-redundant copies, leaving pointers if necessary
- →Mutate artifacts with edit-safety and platform awareness
How it works
This skill identifies scattered facts, consolidates them into a single canonical source, reconciles contradictions, and replaces all other instances with references, ensuring data integrity.
Inputs & outputs
When to use ssotize
- →Consolidating documentation
- →Deduplicating code configuration
- →Establishing a single source of truth
- →Repairing drifting information
About this skill
Collapse a scattered truth into one canonical home; make every other place point to it.
Goal
Enforce Single Source of Truth (SSOT): one fact = one home, and every other place that needs it references that home instead of copying it. References don't drift; copies do. This mutates artifacts, so it is deliberate and loss-averse.
Use this to establish or repair SSOT — messy, legacy, or freshly-scaffolded states. Once SSOT holds, don't overuse it: consolidation is a one-time repair, not ongoing upkeep.
Workflow
- Audit first — run the
ssotchkworkflow (or reuse its result) for the canonical home and the per-occurrence action plan. Don't consolidate blind. - Make or extract the canonical home complete and current — fold in any unique detail that lived only in a copy. When no existing copy is canonical, extract a new canonical home instead of promoting a weak copy. Never lose information to consolidation.
- Reconcile contradictions in the canonical home FIRST (confirm the correct value with the human when ambiguous); only then point others at it.
- Replace each duplicate with a live reference to the canonical home — for docs, use a link, a "see <home>", a quote-with-link, or a transclude where the platform supports it; for code, use an import/source/include of the shared home; for config, use a shared read from the one maintained file.
- Remove the now-redundant copies. Where removal would orphan a reader, leave a one-line pointer instead of deleting outright.
Rules
- A pass that finds no scatter to consolidate changes nothing.
- Don't consolidate across a trust/permission boundary (private → public, customer-facing → internal) without explicit confirmation.
- Mutate with edit-safety: assert each replace target exists before touching it (report a MISS, never a silent no-op), edit unicode-safe (
PYTHONUTF8=1), and act per occurrence, never a blanket sweep; make structural code moves with language-aware tools or scripted AST/parser edits, never scripted text rewrites. - Be platform-aware: transclude where possible, else link to a stable anchor the reader can follow; prefer a reference over a hard deletion when a platform can't link back.
Verification
Before finishing:
- The canonical home holds the complete, current truth on its own.
- Every former copy now references it, and each reference resolves.
- No unique detail was lost and nothing was orphaned.
- Contradictions were reconciled to one value, not left duplicated.
- Report what was consolidated, where the canonical home is, and what (if anything) still needs a human decision.
When not to use it
- →When the user does not ask to deduplicate, consolidate, unify, or establish a single source of truth
- →When the same fact does not live in many places with drifting copies
- →When consolidating across a trust/permission boundary without explicit confirmation
Limitations
- →Does not consolidate across a trust/permission boundary without explicit confirmation
- →Requires edit-safety measures like asserting target existence and unicode-safe editing
- →Acts per occurrence, not a blanket sweep
How it compares
This workflow systematically enforces a Single Source of Truth by mutating artifacts to replace copies with live references, preventing data drift, unlike manual content synchronization.
Compared to similar skills
ssotize side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ssotize (this skill) | 0 | 1mo | No flags | Advanced |
| antfu | 6 | 3mo | Review | Intermediate |
| agent-implementer-sparc-coder | 1 | 6mo | Review | Intermediate |
| backfill-feature | 0 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by LowyShin
View all by LowyShin →You might also like
antfu
antfu
Anthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.
agent-implementer-sparc-coder
ruvnet
Agent skill for implementer-sparc-coder - invoke with $agent-implementer-sparc-coder
backfill-feature
0xdeafcafe
Use when the user says "/backfill-feature", "backfill the ADR", "this feature has no ADR", "I need to document what's already there before I change it", or wants to capture an existing feature's architectural rationale and behaviour *before* modifying it. Reads the relevant code, drafts a reverse-en
tech-debt
agentty-xyz
Sweep the codebase for tech debt and return a prioritized markdown task list of findings.
docx
anthropics
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
notion-knowledge-capture
makenotion
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.