New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ssotize

by LilMGenius in LilMGenius/paperthin

Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references.

MITAuto-check passedDevelopment

Install Ssotize

skills CLI
$ npx skills add LilMGenius/paperthin --skill ssotize -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LilMGenius/paperthin ssotize --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LilMGenius/paperthin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/breadth/ssotize .claude/skills/ssotize && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ssotize
GitHub stars
1.1k
Token cost
~1.3k tokens
SKILL.md length
760 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references.

  • Works in 12 steps: Name the truth in scope — the specific… → Audit read-only first: enumerate every… → Re-enumerate by a second method — a… → …
  • Asked to find duplication
  • SKILL.md covers Goal, Workflow, Rules and Verification
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ssotize is an agent skill from LilMGenius/paperthin. Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts read-only, reports the map and plan, then mutates only after explicit approval.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Low-level agentic design patterns. Turning old engineering wisdom into reflexes your agent reaches for on its own—on any agent. The licence is MIT.

When your agent uses it

  • Asked to find duplication
  • Check consistency
  • Locate the source of truth
  • Establish SSOT across artifacts

Example prompts

  • “/ssotize”

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

  1. Name the truth in scope — the specific fact, value, spec, decision, status, or definition being tracked, not the whole document.
  2. Audit read-only first: enumerate every occurrence across the given artifacts and platforms.
  3. Re-enumerate by a second method — a different search term, synonym, or tool — and confirm it surfaces no occurrence the first pass missed.
  4. Classify each occurrence: exact copy, paraphrase, partial, stale, or contradictory.
  5. Pick the canonical home — the most authoritative and most-maintained location, closest to where the fact actually changes. Never promote a…
  6. Decide the action per non-canonical occurrence: dedupe (redundant copy), reference (docs should link to canonical, code should…
  7. Report the audit before editing: a table of occurrences (location · kind · action), the proposed canonical home with a one-line…
  8. Ask for explicit approval to execute the mutation plan. If approval is not given, stop after the read-only report.
  9. Make or extract the canonical home complete and current — fold in any unique detail that lived only in a copy. Never lose information to…
  10. Reconcile contradictions in the canonical home first; when the correct value is ambiguous, confirm it before replacing anything.
  11. Replace each duplicate with a live reference to the canonical home — for docs, use a link, a "see ", a quote-with-link, or a transclude…
  12. Remove the now-redundant copies. Where removal would orphan a reader, leave a one-line pointer instead of deleting outright.

What it can do on your machine

Read from SKILL.md and the folder at commit 7d5dc62. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ssotize loads about 1.3k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 760 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~100
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LilMGenius/paperthin at commit 7d5dc62, republished under its MIT licence (© LilMGenius). 760 words, ~1,343 tokens.

Download SKILL.mdSave it as .claude/skills/ssotize/SKILL.md (or your agent's skills folder).
name
ssotize
description
Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts read-only, reports the map and plan, then mutates only after explicit approval.

Find where one truth lives, get approval for the consolidation plan, then collapse it into one canonical home.

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.

ssotize starts as a read-only audit. It names the truth in scope, finds every copy, chooses the canonical home, and reports the exact consolidation plan. Only after the user approves that plan does it mutate artifacts.

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. When a read-only checker and a mutating follow-up have become one inseparable workflow, fold the checker into the consolidator and keep the approval gate; splitting the reflex only makes the safer first half easier to skip.

Workflow

  1. Name the truth in scope — the specific fact, value, spec, decision, status, or definition being tracked, not the whole document.
  2. Audit read-only first: enumerate every occurrence across the given artifacts and platforms.
  3. Re-enumerate by a second method — a different search term, synonym, or tool — and confirm it surfaces no occurrence the first pass missed.
  4. Classify each occurrence: exact copy, paraphrase, partial, stale, or contradictory.
  5. Pick the canonical home — the most authoritative and most-maintained location, closest to where the fact actually changes. Never promote a weak copy just because it is convenient; extract a new canonical home if none exists.
  6. Decide the action per non-canonical occurrence: dedupe (redundant copy), reference (docs should link to canonical, code should import/source/include it, config should use a shared read), or reconcile (it disagrees and needs a human call).
  7. Report the audit before editing: a table of occurrences (location · kind · action), the proposed canonical home with a one-line justification, unique details that must be folded into it, contradictions that need a decision, and the exact mutation plan.
  8. Ask for explicit approval to execute the mutation plan. If approval is not given, stop after the read-only report.
  9. Make or extract the canonical home complete and current — fold in any unique detail that lived only in a copy. Never lose information to consolidation.
  10. Reconcile contradictions in the canonical home first; when the correct value is ambiguous, confirm it before replacing anything.
  11. 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.
  12. Remove the now-redundant copies. Where removal would orphan a reader, leave a one-line pointer instead of deleting outright.
Show full SKILL.md (292 more words)Show less

Rules

  • A pass that finds no scatter to consolidate changes nothing.
  • The audit phase is read-only. Do not edit, move, or delete before the user approves the mutation plan.
  • An empty findings list is a valid result — never invent drift to justify a consolidation.
  • Keep contradictions separate from plain duplicates; never silently decide which conflicting value is "true".
  • Flag any detail that lives only in a non-canonical copy — it must be folded into the canonical home before that copy can be cut.
  • 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.
  • When the same project fact is split between a read-only audit artifact and a mutating artifact, and the audit has no independent durable use, treat that as SSOT scatter: propose folding the audit into the mutating artifact, then execute only after approval.

Verification

Before finishing:

  1. The audit was reported before mutation and approval was received, unless the run stayed read-only.
  2. The canonical home holds the complete, current truth on its own.
  3. Every former copy now references it, and each reference resolves.
  4. No unique detail was lost and nothing was orphaned.
  5. Contradictions were reconciled to one value, not left duplicated.
  6. Report what was consolidated, where the canonical home is, what was only audited, and what still needs a human decision.

© LilMGenius, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/breadth/ssotize of LilMGenius/paperthin.

Open the folder on GitHubat commit 7d5dc62

Compare with similar skills

Ssotize next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ssotize compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ssotize this skillLilMGenius/paperthin1.1k—~1.3kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from LilMGenius/paperthin

All 28 skills in this repo

  • Modelchk

    LilMGenius/paperthin

    Size a task's run before spending it: the cheapest sufficient capability tier (fast, standard, frontier) and the reasoning effort within it, on a neutral scale that binds to whatever levels the…

    1.1k GitHub stars~1.6k tokensUpdated 7 days ago
    Auto-check passed

  • Re0 Loop

    LilMGenius/paperthin

    Run repeated build - QA - re0-memo - re0-work cycles while preserving learning and letting code die.

    1.1k GitHub stars~579 tokensUpdated 7 days ago
    Auto-check passed

  • Autobahn

    LilMGenius/paperthin

    Carve guardrail-adjacent items out of scope with safe alternatives before risk-adjacent work starts, then run the safe remainder at full strength in a fresh subagent that only ever sees the carved…

    1.1k GitHub stars~2.1k tokensUpdated 7 days ago
    Auto-check passed

  • Catchup

    LilMGenius/paperthin

    Rebuild the human's lost context on a project from live state, in plain language: what needs them, what changed, what new words mean.

    1.1k GitHub stars~785 tokensUpdated 7 days ago
    Auto-check passed

  • Debloat

    LilMGenius/paperthin

    Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved.

    1.1k GitHub stars~813 tokensUpdated 7 days ago
    Auto-check passed

  • Factchk

    LilMGenius/paperthin

    Verify reality-grounded claims against external sources in both directions before they ship — could the 'absurd' be real, could the 'obvious' be false or long-established?

    1.1k GitHub stars~717 tokensUpdated 7 days ago
    Auto-check passed

Categories

Questions about Ssotize

What does Ssotize do?

Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Ssotize is an agent skill from LilMGenius/paperthin. Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references.

When should I use Ssotize?

Ssotize fits situations like: asked to find duplication; check consistency; locate the source of truth; establish SSOT across artifacts.

How do I install Ssotize in Claude Code?

Run `npx skills add LilMGenius/paperthin --skill ssotize -a claude-code`. Or copy the skill folder (skills/breadth/ssotize in LilMGenius/paperthin) into .claude/skills/ssotize in your project. Claude Code loads it when a task matches its description.

How do I install Ssotize in Codex?

Run `npx skills add LilMGenius/paperthin --skill ssotize -a codex`. Or copy the skill folder (skills/breadth/ssotize in LilMGenius/paperthin) into .agents/skills/ssotize in your project. Codex loads it when a task matches its description.

Can I use Ssotize in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LilMGenius/paperthin --skill ssotize -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ssotize, .gemini/skills/ssotize, .github/skills/ssotize and .opencode/skills/ssotize in your project.

What does Ssotize need to run?

SKILL.md names no scripts, command-line tools or credentials: Ssotize is instructions for the agent only.

Does Ssotize access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ssotize safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ssotize use?

Ssotize is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ssotize use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ssotize?

Skills that share tags, products or a category with Ssotize: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ssotize?

LilMGenius (a GitHub user) maintains it in LilMGenius/paperthin, which has 1,130 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 1, 2026.

Source: LilMGenius/paperthin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.