lilmgenius/paperthin

reorder

Realign a listing whose order has gone arbitrary — a list, table, catalog, sections, an enum — into a logical sequence under one stated principle.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/lilmgenius/paperthin --skill reorder

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Put a listing back into an order that carries meaning, moving items only.

Goal

A listing's order is information: kin sit together, and the sequence follows one axis a reader can feel. Order drifts — items get appended where they were written, not where they belong — until the sequence tells the reader nothing. reorder realigns the set under a single, nameable principle so the order reads as intentional again. It is fast and single-purpose: it moves items, and changes nothing else.

Workflow

  1. Pin the listing and its items — the ordered set in focus.
  2. Name the principle that makes the order carry the most meaning: workflow or lifecycle sequence, dependency, grouping by kind, severity, frequency, or plain alphabetical. If the set already has a latent order, surface and finish it rather than imposing a new one.
  3. Cluster kin adjacent, then sequence the clusters by that one principle.
  4. Move items into the new order in place. Reword nothing; add and remove nothing.
  5. If the same set is mirrored elsewhere — a translated copy, a second surface — apply the identical order to each.

Rules

  • Reorder only. Never reword, add, remove, split, or merge an item; those are other reflexes.
  • One principle, and a reader can name it. Do not blend incompatible sorts into one listing.
  • Respect a deliberate order. If the current sequence already encodes a real principle, complete and tidy it rather than replacing it; surface the call when it is unclear.
  • Keep mirrored copies in lockstep — the same set on different surfaces gets the same order.
  • Mutate with edit-safety: assert each item exists before moving it (report a MISS, never a silent drop), edit unicode-safe, and script a large structural move rather than sweeping by hand.

Verification

  1. A reader can name the ordering principle from the result alone.
  2. Every item that was there is still there — only positions changed; nothing reworded, added, or removed.
  3. Kin are adjacent and the sequence follows the one principle end to end.
  4. Every mirrored copy of the set carries the identical order.

Related by task

from this repository

More skills

All skills
lilmgenius
Community

re0-order

Move items only, reword nothing; realign a listing whose order has gone arbitrary (a list, table, catalog, sections, an enum) into a logical sequence under one stated principle. Nothing is added or removed. Use when the user names a listing, or a scope holding one, whose order no longer helps a reader follow the set, or when a pipeline the user invoked passes that scope on. Acts only inside that scope.

1h installs
5
GitHub stars
1.5K
Updated
Nov 15
lilmgenius
Community

readback

Verify the model's understanding of a user's instruction before spending non-trivial work. Use when a request is long, bundled, high-stakes, hard to undo, or has ambiguous scope or referents such as this, that, it, the other one, whatever is cleaner, or whichever order makes sense. Restate internally, cross-check against available context, proceed silently when resolved, and surface only a genuine surviving fork.

1h installs
5
GitHub stars
1.5K
Updated
Nov 15
lilmgenius
Community

whychk

Right after you pick an option, have a fresh outsider find the sharpest gap in the choice, then explain that gap in your own words, one gap at a time.

1h installs
5
GitHub stars
1.5K
Updated
Nov 15
lilmgenius
Community

aim

When data lands with a thin ask (files, a repo, a paste, a chat scrollback), read it and propose what the user is trying to do with it for them to confirm. Use the moment material arrives without a fully-formed ask, or when the ask reads thinner than the data suggests.

1h installs
4
GitHub stars
1.5K
Updated
Nov 15