Moai Docs Linting

Name: Moai Docs Linting
Author: ajbcoding

Checked

ajbcoding·vlatest·writing

Moai Docs Linting automatically checks your Moai documentation for style and consistency, ensuring high-quality, maintainable guides.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add ajbcoding/claude-skill-eval --skill moai-docs-linting -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

ajbcoding

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 3 Oct 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned ajbcoding/claude-skill-eval at 887808517d.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 887808517d
Manifest: skills/moai-docs-linting/SKILL.md
Scanned: 3 files, 1,251 lines
Copies in repo: 3 — all of them scanned

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

The moai-docs-linting skill analyzes documentation text for common errors and inconsistencies, ensuring higher quality and readability. It checks for things like incorrect Markdown syntax, missing links, and adherence to specific style guidelines. The tool helps maintain a consistent voice and improves the overall user experience of technical documentation.

When to use it

Reviewing newly written documentation: Before publishing new content, run this skill to catch errors early.
Maintaining existing documentation: Regularly lint your docs to ensure they remain accurate and up-to-date.
Enforcing style guides: Use the skill to automatically check for compliance with established documentation standards.
Preparing documentation for release: Before a product launch or major update, use this skill as part of your final quality assurance process.

Key capabilities

Markdown syntax checking
Link validation (checking if links are broken)
Style guide enforcement (specific details not provided in source)

Example prompts

"Lint the following documentation: [paste documentation text here]"
"Check this Markdown file for errors and suggest improvements: [file path/name]"
"Can you review this doc for any style inconsistencies?"

Tips & gotchas

The skill's effectiveness depends on having a clearly defined style guide. Without specific rules, the linting will be less targeted and potentially generate more noise than signal.