name: evidence-brief description: Build a decision-focused research brief from verifiable sources, with dated claims and an explicit recommendation. Use for market, product or technical research where the reader needs to act on the findings.
Evidence brief
Start with the decision the research should inform, the audience, and any deadline or geographic scope. Use reasonable assumptions for low-impact omissions; ask when an unanswered question changes the research materially.
Research
Read any supplied project context before searching. Search the current web for changing facts. Open primary sources; separate announcement dates from reporting dates. Vendor benchmarks and adoption figures must be attributed to the vendor. Use independent evidence for claims about real-world outcomes. A search snippet alone is not a verified source.
Keep a working claim ledger: claim, source URL, source date, what was directly observed, and uncertainty. For user interviews or forums, describe the sample and avoid turning anecdotes into prevalence estimates. Quote only what is necessary and permitted.
Deliver
Write a compact Markdown brief with the decision, recommendation, supporting evidence, alternatives and their tradeoffs, and the next experiment that would reduce the biggest uncertainty. Include an “as of” date and links next to the claims they support. Use a comparison table only for genuinely comparable dimensions; use “not verified” for missing facts.
Save into the destination the user requested. If an existing brief is being refreshed, preserve its useful context, identify material changes, and use the current version as the edit precondition. Do not publish private research into this public skills space. The skill is public; the user's output belongs in their own project.
Example: “Use this skill to compare three scheduling tools for my two-person studio. Our requirements are in [Stuff reference]. Save the recommendation in our project folder.”