Markdown Linter

Validates Markdown files in the workspace for broken local links, missing file references, and basic syntax issues. Use to maintain documentation integrity a...

This linter appears to do what it says: it walks the workspace, reads Markdown files, and checks whether linked files exist. It does not transmit data or require credentials. Two practical cautions before using it on sensitive workspaces: (1) if Markdown files contain links that point to absolute paths (starting with '/'), the linter will check those absolute system paths and will report whether they exist — avoid scanning untrusted content that could intentionally probe your filesystem; (2) as with any code-runner, review the included files yourself and run the test in an isolated/sandbox environment first. If you need to prevent absolute-path checks, run the linter with a controlled rootDir or modify the code to explicitly treat leading '/' as relative to the project root only.

Type: OpenClaw Skill Name: markdown-linter Version: 1.0.0 The skill is classified as suspicious due to its use of file system access (`fs.readdirSync`, `fs.statSync`, `fs.readFileSync`, `fs.existsSync`) in `index.js`. While this file access is plausibly needed for the skill's stated purpose of validating Markdown files, the instructions classify such capabilities without clear malicious intent as 'suspicious'. There is no evidence of intentional harmful behavior like data exfiltration, persistence, or prompt injection attempts in SKILL.md, but the broad file reading capability presents a potential vector for misuse if the agent is prompted to scan sensitive directories.