360 Secure SkillHub
360 安全技能中心

Wiki Lint

该 Skill 指导 Agent 巡检 markdown 知识 wiki,检查页面间矛盾、过时论断、孤立页、重复页、命名与 frontmatter 不一致、引用薄弱等问题,按严重程度分组输出报告并给出最小修复方案,用户要求时可直接实施高价值修复;另附一份精简检查清单供参考。

teki-ai
teki-ai
热度 44.68
最近更新 2026-05-11 17:42:32
分类:知识依赖:读写文件 / 内部调用大模型应用场景:笔记整理 / 校对润色 / 报告撰写 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add wiki-lint
Metadata
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.