CtrlK
BlogDocsLog inGet started
Tessl Logo

market-research-digest

Synthesize Drive files, Granola meeting notes, and web signals into a weekly Markdown research summary with Trends, Competitors, Ideas, and Risks sections. Use when a PM wants to consolidate scattered research into a single weekly digest.

68

Quality

61%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./product-skills/skills/market-research-digest/SKILL.md
SKILL.md
Quality
Evals
Security

Market Research Digest

Turn scattered research into a structured weekly summary — trends, competitor signals, ideas, and risks in one place.

You have files in Google Drive, meeting notes in Granola, and signals scattered across the web. This skill reads everything from the past week, synthesizes it into four clean sections, and saves a dated Markdown file back to Drive — so nothing gets lost and every stakeholder stays informed.


Prompt Template

/schedule Every week, read everything in my Google Drive {{INPUT_FOLDER}} folder (all files and
any links inside them), query my Granola meeting notes from the last 30 days, and search the web
for competitor signals, product trends, feature requests, and risks relevant to {{PRODUCT_DESCRIPTION}}.

Synthesize all of it into a Markdown summary with four sections:

## Trends
What is shifting in the market, user behavior, or the competitive landscape? Lead with the most
significant movement. Each item should be a 2–3 sentence observation with a source citation.

## Competitors
What are competitors shipping, changing, or saying? One entry per competitor. Include: what
changed, why it matters, and what (if anything) to do about it.

## Ideas
Product opportunities, feature ideas, or strategic moves surfaced by the research. Be specific —
"add X to solve Y for Z users" is better than "improve onboarding."

## Risks
Market risks, competitive threats, or internal signals that could hurt the product. Rank by
severity. Include a suggested mitigation for each.

## Sources
Cite every file, meeting, and document used. Format: [Title] — [source type] — [date if known]

Rules:
- If any source is unavailable, skip it and note it at the top of the file
- Do not overwrite existing summaries — always create a new file named research-summary-YYYY-MM-DD.md
- Save to Google Drive at {{OUTPUT_FOLDER}}
- Return the Drive link when done

Setup

FieldValue
MCPs requiredGoogle Drive, Granola, Browser (for web signals)
Input folder/Product/Research (or your folder)
Outputresearch-summary-YYYY-MM-DD.md/Product/Research
SchedulerWeekly

Placeholders to fill in

  • {{INPUT_FOLDER}} — Google Drive path to your research folder, e.g. /Product/Research
  • {{PRODUCT_DESCRIPTION}} — One sentence on what your product does and who it serves
  • {{OUTPUT_FOLDER}} — Where to save the digest, e.g. /Product/Research

Tips

  • Keep a competitors.md in your Research folder listing the competitors to monitor — the skill will find it automatically.
  • Add links to newsletters, blogs, or analyst reports to your Research folder and the skill will pull them in.
  • Pair with the competitor-monitoring skill for deeper per-competitor analysis on the same schedule.
  • The Sources section makes this easy to share with leadership — every claim is traceable.
Repository
amplitude/builder-skills
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.