Listicle Formatter

What it does

Takes a draft written as flowing paragraphs and reorganizes it into a numbered list format, one heading per item, consistent item length, and a short intro explaining the list's criteria, without inventing new items or padding the count to hit a round number. It flags when the source content doesn't naturally split into a clean list rather than forcing an awkward structure.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/listicle-formatter/ (or ~/.claude/skills/listicle-formatter/ for all projects)

GitHub Copilot (VS Code)

.github/skills/listicle-formatter/

OpenAI Codex

.codex/skills/listicle-formatter/

Cursor

.cursor/skills/listicle-formatter/ (or ~/.cursor/skills/listicle-formatter/ globally)

Compatibility

Any WordPress site. No special plugin required; uses the block editor's heading and list blocks, or numbered heading structure if the theme doesn't support ordered lists directly.

The complete SKILL.md for this skill:

---
name: listicle-formatter
description: Use when a user wants a draft restructured into a numbered list format, or asks to turn prose into a listicle. Triggers on "turn this into a listicle", "make this a numbered list post", or "reformat this as a top 10".
---

# Listicle Formatter

## When to use
A draft exists as flowing prose but covers a set of distinct items (tips, tools, mistakes, examples) that would scan better as a numbered list.

## Procedure
1. Read the draft and identify the distinct items it actually covers; count them honestly rather than padding to a round number like 10 or 15.
2. Write a short intro (2 to 3 sentences) stating the list's criteria, what qualifies an item for inclusion, before the numbered items begin.
3. Restructure each item under its own numbered heading, trimming or expanding surrounding prose so each entry is roughly consistent in length.
4. Order the items deliberately (by importance, difficulty, or a logical sequence), not in the order they happened to appear in the original draft, unless that order already made sense.
5. Flag if the source material doesn't cleanly split into a list, some arguments build on each other and resist chopping into standalone items rather than forcing a numbered structure onto it.

## Guardrails
- Do not invent additional items just to reach a rounder or more marketable number; an honest count of 7 beats a padded 10.
- Do not force content into list format when the source is fundamentally an argument that builds sequentially; say so instead of degrading the piece.