What makes markdown-formatting notable?

1.7K downloads. Trust evidence available

How should markdown-formatting be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

markdown-formatting

Enforces markdown line-wrap and structure rules for clean git diffs Skill: markdown-formatting Owner: athola Summary: Enforces markdown line-wrap and structure rules for clean git diffs Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:14:50.645Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:35:54.012Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:52:35.744Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:01:32.157Z | user Release v1.9.14 v1.9.13 | 2026-06-27T16:19:55.208

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.7k

Updated

Oct 10, 2026

Version

1.9.19

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.7K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.7K downloadsadoption · observed Oct 10, 2026
Latest release: 1.9.19release · observed Aug 26, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-leyline-markdown-formatting

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-leyline-markdown-formatting/snapshot"

Documentation

CLAWHUB

116,597 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: markdown-formatting
description: Enforces markdown line-wrap and structure rules for clean git diffs
version: 1.9.8
triggers:
- markdown
- formatting
- documentation
- line-wrapping
- style
- writing or editing any committed markdown documentation or skill file
metadata: {"openclaw": {"homepage": "https://github.com/athola/claude-night-market/tree/master/plugins/leyline", "emoji": "\ud83e\udd9e"}}
source: claude-night-market
source_plugin: leyline
---

> **Night Market Skill** — ported from [claude-night-market/leyline](https://github.com/athola/claude-night-market/tree/master/plugins/leyline). For the full experience with agents, hooks, and commands, install the Claude Code plugin.

# Markdown Formatting Conventions

## When To Use

- Writing or editing any markdown documentation
- Reviewing prose for line-wrapping compliance
- Generating markdown from plugins (scribe, sanctum, etc.)

## When NOT To Use

- Editing code blocks, tables, or frontmatter (these have
their own formatting rules)
- Quick scratch notes that will not be committed

These conventions apply to all markdown documentation generated
or modified by any plugin. The goal: produce prose that creates
clean, reviewable git diffs and reads well on mobile devices.

## Quick Reference

When writing or editing markdown prose:

1. **Wrap prose at 80 chars** using hybrid wrapping (prefer
sentence/clause boundaries over arbitrary word breaks)
2. **Blank line before and after every heading**
3. **ATX headings only** (`# Heading`, never setext underlines)
4. **Blank line before every list**
5. **Reference-style links** when inline links push lines
beyond 80 chars

## What to Wrap

Wrap these content types at 80 characters:

- Paragraphs (flowing prose text)
- Blockquote text (the content after `>`)
- List item descriptions (text after `- ` or `1. `)
- Descriptions in definition lists

## What NOT to Wrap

Never wrap or reflow these content types:

- **Tables**: pipe-delimited rows stay on one line
- **Code blocks**: fenced (` ``` `) or indented content
- **Headings**: lines starting with `#`
- **Frontmatter**: YAML/TOML between `---` or `+++`
- **HTML blocks**: raw HTML elements
- **Link definitions**: `[id]: url` reference lines
- **Image references**: `![alt](url)` on their own line
- **Single-line list items**: short bullets that fit on one line

## Wrapping Algorithm (Summary)

For each prose paragraph:

1. If a sentence fits within 80 chars, keep it on one line
2. If a sentence exceeds 80 chars, break at the nearest
**sentence boundary** (`. ` `! ` `? `) before column 80
3. If no sentence boundary, break at the nearest **clause
boundary** (`, ` `; ` `: `) before column 80
4. If no clause boundary, break before a **conjunction**
(`and ` `but ` `or `) before column 80
5. If none of the above, break at the last **word boundary**
before column 80
6. Never break inside backtick spans, link text, or URLs

See `modules/wrapping-rules.md` for the full a

_meta.json

{
  "ownerId": "kn7d107jg9jv602h9ytsegydq184a42s",
  "slug": "nm-leyline-markdown-formatting",
  "version": "1.9.19",
  "publishedAt": 1787750090645
}

modules/wrapping-rules.md

---
module: wrapping-rules
category: cross-plugin-patterns
dependencies: []
estimated_tokens: 600
---

# Hybrid Line Wrapping Rules

Wrap prose text at 80 characters per line, preferring semantic
boundaries (sentences, clauses) over arbitrary word breaks.
This produces clean git diffs while keeping lines readable.

## The Algorithm

When writing a prose paragraph, apply these rules in order:

### Priority 1: Sentence Boundaries

If a sentence (ending with `.` `!` or `?` followed by a space)
fits within 80 characters, keep it on one line.

```markdown
BEFORE (single long line):
Install the plugin with npm. Configure it in your settings file. Restart the editor to activate.

AFTER (one sentence per line, each under 80 chars):
Install the plugin with npm.
Configure it in your settings file.
Restart the editor to activate.
```

### Priority 2: Clause Boundaries

If a sentence exceeds 80 characters, break after the nearest
comma, semicolon, or colon before column 80.

```markdown
BEFORE (one 95-char sentence):
When the configuration file is missing, the system falls back to sensible defaults for all settings.

AFTER (break after comma at position 43):
When the configuration file is missing,
the system falls back to sensible defaults
for all settings.
```

### Priority 3: Conjunctions

If no clause boundary exists before column 80, break before
a conjunction: `and`, `but`, `or`, `nor`, `yet`, `so`.

```markdown
BEFORE:
The parser reads the input file and transforms each node into an output token.

AFTER:
The parser reads the input file
and transforms each node into an output token.
```

### Priority 4: Word Boundaries

If none of the above apply, break at the last word boundary
before column 80.

```markdown
BEFORE:
The implementation requires understanding the underlying architecture thoroughly.

AFTER:
The implementation requires understanding the underlying
architecture thoroughly.
```

## Never Break Inside

These constructs must stay intact on a single line:

- **Inline code**: `` `some_function_name` `` stays together
- **Link text**: `[link text]` stays on one line
- **Link URLs**: `(https://example.com/path)` stays on one line
- **Image syntax**: `![alt](url)` stays together
- **Bold/italic spans**: `**bold text**` stays together

If keeping these intact pushes a line beyond 80 chars,
that is acceptable. Do not break the construct.

## Exempt Content Types

Do NOT apply wrapping to any of these:

| Content Type | How to Identify |
|-------------|-----------------|
| Tables | Lines containing `\|` pipe characters |
| Code blocks | Between ` ``` ` fences or indented 4+ spaces |
| Headings | Lines starting with `#` |
| Frontmatter | Between `---` or `+++` delimiters at file start |
| HTML blocks | Lines starting with `<` HTML tags |
| Link defs | Lines matching `[id]: url` pattern |
| Image lines | Lines that are only `![alt](url)` |

## Blockquotes

For blockquote content, wrap the text inside the quote at 78
characters (80 minus the `> ` prefix)

skill-card.md

## Description:

Enforces markdown line-wrap and structure rules for clean git diffs.

This skill is ready for commercial/non-commercial use.

## Publisher:

[athola](https://clawhub.ai/user/athola)

### License/Terms of Use:

MIT-0

## Use Case:

Developers, documentation authors, and agents use this skill to apply consistent Markdown wrapping and structural conventions while writing or reviewing committed documentation.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill has broad documentation and formatting triggers, so it may activate during sensitive documentation work.

Mitigation: Review formatting-only changes before accepting them, especially in documents where line wrapping could affect readability, citations, or review history.

Risk: The skill instructs agents not to reflow code blocks, tables, frontmatter, HTML blocks, links, and image references, but formatting edits can still accidentally affect exempt content.

Mitigation: Inspect diffs for protected Markdown constructs and reject changes that alter code, table rows, metadata, raw HTML, link definitions, or standalone image references.

## Reference(s):

- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-leyline-markdown-formatting)
- [Publisher profile](https://clawhub.ai/user/athola)
- [OpenClaw homepage metadata](https://github.com/athola/claude-night-market/tree/master/plugins/leyline)
- [Google Markdown style guide](https://google.github.io/styleguide/docguide/style.html)
- [Hybrid line wrapping rules](modules/wrapping-rules.md)

## Skill Output:

**Output Type(s):** [Guidance, Markdown, Text]

**Output Format:** [Markdown prose guidance and formatting conventions]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Produces formatting recommendations for prose, headings, lists, links, and wrapping behavior; no tool calls or generated files are required by the skill.]

## Skill Version(s):

1.9.19 (source: server release evidence; artifact frontmatter says 1.9.8)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 11h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.