Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

obsidian-wiki-linter

Étoiles3

Forks2

Mis à jour7 juin 2026 à 04:06

Runs a semantic health check over the Obsidian LLM wiki using the cheapest available LLM CLI. Finds inconsistencies, missing concepts, stale articles, connection candidates, and new article suggestions. Writes a structured report to meta/lint-report.md. Use when the wiki is large enough to have quality drift, or as a periodic maintenance step.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

richfrem

richfrem/agent-plugins-skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

6 fichiers

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

agent-swarm

richfrem/agent-plugins-skills

(Industry standard: Parallel Agent) Primary Use Case: Work that can be partitioned into independent sub-tasks running concurrently across multiple agents. Parallel multi-agent execution pattern. Use when: work can be partitioned into independent tasks that N agents can execute simultaneously across worktrees. Includes routing (sequential vs parallel), merge verification, and correction loops.

2026-06-083

dual-loop

richfrem/agent-plugins-skills

(Industry standard: Sequential Agent / Agent as a Tool) Primary Use Case: Delegating a well-defined task to a worker agent, verifying its execution, and repeating if necessary. Inner/outer agent delegation pattern. Use when: work needs to be delegated from a strategic controller (Outer Loop) to a tactical executor (Inner Loop) via strategy packets, with verification and correction loops.

2026-06-083

learning-loop

richfrem/agent-plugins-skills

(Industry standard: Loop Agent / Single Agent) Primary Use Case: Self-contained research, content generation, and exploration where no inner delegation is required. Self-directed research and knowledge capture loop. Use when: starting a session (Orientation), performing research (Synthesis), or closing a session (Seal, Persist, Retrospective). Ensures knowledge survives across isolated agent sessions.

2026-06-083

orchestrator

richfrem/agent-plugins-skills

(Industry standard: Routing Agent / Orchestrator Pattern) Primary Use Case: Analyzing an ambiguous trigger and routing it to one of the specific specialized implementations. Routes triggers to the appropriate agent-loop pattern. Use when: assessing a task, research need, or work assignment and deciding whether to run a simple learning loop, red team review, dual-loop delegation, or parallel swarm. Manages shared closure (seal, persist, retrospective, self-improvement).

2026-06-083

red-team-review

richfrem/agent-plugins-skills

(Industry standard: Review and Critique Pattern) Primary Use Case: Iterative generation paired with adversarial review, continuing until an 'Approved' verdict is reached. Orchestrated adversarial review loop. Use when: research, designs, architectures, or decisions need to be reviewed by red team agents (human, browser, or CLI). Iterates in rounds of research → bundle → review → feedback until approved.

2026-06-083

triple-loop-learning

richfrem/agent-plugins-skills

(Industry standard: Meta-Learning System / Automated Autoresearch) Primary Use Case: Continuous, self-improving orchestration of an agentic system over multiple sessions. Use when: building a continuous improvement layer that autonomously identifies workflow friction, postulates hypotheses, and tests improved instructions/coding skills against an objective headless benchmark before merging and persisting.

2026-06-083

name	obsidian-wiki-linter
plugin	obsidian-wiki-engine
description	Runs a semantic health check over the Obsidian LLM wiki using the cheapest available LLM CLI. Finds inconsistencies, missing concepts, stale articles, connection candidates, and new article suggestions. Writes a structured report to meta/lint-report.md. Use when the wiki is large enough to have quality drift, or as a periodic maintenance step.
allowed-tools	Bash, Read, Write

Dependencies

Requires Python 3.8+ and at least one CLI installed: copilot, claude, or gemini.

pip install -r requirements.txt

Obsidian Wiki Linter

Status: Active Author: Richard Fremmerlid Domain: Obsidian Wiki Engine

Purpose

Performs a semantic health check over the LLM wiki — the step Karpathy calls "linting." Unlike audit.py (which checks structural coverage: orphans, missing summaries, broken wikilinks), this skill uses an LLM to analyze semantic quality: contradictions, knowledge gaps, and connection opportunities that only emerge once the wiki is large enough to have internal consistency requirements.

What It Checks

Category	What it finds
Inconsistencies	Contradicting claims between two concept pages
Missing Concepts	Topics implied by existing articles but not yet written
Stale Articles	Pages with vague, outdated, or thin content
Connection Candidates	Concept pairs that should have wikilinks but don't
New Article Suggestions	Topics the wiki should cover based on its current scope

Usage

Run semantic health check (default engine)

python ./scripts/lint_wiki.py --wiki-root /path/to/wiki-root

Sample more pages for larger wikis

python ./scripts/lint_wiki.py --wiki-root /path/to/wiki-root --sample 30

Force engine

python ./scripts/lint_wiki.py --wiki-root /path/to/wiki-root --engine claude

Dry run (print prompt without calling LLM)

python ./scripts/lint_wiki.py --wiki-root /path/to/wiki-root --dry-run

Engine Fallback Chain

Same strict cheap-model chain as obsidian-rlm-distiller:

1. copilot  → gpt-5-mini        (Paid, AI Credits)
2. claude   → claude-haiku-4-5  (fallback, Paid)
3. gemini   → gemini-3-flash-preview (final fallback, Paid)

Output

Report is written to {wiki-root}/meta/lint-report.md with YAML frontmatter:

generated_at: "2026-04-16T..."
engine: "claude"
model: "claude-haiku-4-5"

Followed by five sections:

Inconsistencies — conflicting claims between articles
Missing Concepts — implied but not yet written
Stale or Weak Articles — need richer content
Connection Candidates — wikilinks to add
New Article Suggestions — fresh topics to write

When to Use

After the wiki reaches ~20+ concept nodes (semantic quality starts to matter)
As a weekly maintenance step before a major query session
When you notice the wiki feels inconsistent or fragmented
Before filing --save-as outputs back — lint first to know what gaps to fill
As the final step in /wiki-rebuild (after ingest, distill, build)

Audit vs. Lint

`audit.py`	`lint_wiki.py`
Structural: missing summaries, broken links, orphans	Semantic: contradictions, gaps, stale content
Always fast, no LLM needed	Requires LLM call
Run before every `/wiki-query`	Run periodically (weekly or post-rebuild)
Exit code 1 on critical issues	Always exits 0 (report-only)

Related Scripts

lint_wiki.py — semantic health check orchestrator
audit.py — structural coverage checker (complementary)
distill_wiki.py — shares engine detection logic