agentleFS
schub-techschub-tech/llm-ideation-wiki/.agents/skills/wiki-lint/SKILL.md

wiki-lint

Skill11 starsChanged 31 days agoMITView on GitHub

Run semantic wiki lint beyond structural link checks. Use when the user asks to audit, lint, health-check, find stale claims, find unsupported claims, check provenance, or identify contradictions in the wiki.

43 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use wiki-capture, wiki-status and 10 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.
  • jehrhardtSkill

    wiki-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

  • nexuschainsSkill

    wiki-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

  • nexuschainsSkill

    cross-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-Chen1999Skill

    wiki-synthesize

    Systematically discover synthesis opportunities across the Obsidian wiki — pairs or clusters of concepts that co-occur frequently across pages but have no synthesis page connecting them. Creates new synthesis/ pages that draw explicit cross-cutting conclusions. Use when the user says "synthesize my wiki", "find connections", "what concepts keep coming up together", "/wiki-synthesize", or after a large ingest when the vault has grown significantly.

    Also in 4 projects that use this

  • Ivy-Chen1999Skill

    wiki-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

  • bozhouDevSkill

    wiki-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

  • +1 more from nexuschains
  • +4 more from Ivy-Chen1999

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run a semantic lint pass over the business-idea wiki.

    line 6
  2. Very specific:

    Run the deterministic Notion helper checks from docs/agent/workflows.md.

    line 10
  3. Distinctive:

    Read the relevant Notion idea page before reading deep-dive pages.

    line 11
  4. Distinctive:

    Risk/verdict mismatch: If a risk could kill the idea, the verdict and Next moves must reflect it.

    line 19
  5. Very specific:

    Answered validations: If a Still to validate item is already answered in a deep-dive or raw note, update or remove it.

    line 20
  6. Distinctive:

    Use priorities this way:

    line 40
  7. Distinctive:

    If the user asked you to fix issues, edit the Notion wiki directly, then run the ritual (AGENTS.md § Mechanics).

    line 46

“Common” is measured: kept by at least 6 in 10 of the 34 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run a semantic lint pass over the business-idea wiki. This complements the Notion helper checks in docs/agent/workflows.md; it does not replace them.

Start with deterministic checks.

  1. Run the deterministic Notion helper checks from docs/agent/workflows.md.
  2. Read the relevant Notion idea page before reading deep-dive pages.

Semantic checks. For each idea, inspect the overview and its related deep-dive notes for:

  • Unsupported material claims. Any statistic, price, legal statement, named competitor claim, market-size claim, or dated event must have a raw-source line citation.
  • Unmarked synthesis. Claims that are inferred from multiple sources, not directly stated by one source, should carry ^[inferred].
  • Ambiguity drift. Contested or weak claims should carry ^[ambiguous] and should not be written as settled.
  • User-only premises. Founder assertions, anecdotes, and "everyone says yes" style evidence should carry ^[user-claim] unless independently validated.
  • Risk/verdict mismatch. If a risk could kill the idea, the verdict and Next moves must reflect it.
  • Answered validations. If a Still to validate item is already answered in a deep-dive or raw note, update or remove it.
  • Stale claims. Pages older than 90 days should be checked for date-sensitive claims before being treated as current.
  • Mapping mismatch. Notion pages that should be script-addressable should either be added to notion.config.json or explicitly left as manually navigated child pages.
  • Prose bloat. Flag any sentence over ~20 words, any bullet carrying two claims, and any run of more than ~3 sentences of prose. Rewrite to the ## Output rules in AGENTS.md.

Report format. Lead with the highest-severity findings:

## Semantic Lint

### P1
- [Page](path) — claim/risk. Why it matters. Suggested fix.

### P2
- ...

### Maintenance
- Mapping/index/log/hot-cache updates needed.

Use priorities this way:

  • P1: Could change the verdict or invalidate a next move.
  • P2: Material but not immediately verdict-changing.
  • P3: Hygiene, clarity, or future retrieval quality.

If the user asked you to fix issues, edit the Notion wiki directly, then run the ritual (AGENTS.md § Mechanics).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.