Skip to content

[Maintenance] Listing-budget watch: report the shared aggregate and drift #2023

Description

@kyle-sexton

Context

Self-maintenance pilot (Boris-talk digest menu #9, first of two report-only routines). The full-install listing surface drifts upward silently — every new skill and every description edit moves the aggregate, and the shared-budget overflow degrades auto-invocation for the least-invoked tail without any error. #2022 holds the current baseline (86,499 chars / 134 skills at 19a3f7b3) and the pending target decision; this routine keeps the number observed either way.

Proposed work

Each cycle (report-only — this routine never edits descriptions):

  • Run the pooled aggregate from a current main checkout: bash <skill-quality>/scripts/check-listing-budget.sh plugins/*/skills.
  • Record on this item: the aggregate, skill count, delta vs the previous cycle's recorded number, and the top-10 contributors.
  • If the aggregate moved >5% since the last cycle, or a single new skill enters the top-10, say so explicitly — that is the drift signal the routine exists to catch.
  • Advance the schedule row via /work-items:track recheck listing-budget-watch.

Acceptance criteria

References

Metadata

Field Value
Category general
Area unspecified
Ecosystem unspecified

Recurring

Cadence: quarterly
Triggers: none configured

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.recurringScheduled maintenance item reconciled against .github/recurring-schedule.json.

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions