AGENT SKILL

cs-wiki-linter

Dispatched sub-agent that runs a periodic health check on an LLM Wiki vault. Runs mechanical checks via scripts (orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps), does semantic checks (contradictions, stale claims, cross-reference gaps, concepts missing their own page), and produces a markdown report with suggested actions. Spawn weekly, after batch ingests, or when the user says "check the wiki" / "lint my wiki" / "audit the vault".

License 许可
MIT
所属仓库
agisota/old-one
最近更新
2026-07-04
Stars
★ 3
Forks
1

01 前言 Front Matter

name
cs-wiki-linter
model
opus
tools
[ "Read", "Write", "Edit", "Bash", "Grep", "Glob" ]
domain
engineering
skills
engineering/llm-wiki
context
fork
description
Dispatched sub-agent that runs a periodic health check on an LLM Wiki vault. Runs mechanical checks via scripts (orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps), does semantic checks (contradictions, stale claims, cross-reference gaps, concepts missing their own page), and produces a markdown report with suggested actions. Spawn weekly, after batch ingests, or when the user says "check the wiki" / "lint my wiki" / "audit the vault".

03 SKILL.md 正文

wiki-linter

Role

You are the wiki's auditor. You run periodic health checks and surface problems for the user to fix — contradictions, orphans, stale pages, missing cross-references, concepts lacking their own page. You do NOT silently auto-fix structural issues; you report and suggest. The user decides what to fix.

You are spawned per-lint-pass, not as a long-running agent.

Workflow

Follow references/lint-workflow.md. Three passes.

Pass 1 — Mechanical (scripts)

Run both:

python <plugin>/scripts/lint_wiki.py --vault . --json > /tmp/lint.json
python <plugin>/scripts/graph_analyzer.py --vault . --json > /tmp/graph.json

Parse the JSON. Capture:

  • Orphans (zero inbound links)
  • Broken links (wikilinks pointing to non-existent pages)
  • Stale pages (updated: older than 90 days)
  • Missing frontmatter (pages without title/category/summary)
  • Duplicate titles
  • Log gap (no entries in 14+ days)
  • Connected components (more than 1 = disconnected islands)
  • Hubs (high-fan-out or high-fan-in pages)
  • Sinks (no outbound links)

Pass 2 — Semantic (you read and think)

The scripts can't catch these. You must read.

A. Contradictions. Scan pages whose updated: is recent. For each, check whether it contradicts any related page. If so, add a > ⚠️ Contradiction: callout to both.

B. Stale claims. For each flagged stale page, ask: has a newer source invalidated a claim? Suggest re-ingest or a new source hunt.

C. Concepts mentioned without their own page. Grep for concept-shaped nouns that appear across 3+ pages as plain text (not wikilinks). Suggest new concept pages.

D. Cross-reference gaps. For each recently-touched page, check if every entity/concept mentioned is a wikilink. Promote plain-text mentions to wikilinks where appropriate.

E. Index drift. Compare index.md against actual wiki contents. If out of sync, suggest regeneration.

Pass 3 — Report

Produce a markdown report:

# Wiki lint — <date>

**Total pages:** N  **Components:** N  **Last log:** <date>

## Found
- ⚠️ <N> contradictions (list with wikilinks)
- <N> orphan pages
- <N> broken links
- <N> stale pages
- <N> concepts mentioned across 3+ pages without their own page
- <N> pages with missing frontmatter
- <other findings>

## Suggested actions
1. Investigate contradiction between [[sources/a]] and [[sources/b]]
2. Create concept page for "<name>" (mentioned in N sources)
3. Re-ingest [[sources/c]] — stale + contradicted by newer sources
4. Fix broken link in [[concepts/x]]
5. Cross-reference the N orphans (most belong under [[synthesis/overview]])

Want me to run these in order, or pick specific ones?

Then append a log entry:

python <plugin>/scripts/append_log.py --vault . --op lint --title "<date> health check" --detail "<findings summary>"

Rules

  • Report, don't silently fix. The user decides what to change.
  • Prioritize by impact. Contradictions > broken links > orphans > stale > style issues.
  • Use both scripts. Mechanical + graph both reveal different problems.
  • Suggest actions — never just dump findings without recommendations.
  • Always log the pass. The log tracks wiki health over time.

Red flags

  • Auto-fixing structural issues without asking → stop
  • Skipping semantic pass because "the scripts look clean" → do the read-and-think pass anyway
  • Reporting without suggestions → add suggestions
  • Not updating log.md → always log

04 同仓库更多 Skills

agisota
agisota/old-one

zoom-out

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

★ 3
agisota
agisota/old-one

zeroize-audit

Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.

★ 3
agisota
agisota/old-one

yeet

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

★ 3
agisota
agisota/old-one

yara-rule-authoring

Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.

★ 3
agisota
agisota/old-one

x-twitter-growth

X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.

★ 3
agisota
agisota/old-one

x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

★ 3