mooqii/OpenPanels / agent-resources/preset-skills/publication-layout-default
publication-layout-default
VerifiedRestructure publication content for clear, scannable reading while preserving its meaning, voice, links, and images. Use for paragraphing, section hierarchy, lists, quotations, and restrained emphasis.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.1 KB |
SKILL.md
View on GitHub---
name: publication-layout-default
description: Restructure publication content for clear, scannable reading while preserving its meaning, voice, links, and images. Use for paragraphing, section hierarchy, lists, quotations, and restrained emphasis.
---
# Default Publication Layout
Improve the reading structure, not the author's argument. Work in three passes.
## 1. Diagnose
Read the complete title and document before editing. Identify:
- the opening, main ideas, topic shifts, examples, and conclusion;
- walls of text containing multiple complete ideas;
- paragraphs that mix unrelated topics or fragments that belong together;
- genuine section labels, parallel items, sequences, and quotations.
Do not mistake a change in formatting for a change in subject. Treat the
captured publication title as context and do not duplicate it in the body.
## 2. Restructure
Apply the smallest set of changes that makes the article easy to follow.
1. **Paragraphs come first.** Give each paragraph one main idea. Split a long
paragraph at clear topic shifts, examples, contrasts, consequences, or
transitions. Merge accidental fragments that form one idea. A document must
not remain a single wall of text when clear paragraph boundaries exist.
2. **Use headings for real sections.** Preserve existing headings and repair
inconsistent levels. In a longer article, you may add a short, neutral
heading where an unmistakable section boundary lacks one. Prefer words
already present in the article. Do not over-section short prose, promote
ordinary sentences, duplicate the publication title, or use a heading with
only one trivial paragraph beneath it.
3. **Use semantic structures only when earned.** Convert genuinely parallel
items or sequential steps to bullet or ordered lists. Use blockquotes only
for actual quoted passages. Never create a one-item list or turn ordinary
promotional prose into a quotation.
4. **Keep emphasis restrained.** Preserve meaningful bold and italic marks.
Add them only to a small number of key terms or conclusions when they improve
scanning; never emphasize whole paragraphs or decorate every section.
5. **Polish lightly.** Fix obvious punctuation, spacing, and paragraph-boundary
errors. Make only minimal transition or wording edits needed after
restructuring. Do not invent claims, examples, data, summaries, or calls to
action, and do not alter the author's position or voice.
## 3. Verify
Before returning the structured document, confirm all of the following:
- every paragraph has a coherent purpose and no clearly splittable wall of text
remains;
- headings and lists improve navigation rather than merely adding decoration;
- no substantive text was lost, duplicated, or reordered without a structural
reason;
- every link target and every image remains present, unchanged, and in the same
relative order, including all image attributes;
- the result follows the caller's required document and output contract.
Return only the structured document requested by the caller. Returning the
source unchanged is appropriate only when it already passes this quality gate.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |