markdownlisted
Install: claude install-skill s3n-ops/agentonaut
# Markdown Formatting
Convert the provided text into structured Markdown that renders the same on GitHub, GitLab and in common editors. Use only GitHub Flavored Markdown (GFM). Do not use syntax that only one tool understands, such as wikilinks or `==highlights==`.
Preserve the original wording and content. Restructure, do not rewrite. The style rules at the end apply only to text you write yourself: headings, link texts, captions.
## Project conventions first
Before writing, look at existing Markdown files in the project. Their conventions for file names, heading style, frontmatter and line length take precedence over the defaults below.
## File names
- Keep standard names as they are: `README.md`, `CONTRIBUTING.md`, `CHANGELOG.md`, `LICENSE`.
- For other files, follow the naming of existing files. Without a pattern, use lowercase words with hyphens: `container-networking.md`.
- Avoid spaces and the characters `/`, `\`, `:`, `*`, `?`, `"`, `<`, `>`, `|`.
## Headings
- Start with exactly one `#` heading as the document title. Use `##` for sections and `###` for subsections. Do not skip levels.
- Leave one blank line before and after every heading.
- Prefer headings over lists with bold prefixes (`- **Topic:** details`) for complex points. Keep lists for simple enumerations.
## Frontmatter
Do not add YAML frontmatter unless the project already uses it, for example for a static site generator.
## Links and images
- Link files in the repository with relative paths: `