We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFExisting AutoGen user wants to migrate to the new Microsoft Agent Framework (MAF) for enterprise support.
THENFollow the official migration guide at https://learn.microsoft.com/en-us/agent-framework/migration-guide/from-autogen/. MAF is the enterprise-ready successor with multi-provider model support and cross-runtime interoperability.
IFYou are currently using the AgentChat packages and need to migrate to the official AutoGen packages.
THENReplace the AgentChat.Core package reference with AutoGen. If using AgentChat.DotnetInteractive, replace it with AutoGen.DotnetInteractive. Add a reference to AutoGen.SourceGenerator for type-safe function calls. Then fix build errors; the API mapping is straightforward.
IFUser is currently using OpenClaw and wants to migrate to Hermes Agent with all settings, memories, and skills.
THENRun the migration command `hermes claw migrate`. Use `--dry-run` to preview, `--preset user-data` to exclude secrets, or `--overwrite` to resolve conflicts. The migration automatically detects `~/.openclaw` and imports persona, memories, skills, command allowlist, messaging settings, API keys, and workspace instructions.
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site