agentleFS
NetcrackerNetcracker/qubership-ai-agent-telemetry/.agents/skills/markdown-line-length-120/SKILL.md

markdown-line-length-120

Skill1 starsChanged 28 days agoApache-2.0View on GitHub

Apply Markdown drafting rules an autofixer cannot fix — wrap body lines at 120 chars (MD013), one H1 per document (MD025), named links instead of bare URLs (MD034), language tag on every fenced code block (MD040). Use when editing `*.md` in a repository that pins markdownlint `MD013.line_length` to 120. Do not wrap text for GitHub, GitLab, or JIRA; they reflow it automatically.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When preparing text for GitHub, Gitlab or JIRA (PR or issue description, comment, discussion), don't hard-wrap.

    line 21
  2. Distinctive:

    Keep each paragraph and list item on one line.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Markdown drafting rules an autofixer cannot fix

Build every .md file with these four rules in mind from the first draft. They are not autofixable, so pasting in a long paragraph and rewrapping it afterwards is wasted work. Run markdownlint-cli2 --fix before commit for the rest (MD022, MD032, MD060, MD029, MD026, MD047, ...).

Wrap body lines at 120 characters (MD013)

Plan the sentence around the wrap, not the other way round. Break at word boundaries; never split `inline code` or a [link](url) span across lines. List-item continuations indent by two spaces to line up with the bullet content. Exempt from the limit: YAML frontmatter, fenced code blocks, and pipe tables — do not reformat them to fit 120.

When preparing text for GitHub, Gitlab or JIRA (PR or issue description, comment, discussion), don't hard-wrap. Keep each paragraph and list item on one line; GitHub, Gitlab, JIRA re-flow it.

One H1 per document (MD025)

The first heading is the title (#). All later sections are ## or deeper. A section break never gets promoted back to #, even when the document is long.

Named links, not bare URLs (MD034)

Write [the SDK reference](https://example.com/sdk), not https://example.com/sdk on its own. When the URL really is the link text (citations, release notes), wrap it in angle brackets: <https://example.com/sdk>.

Language tag on every fenced code block (MD040)

```yaml, ```bash, ```text, ```diff — always pick one. Use text for plain output, directory listings, ASCII diagrams, or fixtures with no syntax to highlight.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.