Md Review
borghei/Claude-Skills
Pre-publication quality gate for authored Markdown — heading structure, on-disk link resolution, readability, accessibility, terminology.
Reviews and lints Avalonia documentation pages against house style rules, content boundaries, anti-marketing standards, accessibility, and SEO.
Install Docs Style Lint
$ npx skills add AvaloniaUI/avalonia-docs --skill docs-style-lint -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AvaloniaUI/avalonia-docs docs-style-lint --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AvaloniaUI/avalonia-docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/docs-style-lint .claude/skills/docs-style-lint && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "docs-style-lint" agent skill from https://github.com/AvaloniaUI/avalonia-docs/tree/main/.claude/skills/docs-style-lint into .claude/skills/docs-style-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style-lint", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AvaloniaUI/avalonia-docs/tree/main/.claude/skills/docs-style-lintType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AvaloniaUI/avalonia-docs --skill docs-style-lint -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AvaloniaUI/avalonia-docs docs-style-lint --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AvaloniaUI/avalonia-docs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/docs-style-lint .agents/skills/docs-style-lint && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docs-style-lint" agent skill from https://github.com/AvaloniaUI/avalonia-docs/tree/main/.claude/skills/docs-style-lint into .agents/skills/docs-style-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style-lint", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AvaloniaUI/avalonia-docs --skill docs-style-lint -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AvaloniaUI/avalonia-docs docs-style-lint --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AvaloniaUI/avalonia-docs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/docs-style-lint .cursor/skills/docs-style-lint && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "docs-style-lint" agent skill from https://github.com/AvaloniaUI/avalonia-docs/tree/main/.claude/skills/docs-style-lint into .cursor/skills/docs-style-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style-lint", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AvaloniaUI/avalonia-docs.git --path .claude/skills/docs-style-lint--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AvaloniaUI/avalonia-docs --skill docs-style-lint -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AvaloniaUI/avalonia-docs docs-style-lint --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AvaloniaUI/avalonia-docs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/docs-style-lint .gemini/skills/docs-style-lint && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "docs-style-lint" agent skill from https://github.com/AvaloniaUI/avalonia-docs/tree/main/.claude/skills/docs-style-lint into .gemini/skills/docs-style-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style-lint", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AvaloniaUI/avalonia-docs docs-style-lintInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AvaloniaUI/avalonia-docs --skill docs-style-lint -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AvaloniaUI/avalonia-docs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/docs-style-lint .github/skills/docs-style-lint && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "docs-style-lint" agent skill from https://github.com/AvaloniaUI/avalonia-docs/tree/main/.claude/skills/docs-style-lint into .github/skills/docs-style-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style-lint", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AvaloniaUI/avalonia-docs --skill docs-style-lint -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AvaloniaUI/avalonia-docs docs-style-lint --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AvaloniaUI/avalonia-docs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/docs-style-lint .opencode/skills/docs-style-lint && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "docs-style-lint" agent skill from https://github.com/AvaloniaUI/avalonia-docs/tree/main/.claude/skills/docs-style-lint into .opencode/skills/docs-style-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style-lint", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
docs-style-lint- GitHub stars
- 166
- Token cost
- ~4.6k tokens
- SKILL.md length
- 1,988 words
- Files
- 5 (incl. references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- None found
At a glance
Reviews and lints Avalonia documentation pages against house style rules, content boundaries, anti-marketing standards, accessibility, and SEO.
- Works in 10 steps: Identify page type → Run structural checks → Run anti-marketing checks → …
- Writing documentation to ensure consistency with established patterns
- SKILL.md covers Diataxis as invisible discipline, Technical accuracy…, When to use and Inputs, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Docs Style Lint is an agent skill from AvaloniaUI/avalonia-docs. Reviews and lints Avalonia documentation pages against house style rules, content boundaries, anti-marketing standards, accessibility, and SEO. Use when reviewing, editing, or writing documentation to ensure consistency with established patterns. Checks structure, voice, terminology, formatting, linking, tone, Diataxis compliance, image accessibility, meta descriptions, and jargon simplification.
Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/house-rules.yaml`, `references/linter-checklist.md` and `references/page-templates.yaml`).
It sits in Development, covering Linting and formatting, Plain language and style rules and On-page SEO. It works with Avalonia.
When your agent uses it
- Writing documentation to ensure consistency with established patterns
- Tasks that involve Linting and formatting
- Tasks that involve Plain language and style rules
Example prompts
- “Use the docs-style-lint skill to review and lints Avalonia documentation pages against house style rules, content boundaries, anti-marketing…”
- “/docs-style-lint”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
- Identify page type
- Run structural checks
- Run anti-marketing checks
- Run terminology checks
- Validate API references (ACCU-003)
- Run content boundary checks
- Run template compliance
- Check banned phrases
- Run inclusive language checks
- Generate report
What it can do on your machine
Read from SKILL.md and the folder at commit 0d91508. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.avaloniaui.net
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Docs Style Lint loads about 4.6k tokens when it runs, and up to ~18k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 1,988 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,988 words (~4,605 tokens).
“Review documentation pages against Avalonia's house style rules derived from corpus analysis of professional .NET framework documentation, adapted for Avalonia's Docusaurus-based site.”
- name
- docs-style-lint
Files
SKILL.md and 4 other files (references) in .claude/skills/docs-style-lint of AvaloniaUI/avalonia-docs.
- SKILL.md
- references/house-rules.yaml
- references/linter-checklist.md
- references/page-templates.yaml
- references/terminology-map.yaml
Open the folder on GitHubat commit 0d91508
Compare with similar skills
Docs Style Lint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Docs Style Lint this skillAvaloniaUI/avalonia-docs | 166 | — | ~4.6k | Automated safety check: Pass | None | |
| Md Reviewborghei/Claude-Skills | 886 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Commenting C And Pythonmicrosoft/bocpy | 201 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Code Review And QualityHangYu8123/mini-harness | 199 | — | ~1.8k | Automated safety check: Pass | None | |
| Code Quality Reviewrsmdt/the-startup | 557 | — | ~525 | Automated safety check: Pass | MIT | |
| Code Layout Evaluation Principleskitchen-engineer42/pdf2skills | 134 | — | ~383 | Automated safety check: Pass | None |
Similar skills
- Official
Commenting C And Python
microsoft/bocpy
Follow bocpy commenting and documentation conventions. An agent skill from microsoft/bocpy.
Code Review And Quality
HangYu8123/mini-harness
Multi-axis, review-only code review of a diff across six axes — request achievement, correctness, readability/simplicity, architecture, security, and performance — with severity-labelled findings.
Code Quality Review
rsmdt/the-startup
Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions.
Code Layout Evaluation Principles
kitchen-engineer42/pdf2skills
Evaluate code layout quality based on accuracy, consistency, readability, and maintainability rather than aesthetics.
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
More from AvaloniaUI/avalonia-docs
Docusaurus Styling
AvaloniaUI/avalonia-docs
Style Docusaurus sites to match Avalonia Customer Portal theme using TailwindCSS, CSS variables, and component swizzling.
API Link Builder
AvaloniaUI/avalonia-docs
Scans the /docs directory for opportunities to cross-link with API reference documentation in /api, and vice versa.
Discussion Gap Finder
AvaloniaUI/avalonia-docs
Analyzes GitHub discussion links to identify documentation gaps.
Tailwind To Infima
AvaloniaUI/avalonia-docs
You are an expert in Docusaurus theming and the Infima CSS framework.
Related
Works with
Categories
Questions about Docs Style Lint
What does Docs Style Lint do?
Reviews and lints Avalonia documentation pages against house style rules, content boundaries, anti-marketing standards, accessibility, and SEO. Docs Style Lint is an agent skill from AvaloniaUI/avalonia-docs. Reviews and lints Avalonia documentation pages against house style rules, content boundaries, anti-marketing standards, accessibility, and SEO.
When should I use Docs Style Lint?
Docs Style Lint fits situations like: writing documentation to ensure consistency with established patterns; tasks that involve Linting and formatting; tasks that involve Plain language and style rules.
How do I install Docs Style Lint in Claude Code?
Run `npx skills add AvaloniaUI/avalonia-docs --skill docs-style-lint -a claude-code`. Or copy the skill folder (.claude/skills/docs-style-lint in AvaloniaUI/avalonia-docs) into .claude/skills/docs-style-lint in your project. Claude Code loads it when a task matches its description.
How do I install Docs Style Lint in Codex?
Run `npx skills add AvaloniaUI/avalonia-docs --skill docs-style-lint -a codex`. Or copy the skill folder (.claude/skills/docs-style-lint in AvaloniaUI/avalonia-docs) into .agents/skills/docs-style-lint in your project. Codex loads it when a task matches its description.
Can I use Docs Style Lint in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AvaloniaUI/avalonia-docs --skill docs-style-lint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-style-lint, .gemini/skills/docs-style-lint, .github/skills/docs-style-lint and .opencode/skills/docs-style-lint in your project.
What does Docs Style Lint need to run?
SKILL.md names no scripts, command-line tools or credentials: Docs Style Lint is instructions for the agent only.
Does Docs Style Lint access the network?
SKILL.md names 1 domain. As links in the text: docs.avaloniaui.net. This is read from the text; nothing was executed.
Is Docs Style Lint safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Docs Style Lint use?
No licence was found for Docs Style Lint or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Docs Style Lint use?
About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.
What are the alternatives to Docs Style Lint?
Skills that share tags, products or a category with Docs Style Lint: Md Review (borghei/Claude-Skills, 886 stars), Commenting C And Python (microsoft/bocpy, 201 stars), Code Review And Quality (HangYu8123/mini-harness, 199 stars) and Code Quality Review (rsmdt/the-startup, 557 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docs Style Lint?
AvaloniaUI (a GitHub organization) maintains it in AvaloniaUI/avalonia-docs, which has 166 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.
Source: AvaloniaUI/avalonia-docs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.