There is so much good stuff that gets posted here, and I've tried various ways of keeping up with it: The forums' bookmarking tool, Safari's bookmarks, notes files. All of them fail, primarily because it's still too hard to find what I want. And it's work to remember to add the items to another app, or to keep my bookmarks sorted, etc.
This morning I had the thought that a "best macros collector" macro could be just what I wanted to make it easier to save, find, and use all the macros posted here. So I whipped up a rough proof of concept, and so far, I like how it works. Here's the macro group, which currently only works in Safari.
__Best Macros Collection Macros.kmmacros (40 KB)
How it works: Hover over any macro link—like the one above—and press Control-C. The macro will save the download link, macro title, and page URL, then present a pop-up categorizer:
Select an existing category or add a new one, then press Enter, and the macro's details are saved to a SQLITE3 database. Once you have at least one item in your collection, while in Safari press Shift-Control-C to open the collection browser:
Select a macro in the list, and you get its details dialog:
Open Topic will open the thread with the macro, usually on or close to the post where the macro was poste; Download will download the macro.
This is a very rough concept—the final version wouldn't use dialogs, but HTML prompts with tables, like my Recent Macro Browser Plus macro, so you could sort and act on the entire database of entries at once. And you could search the database, of course, using the description or title, etc. And there'd be ways to delete, edit, etc. the database entries, and a lot more.
But before I get too far into it, is there general interest in a tool like this? If so, I'll develop with sharing in mind. If not, I'll just do what I need to make it useful to myself, which will require a fair bit less effort—I don't mind doing the work, but if there's no interest, I won't bother :).
-rob.
), it goes on to mention possible dangers before documenting its recovery API. 
I suppose the key question is: do you want to use KM not only as a library of your macros but also as a database of macros that you might want to use one day? I can see that for many it would make sense to keep macros and information about available macros in one place. To me, that's extending KM's role, in a proprietary way, to handle a different kind of (meta)data.