wiki-lint
Skill4 starsChanged 4 months agoApache-2.0View on GitHub
Audit the Living Entity Wiki for structural integrity, citations, source conflicts, drift, stale questions, and classification hygiene.
44 other projects use a version of this.
Adopted by
Most recently taken up by
- altisvc/claude-skillstheir own version, first seen Nov 16, 2026
- tboome33/obsidian-mcp-routertheir own version, first seen Nov 15, 2026
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
- ggoosen/Digital-Workforcetheir own version, first seen Nov 8, 2026
- barakgut/llm-wikitheir own version, first seen Nov 1, 2026
- chobizzy/llm-wikitheir own version, first seen Nov 1, 2026
Used with
Projects with it also use wiki-capture, wiki-status and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jehrhardtSkillwiki-capture
Quickly capture raw thoughts, links, images, or notes to today's Obsidian daily note from anywhere in Pi. Use when the user wants to jot something down for later wiki processing.
Also in 6 projects that use this
nexuschainsSkillwiki-status
Reports the current state of the wiki vault — page counts, category breakdown, hub pages, orphans, stale entries, and a delta showing what has changed since the last ingest. Use this skill when the operator asks "what's the status", "wiki dashboard", "how many pages", "what's stale", "what's been ingested", "show me the delta", or "wiki health overview". Also surfaces structural insights (top hubs, fragmented clusters, bridge pages) when the operator asks "wiki insights", "what's central", or "show me the hubs". Read-only: this skill reports and recommends; it does not modify any files.
Also in 5 projects that use this
nexuschainsSkillcross-linker
Scans the wiki vault and adds missing [[wikilinks]] between pages that are related but not yet connected. Use this skill when the operator says "link my pages", "find missing links", "cross-reference the wiki", "connect my wiki", "add wikilinks", or after any large ingest to weave new pages into the existing knowledge graph. Also trigger when orphaned pages need connecting or when wiki-lint reports fragmented tag clusters. This is a write-heavy skill — it modifies page files to insert links, unlike wiki-lint which only reports.
Also in 4 projects that use this
Ivy-Chen1999Skillwiki-setup
Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.
Also in 5 projects that use this
bozhouDevSkillwiki-init
Use when bootstrapping a new personal wiki for any knowledge domain — research, codebase documentation, reading notes, competitive analysis, or any long-term knowledge accumulation project.
Also in 7 projects that use this
Ivy-Chen1999Skillwiki-research
Autonomously research a topic via multi-round web search, synthesize findings, and file structured results into the Obsidian wiki. Use this skill when the user says "/wiki-research [topic]", "research X", "find everything about Y", "do a deep dive on Z", "autonomous research on X", or wants comprehensive, web-sourced knowledge on a topic filed directly into their wiki.
Also in 4 projects that use this
- +1 more from nexuschains
- +3 more from Ivy-Chen1999
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- AgriciDaniel/claude-obsidian★ 16ksame name
- Ar9av/obsidian-wiki★ 3.7ksame name
- kfchou/wiki-skills★ 189same name
- IssacW228/student-llm-wiki★ 173same name
- vanillaflava/llm-wiki-skills★ 65same name
- cookyman74/llmwiki-harness★ 34same name
- SantaJordan/gtm-engineer-starter★ 33same name
- Ivy-Chen1999/llm-wiki-kit★ 21same name
- schub-tech/llm-ideation-wiki★ 11same name
- CarbeneAI/Forge★ 9same name
34 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-remediationSkill
- attentionSkill
- classify-docSkill
- codebase-designSkill
- codebase-memory-mcpSkill
- codegraphSkill
- coding-standardsSkill
- contract-ledgerSkill
- conventional-commitsSkill
- database-migrationsSkill
- deduplicate-codeSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- format-codeSkill
- github-issue-dependenciesSkill
- graphifySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implement-ticketSkill
- improve-codebase-architectureSkill
- project-delivery-managementSkill
- project-trackingSkill
- prototypeSkill
- repowiseSkill
- researchSkill
- resolving-merge-conflictsSkill
- review-architectureSkill
- review-specSkill
- setup-matt-pocock-skillsSkill
- spec-contractSkill
- spec-merge-cleanupSkill
- tddSkill
- teachSkill
- to-adr-docSkill
- to-docSkill
- to-specsSkill
- to-ticketsSkill
- triageSkill
- verify-architectureSkill
- verify-codeSkill
- verify-spec-closureSkill
- verify-specSkill
- verify-ticket-closureSkill
- verify-ticket-decompositionSkill
- wayfinderSkill
- wiki-syncSkill
- wiki-synthesizeSkill
- writing-great-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
38 rules. 0 are common, 26 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
26
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Do not classify downstream drift until authoritative-source consistency is understood.
- Distinctive: line 59
Do not invent missing rationale or topology.
- Very specific: line 65
Use wiki/_schema.md and wiki/_template.md.
- Very specific: line 88
Use provenance allowed by wiki/_template.md.
- Distinctive: line 92
Do not delete claims merely because a citation is broken or stale.
- Distinctive: line 121
Do not select a winner or repair the disputed claim.
- Very specific: line 125
Do not report [source-conflict] merely because an accepted ADR still says implementation is pending, not yet realized, or equivalent while …
- Distinctive: line 132
only the ADR's descriptive realization/status statement is stale.
- Distinctive: line 145
Do not use this rule when implementation contradicts the ADR's actual decision.
- Distinctive: line 180
Do not infer realization from weak or merely suggestive evidence.
- Very specific: line 186
Do not use [code-drift] for inability to prove a claim.
- Distinctive: line 190
When expected implementation cannot be found on the current branch, inspect relevant open GitHub work when useful.
- Distinctive: line 194
If an open Spec/ticket explicitly tracks missing realization:
- Distinctive: line 196
treat it as pending rather than unexplained.
- Distinctive: line 198
do not switch branches;
- Distinctive: line 237
Do not fabricate resolution.
- Very specific: line 243
If underlying authorities disagree, use [source-conflict].
- Distinctive: line 245
If authorities agree and only derived wiki state is stale, use the appropriate drift finding.
- Distinctive: line 247
Avoid duplicate findings for the same root cause.
- Very specific: line 273
Do not report ignored paths as process or unclassified, and do not infer that an unfamiliar directory is ignored when it is not explicitly …
- Very specific: line 275
Use $classify-doc only for existing non-ADR documents inside the Living Entity Wiki document universe.
- Distinctive: line 279
Prefer the root cause:
- Distinctive: line 295
Do not emit duplicate downstream findings when one finding explains them.
- Distinctive: line 322
Do not treat architectural claim changes, source selection, realization/lifecycle transitions, or topology changes as mechanical.
- Very specific: line 363
does not edit wiki/log.md.
- Distinctive: line 364
does not create a commit.
- Distinctive: line 372
Do not log lint runs or issue counts.
- Distinctive: line 391
treat GitHub issues as architectural authority.
- Distinctive: line 392
treat unmerged work as current implementation.
- Distinctive: line 405
Before reporting a clean result, build a working Wiki Audit Coverage inventory from the repository's current canonical registries/sources.
- Very specific: line 407
every active wiki/index.md entity row and every entity page.
- Very specific: line 408
every inline source: citation on active entity pages.
- Distinctive: line 409
every authoritative source referenced by those citations whose lifecycle/eligibility must be checked.
- Very specific: line 410
every Strict Invariant/Planned/Open Question/Boundary Rationale claim requiring the applicable audit stage.
- Distinctive: line 411
every active entity pair/scope implicated by a possible cross-entity contradiction.
- Very specific: line 412
every project-owned docs/ file remaining in the classification universe after validated docs/.wikiignore exclusions are applied.
- Distinctive: line 426
Before a clean result require:
- Distinctive: line 437
When findings exist, the same coverage discipline still applies: do not stop after the first issue if other independently inspectable audit …
“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wiki Lint
$wiki-lint independently audits accumulated Living Entity Wiki state.
$wiki-sync maintains one change. $wiki-lint audits the whole.
A clean run reports only. Do not mutate the wiki, append wiki/log.md, or commit unless applying an explicitly allowed mechanical fix.
Audit Order
Run in order:
- structural integrity;
- citation resolution and eligibility;
- authoritative-source consistency;
- document/wiki drift;
- implementation drift;
- Open Questions;
- cross-entity contradictions;
- document classification.
Do not classify downstream drift until authoritative-source consistency is understood.
1. Structural Integrity
wiki/index.md is the active-entity registry.
Report [structural] for:
- entity/index mismatches;
- duplicate Entity IDs or active scopes;
- invalid
Implementationvalues; - invalid/missing Routing Anchors;
pendingwhen implementation clearly exists;presentwhen implementation cannot reasonably be found;- retired/tombstone pages under
wiki/entities/; - obsolete metadata/frontmatter;
- invalid or unsupported
docs/.wikiignoresyntax; - invalid entity-page structure;
- missing or invalid Boundary Rationale.
Allowed implementation states:
present
pendingA pending entity normally has no implementation Routing Anchor.
Entity pages must follow wiki/_template.md.
Do not invent missing rationale or topology.
2. Citation Resolution and Eligibility
Entity-document relationships exist only through inline source: citations.
Use wiki/_schema.md and wiki/_template.md.
Report:
[broken-doc-citation]— citeddocs/...path no longer resolves;[invalid-citation]— source type was never valid for that section;[stale-citation]— source was valid but its lifecycle/classification changed.
Core eligibility:
Strict Invariants
- accepted ADR;
docs/current/.
Planned
- proposed ADR;
docs/proposed/;- accepted ADR whose realization is still pending.
Rejected Approaches, Open Questions, Boundary Rationale
Use provenance allowed by wiki/_template.md.
A docs/... path matched by docs/.wikiignore is outside the Living Entity Wiki source universe and is not an eligible document citation.
Do not delete claims merely because a citation is broken or stale.
3. Authoritative-Source Consistency
Authority is claim-specific:
- implementation → what currently exists/behaves;
- accepted ADR → active architectural decision;
docs/current/→ current architectural description;- entity pages → derived knowledge, never authority.
Report [source-conflict] only when applicable authorities normatively disagree about architecture or when competing authoritative claims about current behavior cannot be reconciled without judgment.
Examples:
- incompatible architectural invariants;
- conflicting canonical owners/paths;
- incompatible boundary or dependency rules;
- one authority requires behavior another forbids;
- authoritative current-state descriptions materially disagree and no deterministic lifecycle update explains the difference.
For each [source-conflict], include:
- entity/claim;
- conflicting sources;
- what each says;
- implementation evidence;
- why the disagreement matters.
Do not select a winner or repair the disputed claim.
Realization-Status Rule
Do not report [source-conflict] merely because an accepted ADR still says implementation is pending, not yet realized, or equivalent while current implementation clearly realizes its accepted normative decision.
When:
- the ADR remains accepted;
- its normative decision agrees with the implementation;
- implementation evidence clearly realizes that decision; and
- only the ADR's descriptive realization/status statement is stale;
then classify the condition as deterministic [doc-drift], not [source-conflict].
Report:
- the accepted decision;
- evidence that implementation realizes it;
- the stale realization/status statement;
- required owner:
$to-adr-doc.
The derived wiki may already reflect the realized invariant without creating a source conflict when its claim agrees with both the ADR's normative decision and current implementation.
Do not use this rule when implementation contradicts the ADR's actual decision.
4. Document and Wiki Drift
Report [doc-drift] when meaning or lifecycle state has become stale while underlying architectural authority remains unambiguous.
Examples:
- entity claim no longer reflects its valid source;
- accepted ADR realization status remains pending after clear realization;
- current documentation describes an obsolete state while authority and implementation agree on the replacement.
For entity claims sourced from docs/current/:
- confirm the source remains current;
- ensure no
[source-conflict]; - compare the claim with current source meaning.
For Planned entries sourced from proposed material:
- compare against the current proposal;
- report drift when it changed, disappeared, or was substantively rewritten.
Accepted Implementation-Pending Decisions
For accepted ADR-backed Planned entries:
- confirm the ADR remains accepted;
- determine whether realization is still pending;
- inspect strong implementation evidence;
if clearly realized:
- stale ADR realization statement →
[doc-drift], owner$to-adr-doc; - stale wiki
Planned/Implementation: pendingstate →[doc-drift]or[structural]as applicable.
- stale ADR realization statement →
Do not infer realization from weak or merely suggestive evidence.
5. Implementation Drift
Report [code-drift] when implementation materially contradicts an active architectural invariant whose authorities otherwise agree.
Do not use [code-drift] for inability to prove a claim.
Active Implementation Work
When expected implementation cannot be found on the current branch, inspect relevant open GitHub work when useful.
Issues are workflow-status evidence only, never architectural authority or implementation proof.
If an open Spec/ticket explicitly tracks missing realization:
- treat it as pending rather than unexplained;
- inspect its declared work branch read-only when useful;
- do not switch branches;
- unmerged implementation remains in progress, not current implementation.
Closed issues are not implementation proof.
Evidence
For mechanically observable invariants, use:
- source;
- tests;
- executable architecture checks;
$codegraph;$codebase-memory-mcp;- configuration.
For intent-level invariants, report [code-drift] only when contradictory evidence exists.
Otherwise report:
no contrary implementation evidence foundnot verified.
6. Open Questions
Report [stale-question] when an Open Question deserves deliberate review because of age, changed context, or apparent later resolution.
Approximately 60 days is a heuristic, not an expiry rule.
A stale question may be:
- resolved;
- confirmed open;
- converted into another durable section;
- removed because it is no longer meaningful.
Do not fabricate resolution.
7. Cross-Entity Contradictions
Scan active entity claims for material contradictions.
If underlying authorities disagree, use [source-conflict].
If authorities agree and only derived wiki state is stale, use the appropriate drift finding.
Avoid duplicate findings for the same root cause.
8. Document Classification
Validate docs/.wikiignore against the exclusion grammar in wiki/_schema.md before using it to construct the classification universe. Invalid syntax is [structural]; do not treat an invalid line as permission to omit a path.
Construct the document-classification universe as:
all project-owned files under docs/
- docs/.wikiignore
- paths explicitly matched by valid docs/.wikiignore entries
= files subject to Living Entity Wiki classificationFor every file remaining in that universe, derive classification from:
docs/adr/plus ADR status;docs/current/;docs/proposed/;docs/research/;docs/reference/;docs/process/.
Report [unclassified-doc] for any remaining project-owned file whose classification cannot be derived from those rules.
Do not report ignored paths as process or unclassified, and do not infer that an unfamiliar directory is ignored when it is not explicitly matched by docs/.wikiignore.
Use $classify-doc only for existing non-ADR documents inside the Living Entity Wiki document universe.
Finding Priority
Prefer the root cause:
[source-conflict]
↓
[broken-doc-citation]
↓
[stale-citation] / [invalid-citation]
↓
[doc-drift]
↓
[code-drift]Exception: stale realization metadata that satisfies the Realization-Status Rule is [doc-drift], not [source-conflict].
Do not emit duplicate downstream findings when one finding explains them.
Resolution Rules
$wiki-lint reports judgment-bearing findings. It does not decide architecture.
Never automatically resolve:
- genuine
[source-conflict]; [code-drift];- semantic
[doc-drift]; - ambiguous citation findings;
- stale questions;
- cross-entity semantic contradictions;
- topology or Boundary Rationale.
Mechanical Fixes
Apply a fix only when exactly one correction is unambiguous and no architectural judgment is required.
Examples:
- stale link after known rename;
- formatting damage;
- duplicate registry row;
- Routing Anchor changed only by established path rename.
Do not treat architectural claim changes, source selection, realization/lifecycle transitions, or topology changes as mechanical.
For stale accepted-ADR realization status, report $to-adr-doc as owner rather than editing the ADR directly.
Reporting
Use:
[source-conflict]
[code-drift]
[doc-drift]
[stale-citation]
[invalid-citation]
[broken-doc-citation]
[unclassified-doc]
[stale-question]
[structural]Each finding includes:
- entity/claim;
- evidence/sources;
- relevant implementation evidence;
- relevant open work when applicable;
- why it matters;
- required next action/owner.
End with counts by finding type.
Clean result:
Wiki lint: 0 issues foundLogging and Commits
A report-only or clean run:
- does not edit
wiki/log.md; - does not create a commit.
For an allowed mechanical fix:
- append one semantic
wiki/log.mdentry; - land fix and log atomically;
- defer commit ownership to the calling workflow when one exists.
Do not log lint runs or issue counts.
Related Skills
$wiki-sync— per-change synchronization;$to-adr-doc— ADR lifecycle and realization-status updates;$to-doc— new non-ADR documents;$classify-doc— existing non-ADR classification;$wiki-synthesize— higher-inference synthesis.
Out of Scope
$wiki-lint does not:
- bootstrap the wiki;
- decide entity boundaries;
- settle genuine source conflicts;
- rewrite architectural decisions;
- directly update ADR realization/lifecycle state;
- treat GitHub issues as architectural authority;
- treat unmerged work as current implementation;
- infer intent-level compliance from absence of evidence;
- maintain obsolete entity metadata;
- classify
docs/.wikiignore-excluded documentation as Living Entity Wiki source material; - log clean runs;
- perform cross-entity synthesis.
Its job is to determine whether the Living Entity Wiki can be trusted, distinguish genuine authority conflicts from ordinary lifecycle drift, and route correction to the proper owner.
Transition-Bound Wiki Audit Coverage
Wiki lint: 0 issues found is an exhaustive claim and requires a materialized audit universe. Zero findings among the surfaces that happened to be inspected is not a clean audit.
Before reporting a clean result, build a working Wiki Audit Coverage inventory from the repository's current canonical registries/sources. At minimum account for the candidate universes relevant to the eight audit stages:
- every active
wiki/index.mdentity row and every entity page; - every inline
source:citation on active entity pages; - every authoritative source referenced by those citations whose lifecycle/eligibility must be checked;
- every Strict Invariant/Planned/Open Question/Boundary Rationale claim requiring the applicable audit stage;
- every active entity pair/scope implicated by a possible cross-entity contradiction;
- every project-owned
docs/file remaining in the classification universe after validateddocs/.wikiignoreexclusions are applied.
Each candidate receives a working disposition:
Candidate: WA-<n>
Audit stage: <1..8>
Surface/claim: <exact identity>
Disposition: <checked | finding:<type/id> | not-applicable>
Evidence/reason: <direct evidence or exact N/A reason>Candidates may be generated by more than one stage when genuinely necessary; deduplicate identical stage+claim obligations rather than silently dropping them.
Before a clean result require:
Audit candidates: <n>
Coverage rows: <n>
Missing/unclassified candidates: 0
Unchecked candidates: 0
Not-applicable rows without reason: 0
Findings: 0When findings exist, the same coverage discipline still applies: do not stop after the first issue if other independently inspectable audit stages remain. A concise finding report is still allowed; the full working coverage table need not be persisted.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

