SkillAgentSearch skills...

second-brain-lint

Audit a second-brain vault for structural problems and repair them: broken wikilinks, orphan pages, empty stubs, frontmatter that violates the schema, near-duplicate pages, and stale index entries.

Install / Use

npx skills add undefined-ui/second-brain-os --skill second-brain-lint

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Tags

Our assessment of second-brain-lint

second-brain-lint scores 83/100 on our quality scale, 945th of 1,173 Content & Media skills we index.

Its SKILL.md is 2.6 KB long, split into 5 sections with 1 code example: a solid amount of guidance for an agent.

It has 988 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 14 days ago, so second-brain-lint is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

second-brain-lint compared with similar skills

All 4 of these similar skills score higher than second-brain-lint; compare them before choosing.

SkillScoreStarsUpdatedFormat
second-brain-lint (this skill)by undefined-ui8398814d agoSKILL.md
siyuanby siyuan-note10046.8ktodayMCP Server
algorithmic-artby anthropics100177.9k21d agoSKILL.md
pptxby anthropics100177.9k21d agoSKILL.md
designby nextlevelbuilder100133.6k10d agoSKILL.md

Frequently asked questions

How do I install second-brain-lint?
Run npx skills add undefined-ui/second-brain-os --skill second-brain-lint. The install tabs above show the steps for each supported agent.
Which AI agents does second-brain-lint work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is second-brain-lint safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is second-brain-lint still maintained?
The repository was last updated 14 days ago, so second-brain-lint is actively maintained.

name: second-brain-lint description: >- Audit a second-brain vault for structural problems and repair them: broken wikilinks, orphan pages, empty stubs, frontmatter that violates the schema, near-duplicate pages, and stale index entries. Use this skill whenever the user asks to lint, clean, audit or check the health of their vault, says pages feel messy or links are broken, after a large bulk import, or when a scheduled maintenance run fires. Do NOT use for ingesting new sources, for answering questions from the vault, or for rewriting page content that is structurally fine but reads badly.

Lint the vault

Structural rot is silent. Nothing errors, nothing crashes, the vault just slowly stops answering questions well because a third of its pages are unreachable. Linting is the only thing that catches it before the owner does.

Core rule

Report before repairing. Fix the mechanical problems automatically, but never delete or merge a page without listing it first and getting a yes, because the owner may have written it by hand.

Workflow

  1. Inventory. Count pages by type. Build the link graph by parsing every [[wikilink]].
  2. Broken links. Links pointing at pages that do not exist. Distinguish two cases: a typo or rename, which you fix, and a genuine gap, which goes into index.md under Gaps.
  3. Orphans. Pages with no inbound links. For each, either find where it should be linked from and add the link, or flag it as a candidate for deletion.
  4. Stubs. Pages under roughly 40 words with no links. Usually a failed ingest. Flag for re-ingest from the original source in raw/.
  5. Schema. Missing or malformed frontmatter, wrong type, missing dates, tags outside the existing vocabulary.
  6. Near-duplicates. Pages with very similar titles or aliases. Propose merges; do not perform them unsolicited.
  7. Index drift. Pages missing from index.md, index entries pointing nowhere.
  8. Repair, then append the run to log.md.

Output format

Vault: <n> pages (<n> sources, <n> concepts, <n> entities, <n> synthesis)
Link graph: <n> links, average <n> per page, <n> orphans

Fixed automatically:
- <list>

Needs a decision:
- <list, each with the recommended action>

Health: orphan rate <n>%, broken link rate <n>%, stub rate <n>%

Calibration

An aggressive linter that merges pages on its own judgement destroys work. A timid one that only reports produces a list nobody acts on. The split above is the useful line: mechanical fixes happen, semantic decisions get proposed.

Do not run a full lint after every ingest. Weekly, or after an import of more than about twenty sources.

Related Skills

View on GitHub
GitHub Stars988
CategoryContent
Updated14d ago
Forks158

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
second-brain-lint — Universal Skill: Install & Safety Check | SkillAgent