AgentStack
SKILL verified MIT Self-run

Sembr Reformat

skill-sembr-skills-sembr-reformat · by sembr

Reformat prose using Semantic Line Breaks (SemBr) from https://sembr.org while preserving rendered output and meaning. Use when asked to reflow plain text or compatible markup (Markdown, AsciiDoc, reStructuredText, LaTeX, Org, MediaWiki) into semantic one-thought-per-line formatting, or when improving prose diffs and editorial readability.

No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-sembr-skills-sembr-reformat

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Sembr Reformat? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Reformat With SemBr

Apply Semantic Line Breaks to prose without changing what readers see. Preserve wording, punctuation, and intent.

Reformat Workflow

  1. Identify prose regions that support soft-wrapped lines.
  2. Skip regions where line breaks are syntactically significant:
  • fenced code blocks and indented code blocks
  • tables
  • YAML frontmatter
  • URLs or markup tokens that must stay contiguous
  1. Rewrite only line wrapping, not content.
  2. Keep paragraphs and list structures intact.
  3. Return full rewritten text unless asked for a targeted excerpt.

SemBr Rules

Apply these rules in order:

  1. Break after every sentence ending in ., !, or ?.
  2. Prefer a break after independent clauses ending in ,, ;, :, or .
  3. Optionally break after dependent clauses when it clarifies structure.
  4. Insert a break before an enumerated or itemized list.
  5. Optionally add breaks between list items to group related items.
  6. Never break inside a hyphenated word.
  7. Allow breaks around hyperlinks and before inline markup when helpful.
  8. Target 80 columns when possible; allow longer lines for URLs, code spans, or unavoidable markup.

Quality Checks

Before returning output, verify:

  • Rendering-equivalence: no hard-break syntax added accidentally.
  • Meaning-equivalence: no word changes or punctuation edits.
  • Structure-equivalence: headings, lists, and block boundaries unchanged.
  • Diff-friendliness: edits are mostly line-wrap changes.

Output Style

Use minimal explanation. Return reformatted text directly. If any segment cannot be safely reformatted, leave it unchanged and add a one-line note.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.