evosearch vs memory-policy
evosearch and memory-policy are both search and web skills. memory-policy scores higher (82 vs 80 out of 100). memory-policy has more GitHub stars (5.0k), and evosearch was updated more recently (7 days ago). The table compares them side by side.
| evosearch | memory-policy | |
|---|---|---|
| Score | 80 / 100 | 82 / 100 |
| What it does | Run the CaP Fix Loop + Evolutionary Search experiment on a user-supplied list of low-performing benchmark tasks: iterative K=8 candidate search on development seeds 51–65, validation selection, and final held-out evaluation on seeds 1–50. | Use when deciding whether to search Zep memory for user preferences. |
| Publisher | Community: NVlabs | Community: getzep |
| Grades | Maintenance A, Licence A, Quality A | Maintenance A, Licence A, Quality A |
| npm downloads a week | Not on npm | Not on npm |
| Runs | Skill | Skill |
| Works with | Claude Code, Claude apps | Claude Code, Claude apps |
| GitHub stars | 719 | 4,966 |
| Last commit | 16 Oct 2026 | 14 Oct 2026 |
| Licence | Apache-2.0 | Apache-2.0 |
| Listed since | 20 Oct 2026 | 19 Oct 2026 |
| Install evosearch | Install memory-policy |
Questions
Is evosearch or memory-policy more popular?
memory-policy has more GitHub stars: 4,966.
Can I use evosearch and memory-policy together?
Yes. AI assistants can load several skills at once. Install both and the assistant picks the right one for each task.