Individual skill

proxmox-writing-style

Unofficial skill for the Proxmox Technical Writing Style Guide. Use it to write, edit, or review Proxmox documentation: Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway admin guides, wiki pages, how-to guides, procedures, release notes, and UI text. Also use it when the user asks for the Proxmox style, the Proxmox wiki style, or a style review of Proxmox text. It covers voice, mood, sentence length, procedures, headings, punctuation, product names, terms, abbreviations, and examples.

plugins/msoltanov/Proxmox-Technical-Writing-Style-Skill/skills/proxmox-writing-style/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Proxmox Writing Style

Use this skill for Proxmox technical documentation, how-to guides, release notes, procedures, and user-facing technical text.

For before and after rewrites of each rule, read [references/examples.md](references/examples.md).

When you review text, report each problem with the rule, the problem text, and a correct rewrite.

## Workflow

1. Identify whether the text describes a system or gives instructions.
2. Put the important information near the start of each sentence.
3. Use US English spelling.
4. Write short, clear sentences.