Skill: teki-ai/wiki-lint (version 0.1.0)

--- name: wiki-lint description: Lint and health-check a persistent markdown knowledge wiki. Use when a user wants the agent to inspect a wiki for contradictions, stale claims, missing cross-links, orphan pages, duplicate pages, inconsistent naming, inconsistent frontmatter, schema drift, weak source attribution, or other maintenance issues. Best for Obsidian-friendly, plain markdown, or git-backed wikis that are maintained over time and need periodic cleanup or structural review. --- # Wiki Lint Inspect a markdown knowledge wiki for structural and content quality problems. Produce actionable findings that improve consistency, navigability, and trustworthiness without forcing unnecessary rewrites. ## Lint workflow 1. Inspect the wiki schema and top-level structure 2. Review `index.md` and `log.md` when available 3. Sample representative topic, entity, concept, source, and analysis pages 4. Identify the highest-value consistency and maintenance issues 5. Group findings by severity 6. Recommend concrete fixes 7. When asked, implement the highest-value fixes first ## What to look for Check for: - contradictions between pages - stale claims superseded by newer material - orphan pages with weak or missing inbound links - duplicate pages with overlapping scope - missing cross-links between obviously related pages - important repeated concepts that still lack canonical pages - broken naming conventions - inconsistent frontmatter or page structure - weak citation or source attribution - analysis pages that should be linked from topic or entity pages but are not ## Output shape Prefer a concise report grouped into: - critical consistency issues - important quality improvements - optional structure improvements For each issue, include: - what is wrong - why it matters - the smallest useful fix ## Linting philosophy Prefer gradual repair over massive rewrites. Follow existing conventions unless they are clearly harmful. If a larger schema change is justified, propose it before applying it. ## References Read `references/lint-checklist.md` for a compact checklist and reporting pattern.

path: references/lint-checklist.md
content: # Wiki Lint Checklist

Use this checklist when reviewing a markdown knowledge wiki.

## Structural checks

- Does the wiki have a clear schema or at least stable conventions?
- Is `index.md` still useful as a navigation map?
- Is `log.md` append-only and parseable?
- Are page names stable and human-readable?

## Content checks

- Do important pages start with a short summary?
- Are claims supported by source pages or clearly marked as synthesis?
- Are contradictions surfaced instead of smoothed over?
- Are outdated claims still presented as current?

## Linking checks

- Do major pages link to related concepts and entities?
- Are there orphan pages?
- Are there duplicate pages that should be merged?
- Are durable analysis pages linked from the pages they affect?

## Reporting pattern

```markdown
# Wiki Lint Report

## Critical consistency issues
- issue

## Important quality improvements
- issue

## Optional structure improvements
- issue
```
```

## Fix prioritization

Prioritize:
1. contradictions and stale claims
2. duplicate or ambiguous canonical pages
3. broken navigation and missing cross-links
4. cosmetic consistency improvements


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)