Skip to content

hani-q/qstack / skills/qstack-be-concise

qstack-be-concise

Verified

Rewrite the immediately previous assistant answer in plain, non-technical language as a short bulleted list, or a numbered list when the content is ordered or counted. Use when the user invokes `/qstack-be-concise`, optionally with a target such as `/qstack-be-concise 4`, or asks to make the last answer shorter and simpler.

/qstack-be-concise

Rewrite the immediately previous assistant answer. Output only the rewrite.

Choose the length

  • If the invocation includes a positive whole number N, use N or N + 1 short lines. For example, /qstack-be-concise 4 produces about 4–5 lines.
  • Otherwise, count the non-empty lines in the previous answer and use this guide:
    • 1–5 lines: rewrite in 1–2 lines.
    • 6–12 lines: rewrite in 2–3 lines.
    • 13–24 lines: rewrite in 3–5 lines.
    • 25–49 lines: rewrite in 5–7 lines.
    • 50 or more lines: rewrite in 7–10 lines.
  • Treat the ranges as ceilings, not quotas. Use fewer lines when they are enough.
  • Exceed a requested limit only when needed to avoid an unsafe or seriously misleading answer.

Choose the list shape

  • Always answer as a list. Never write the rewrite as a paragraph.
  • One bullet counts as one line against the length guide above.
  • Default to a bulleted list with -.
  • Use a numbered list only when the content is genuinely ordered or counted: steps that happen in sequence, a ranking, or items the previous answer already numbered or referred to by number.
  • When the order of the items does not matter, use bullets even if there are several of them.
  • Do not mix the two shapes in one rewrite, and do not nest sub-lists.

Rewrite rules

  • Preserve the important result, decisions, warnings, and next action.
  • Use everyday words a non-technical reader can understand.
  • Remove jargon, implementation details, file paths, command names, and process narration unless the user must know them to act.
  • Translate any unavoidable technical term immediately into plain language.
  • Do not add new facts, repeat the work, call tools, or change the meaning.
  • Keep each item to one short sentence. Avoid headings, tables, code blocks, preambles, apologies, and commentary about shortening the answer.
  • If there is no previous substantive assistant answer, say so in one bullet.
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall