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.
IFUsing KnowledgeGraphIndex.from_documents() with graph-specific keyword arguments (space_name, edge_types, rel_prop_names, tags) causes a TypeError because those arguments should be passed to NebulaGraphStore, not the index.
THENPass graph-specific configuration parameters to the NebulaGraphStore constructor, then create a StorageContext with that graph_store. Only pass storage_context, max_triplets_per_chunk, and include_embeddings to KnowledgeGraphIndex.from_documents(). Alternatively, consider migrating to PropertyGraphIndex as KnowledgeGraphIndex is deprecated.
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