What problem does it solve? Evaluating a technology from marketing pages and READMEs produces decisions built on claims rather than evidence. This Skill structures the technology domain of a research plan so every finding comes from primary documentation, issue trackers, incident history, and verbatim licence text. ## Core Features & Use Cases - Evidence-based capability review: Documents what a technology actually does and explicitly does not do, at a named version, with dated limits and quotas. - Cost, failure, and licence analysis: Identifies the pricing dimension that drives the bill, published failure modes with recovery paths, and quotes licence and data terms verbatim. - Use Case: Before adopting a managed queue service, dispatch this Skill to return its rate limits at the current version, its incident history, the cost driver at your message volume, and the exact data-residency terms — filed as a research corpus entry. ## Quick Start Ask the agent to research the technology domain for a specific technology you are evaluating, naming the version and your expected usage shape.