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.
IFWhen a task's LLM output continuously fails conversion to a Pydantic model (e.g., due to malformed JSON), the error recovery mechanism crashes with 'NoneType' object has no attribute 'function_calling_llm', providing no clear user guidance.
THENIn crewAI's converter.py, modify the `to_pydantic` method to pass the agent object (instead of None) to `handle_partial_json`. Specifically, change line 42 from `result = handle_partial_json(response, self.model, False, None)` to `result = handle_partial_json(response, self.model, False, self.agent)`. Ensure that the `Converter` class stores and forwards the agent reference so error recovery can access `agent.function_calling_llm` for retry with 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