Skip to content

Reduce decorative formatting in skill and agent files #159

Description

@gringolito

What

Convert decorative, non-load-bearing markdown formatting in skill and agent files into compact equivalents. Specifically: replace tables whose column relationships are not meaningful (i.e. they are really labeled lists rendered as tables) with compact list form, and remove redundant --- horizontal-rule dividers and gratuitous bold/italic emphasis. All semantic structure — section headers, numbered step lists, and genuinely tabular tables where column relationships matter — must be preserved unchanged.

Why

Decorative markup adds byte and token overhead without contributing meaning the model needs to process. Reducing that overhead lowers the input-token footprint for every invocation of the affected skills and agents. This is the smallest, secondary lever in the broader token-reduction initiative (markup is a small fraction of body bytes; words dominate), so it should be prioritized last among siblings. Byte/line count (via wc) serves as the explicit, model-agnostic proxy for input-token reduction, by design.

In Scope

  • Skill and agent files across the repository
  • Convert non-load-bearing tables (labeled lists rendered as tables) to compact list form
  • Remove redundant --- horizontal-rule dividers
  • Remove gratuitous bold/italic emphasis that carries no semantic meaning

Out of Scope

  • Any genuinely tabular table where column relationships are load-bearing (e.g. lookup tables)
  • Any semantic structure: section headers, numbered step lists
  • Any workflow step, rule, gh command, or contract string — content must not change, only formatting

Acceptance Criteria

  • Every touched file is measurably smaller in bytes and/or lines, confirmed via wc before and after.
  • Every genuinely tabular table (load-bearing column relationships) is preserved as a table; only non-tabular labeled-list tables are converted. Confirmed by diff review.
  • No semantic structure is removed (headers, numbered steps) and no workflow step, rule, gh command, or contract string is altered. Confirmed by diff review.

INVEST Notes

Verification is diff-review-only — no skill-behavior test harness exists (initiative-wide decision). No fixed byte-reduction target; "measurably smaller" via wc is sufficient, by explicit decision.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    Status
    Todo

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions