Never accept unverified claims about tools, hardware, or projects at face value

When the user asks about adopting a GitHub project, comparing hardware, or evaluating tool definitions, they expect the assistant to actively research and verify real information (e.g., fetch the repo, inspect actual code/specs) rather than rely on assumptions or general knowledge. The user frequently poses evaluative questions ('would this be useful?', 'is this worth it?') that require concrete investigation before giving an opinion. Always begin by investigating the referenced resource (repo, hardware specs, tool schema) directly, then provide an evidence-based assessment tailored to the user's workflow or context.