Support Wiki Linter
Lint a support wiki for the drift that accumulates over hundreds of articles: broken links, stale screenshots, inconsistencies.
by AgentVoltv1.0.0
Free to sign up · every skill included with AgentVolt Pro
Before & after
Same prompt, same agent — the only difference is the skill.
Prompt“Lint our internal wiki for outdated docs, broken links, and formatting issues.”
Beforegeneric AI agent
A wiki linter checks documentation for consistency, broken references, and staleness. You'd typically look for missing links, outdated information, inconsistent formatting, and pages that haven't been updated in a long time. I'd recommend establishing what 'outdated' means first—is something stale after 6 months? Do you have pages that require regular review cycles? Should you automate this check or do it manually? What are your main pain points with the wiki right now?
Afterwith Support Wiki Linter
INTERNAL WIKI LINTING REPORT EXECUTIVE SUMMARY → Total pages scanned: 247 → Critical issues: 18 (block reader understanding) → Warning issues: 34 (inconsistency, minor friction) → Green issues: 195 (compliant) → Recommendation: Priority fix 18 critical by EOD CRITICAL ISSUES (Must fix) CATEGORY: Broken Links (8 found) → Page 'API Documentation' links to deleted 'v2-endpoints' page → Page 'Deployment Guide' references dead imgur URL (4 links) → Page 'Troubleshooting' references old Slack channel #dev-help (archived 2026-03) → ACTION: Redirect v2-endpoints to v3-endpoints, fix Slack reference, update image URLs CATEGORY: Dangerously Outdated (6 found) → 'Getting Started' references Node 14 (current: 18+) → 'Database Setup' mentions Postgres 11 (current: 15+) → 'Production Checklist' references deprecated env var MONGODB_URI (removed 2026-04) → 'Release Process' mentions Jenkins (migrated to GitHub Actions 2026-05) → Last updated: 8+ months ago, no reviewer signature → ACTION: Flag for mandatory review by engineering lead, add update date to header CATEGORY: Missing Critical Info (4 found) → 'First Week On-Call' missing link to runbook repository → 'Billing FAQ' never updated after pricing change (2026-02) → 'Performance Baseline' missing thresholds for alerts → ACTION: Add reviewers to CODEOWNERS, set update frequency WARNING ISSUES (Fix within 1 week) CATEGORY: Inconsistent Formatting (12 found) → 'Setup Guide' uses backticks for code; 'Deployment Guide' uses code blocks → Headings inconsistent: some Title Case, some lowercase → Bullet vs numbered lists vary by section → ACTION: Standardize on code blocks, Title Case headers, bullets for non-sequential CATEGORY: Orphaned Pages (8 found) → 8 pages unreachable from main navigation or index → Likely outdated or superseded → ACTION: Add breadcrumb to each or consider archive CATEGORY: Missing Table of Contents (10 found) → Pages over 3 sections lack TOC → Reduces scannability → ACTION: Add auto-generated TOC to 10 pages CATEGORY: Accessibility Issues (4 found) → 4 images missing alt text descriptions → Heading hierarchy broken (h3 before h2) in 2 pages → ACTION: Audit and fix heading structure PRIORITIZATION ROADMAP Today: [ ] Fix 8 broken external links [ ] Update 4 dangerously outdated tech references [ ] Add link to runbook in on-call guide Week 1: [ ] Standardize formatting across 12 inconsistent pages [ ] Add TOC to 10 large pages [ ] Fix image alt text Week 2: [ ] Establish update schedule for 6 high-value pages [ ] Archive or restore 8 orphaned pages [ ] Add reviewer name + date to critical pages ONGOING MAINTENANCE → Wiki lint automation: Run monthly via CI/CD → Freshness policy: Pages over 6 months need reviewer sign-off → Broken link check: Weekly automated scan → Format consistency: Pre-commit hook prevents new issues
About this skill
name: cs-wiki-linter description: Use when Structured Claude skill that gives Claude a repeatable workflow for cs wiki linter.
Cs Wiki Linter
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Cs Wiki Linter workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the cs-wiki-linter skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Cs Wiki Linter; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
SKILL.md
---
name: cs-wiki-linter
description: Use this skill when auditing a customer-support or internal wiki for outdated content, broken links, inconsistent tone, or missing metadata.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Cs Wiki Linter
Runs a structured lint pass over a support wiki, catching the drift that accumulates over hundreds of articles: broken links, stale screenshots, inconsistent tone, and duplicate coverage.
## When to use
… (sign up to view the full skill)Sign up to view, copy, and install the full skill
More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
AI & Agents
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
AI & Agents
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
AI & Agents
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.
AI & Agents