mcpbeat Sign in

Second Brain Lint Agent Skill

> Health-check the wiki for contradictions, orphan pages, stale claims, and missing cross-references. Use when the user says "audit", "health check", "lint", "find problems", or wants to improve wiki quality.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
651
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/NicholasSpisak/second-brain --skill second-brain-lint

The instruction itself

19 sections, as written by the author

Second Brain — Lint

Health-check the wiki and report issues with actionable fixes.

Audit Steps

Run all checks below, then present a consolidated report.

Scan all wiki pages for [[wikilink]] references. For each link, verify the target page exists. Report any broken links.

# Find all wikilinks across wiki pages
grep -roh '\[\[[^]]*\]\]' wiki/ | sort -u

Cross-reference against actual files in wiki/.

2. Orphan pages

Find pages with no inbound links — no other page references them via [[wikilink]].

For each .md file in wiki/sources/, wiki/entities/, wiki/concepts/, wiki/synthesis/:

  • Extract the page name (filename without extension)
  • Search all other wiki pages for [[Page Name]]
  • If no other page links to it, it's an orphan

3. Contradictions

Read pages that share entities or concepts and look for conflicting claims. Flag when:

  • Two source summaries make opposing claims about the same topic
  • An entity page contains information that conflicts with a source summary
  • Dates, figures, or factual claims differ between pages

4. Stale claims

Cross-reference source dates with wiki content. Flag when:

  • A concept page cites only old sources and newer sources exist on the same topic
  • Entity information hasn't been updated despite newer sources mentioning that entity

5. Missing pages

Scan for [[wikilinks]] that point to pages that don't exist yet. These are topics the wiki mentions but hasn't given their own page. Assess whether they warrant a page.

6. Missing cross-references

Find pages that discuss the same topics but don't link to each other. Look for:

  • Entity pages that mention concepts without linking them
  • Concept pages that mention entities without linking them
  • Source summaries that cover the same topic but don't reference each other

7. Index consistency

Verify wiki/index.md is complete and accurate:

  • Every page in wiki/sources/, wiki/entities/, wiki/concepts/, wiki/synthesis/ has an index entry
  • No index entries point to deleted pages
  • Entries are under the correct category header

8. Data gaps

Based on the wiki's current coverage, suggest:

  • Topics mentioned frequently but lacking depth
  • Questions the wiki can't answer well
  • Areas where a web search could fill in missing information

Report Format

Present findings grouped by severity:

Errors (must fix)

  • Broken wikilinks
  • Contradictions between pages
  • Index entries pointing to missing pages

Warnings (should fix)

  • Orphan pages with no inbound links
  • Stale claims from outdated sources
  • Missing pages for frequently referenced topics

Info (nice to fix)

  • Potential cross-references to add
  • Data gaps that could be filled
  • Index entries that could be more descriptive

For each finding, include:

  • What: description of the issue
  • Where: the specific file(s) and line(s)
  • Fix: what to do about it

After the Report

Ask the user:

> "Found N errors, N warnings, and N info items. Want me to fix any of these?"

If the user agrees, fix issues and report what changed.

Log the lint pass

Append to wiki/log.md:

[YYYY-MM-DD] lint | Health check

Found N errors, N warnings, N info items. Fixed: [list of fixes applied].

When to Lint

  • After every 10 ingests — catches cross-reference gaps while they're fresh
  • Monthly at minimum — catches stale claims and orphan pages over time
  • Before major queries — ensures the wiki is healthy before you rely on it for analysis
  • /second-brain-ingest — process new sources into wiki pages
  • /second-brain-query — ask questions against the wiki

Other skills for the same job

different authors, same section of the catalogue
Receiving Code Review
by ZhanlinCui
×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens
Requesting Code Review
by ZhanlinCui
×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

2k tokens
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Karpathy Guidelines
by hyyhf
×3

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

629 tokens
Code Reviewer
by google-gemini
vendor ×2

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

795 tokens
Agent MD Refactor
by softaworks
×2

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

4k tokens
Commit Work
by softaworks
×2

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take nicholasspisak/second-brain-lint from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.