@Brandon Hancock I loved using your task template from your 5 step crash course video. It enhanced the my current task layout. I reviewed the content of the task it created and it was very thorough and then watching the agent execute the task and then realize it's not what i wanted and put in corrective action it was great. I was able to spin up an OCR tool and enhance it within 30 minutes. Always love groups like this and videos like yours for collaboration!

🔥 Shoutout @Brandon Hancock for 👉🏿Ship Kit! I’m really impressed by the amount of value it provides. The templates alone could easily be worth the full price💯. At the pre-sell rate, it’s an incredible deal and a complete no-brainer. I’m excited for the full course release on September 20th. If you’re considering it, do yourself a favor and jump in now.

Hi, I'm working on creating a Cursor rule to ensure that generated code follows all our linting and coding standards. However, I'm still not able to get it to work the way I’d like. This would be a huge help to me and my team, as we currently spend a lot of time fixing mypy and other linting issues. Here's the Cursor rule I've written so far—I'd really appreciate any feedback or suggestions on how to improve it to boost my productivity: You are an expert in Python, FastAPI, and scalable API development. ## Git Usage - use the following prefix for commit messages followed by a colon and a space - "fix" for bug fixes - "feat" for new features - "docs" for documentation changes - "style" for formatting changes - "refactor" for code refactoring - "test" for adding missing tests - "chore" for chore tasks - when determining the commit message prefix, pick the most relevant prefix from the list above - use lower case for commit messages - the commit message should also include a list of the changes made in the commit after the summary line if the changes are not self explanatory ## Python/FastAPI Coding Standards **General:** - All code must be valid Python 3.10+ and compatible with [PEP8](https://peps.python.org/pep-0008/). - Use FastAPI best practices for API endpoints, dependency injection, and response models. - All new code and edits must pass `ruff` and `mypy` checks with the strict settings defined in `pyproject.toml`. - Use only absolute imports; relative imports are banned. - All functions, methods, and classes must have type annotations. - Docstrings are required for all public modules, classes, and functions (Google style preferred). - Line length must not exceed 88 characters. - Use f-strings for string formatting. - Avoid magic values; use named constants or enums. - Do not use `assert` in production code (allowed in tests). - Do not use lambda assignment. - Do not include TODOs without an author. **Linting & Typing:**

Hey guys! What if you could build a high-quality AI-generated newsletter in just 3 minutes? With CrewAI’s newest feature—Conversational Crews—now you can! In my latest video, I’ll show you how CrewAI Chat lets you interact with your agents in real time, refine their outputs, and create fully AI-driven content effortlessly. ​ To prove it, I built a Newsletter Crew that generates complete AI-powered newsletters in minutes—and I’m giving it to you for free! Here’s what you’ll learn: ✅ How to build an AI newsletter in under 3 minutes with CrewAI Chat. ✅ How to refine AI-generated content with real-time feedback & iterations. ✅ How CrewAI Chat works behind the scenes, so you can master the code. ​ Cheers,Brandon Hancock 🧑‍💻 P.S. Download My Best Newsletter Crew for FREE!​ This Crew is packed with top-tier AI content-generation techniques—grab it here: 👉 Download Free Crew

Has anyone created a custom tool but cannot use it in their crew? I am using flows and i created a custom tool, I imported that tool into the crew with the line from tools.<toolname> import <toolname> but i get the error everytime during kickoff that states ModuleNotFoundError: No module named 'tools'. To make sure it wasn't something i did in my custom tool I changed the from statement to use the default custom tool that was created with the flow and I still run into the same issue. Spinning my wheels at the moment so I thought I'd reach out and see if anyone else ran into this issue.