markdown-linterValidates Markdown files in the workspace for broken local links, missing file references, and basic syntax issues. Use to maintain documentation integrity a...
Install via ClawdBot CLI:
clawdbot install wanng-ide/markdown-linterGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Potentially destructive shell commands in tool definitions
exec(Audited Apr 17, 2026 · audit v1.0
Generated Mar 22, 2026
Development teams use the linter to validate internal documentation like README files and API guides, ensuring all local links to code examples or configuration files are intact. This prevents broken references during project updates or when onboarding new developers, maintaining documentation reliability across repositories.
Technical writers employ the linter to check Markdown files for broken image links and proper header hierarchies in user manuals or help articles. It helps catch errors before publishing, reducing support tickets and improving user experience with accurate, well-structured documentation.
Researchers use the linter to validate Markdown-based lab notebooks or paper drafts, ensuring references to data files or supplementary materials are correct. This maintains integrity in collaborative projects by preventing missing links that could delay analysis or publication.
Companies integrate the linter into their internal wiki systems to automatically scan for broken links in employee training materials or policy documents. This ensures up-to-date information, reduces confusion, and supports compliance by keeping all references accessible.
Open source maintainers run the linter on community-contributed Markdown files to validate links to source code or external resources before merging pull requests. This streamlines review processes and enhances project quality by preventing broken documentation in public repositories.
Offer a free basic version for individual users with limited scans, and a paid tier for teams with advanced features like CI/CD integration and priority support. Revenue comes from monthly subscriptions, targeting small to medium-sized businesses needing reliable documentation workflows.
Sell enterprise licenses to large organizations for integrating the linter into their internal development or content management systems. Revenue is generated through one-time fees or annual contracts, with customization options and dedicated support for high-volume usage.
Provide consulting services to help companies set up and customize the linter within their existing workflows, such as adding it to Git hooks or documentation pipelines. Revenue comes from project-based fees and ongoing maintenance contracts, focusing on industries with strict documentation standards.
💬 Integration Tip
Integrate the linter into CI/CD pipelines using the provided JavaScript API to automatically scan Markdown files on commits, ensuring broken links are caught early without manual intervention.
Scored Apr 19, 2026
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Ship production code with AI agents through acceptance contracts, micro diffs, red green loops, and deterministic handoff checkpoints.