Use these prompts as adaptable starting points. Tool capabilities and integrations vary by account, so confirm what data is being used and verify factual answers through reliable primary sources.
1. Create a Research Roadmap
I need to research [question] for [purpose]. Build a research roadmap with definitions, subquestions, primary-source types, useful search terms, likely bias, and a method for recording evidence. Do not answer the research question yet.
2. Compare Sources Carefully
Compare the sources I provide about [topic]. For each, identify the author or organization, publication date, evidence, methodology, incentives, limitations, and claims supported. Then explain where the sources agree or disagree. Do not treat popularity as reliability. Sources: [links or text]
3. Analyze an Image or Diagram
Describe the attached [image/diagram] for [purpose]. Separate directly visible details from interpretations. Identify unclear elements, possible accessibility issues, and questions a domain expert should answer. Do not infer sensitive personal traits.
4. Prepare for a Meeting
Help me prepare for a meeting about [topic] with [participants]. The desired outcome is [outcome]. Create an agenda, essential questions, decisions needed, preparation tasks, likely disagreements, and a concise follow-up template.
5. Build a Learning Plan
Create a [number]-week learning plan for [skill]. My current level is [level], time available is [time], and desired outcome is [outcome]. Include practice activities, evidence of progress, review intervals, and a final project. Avoid recommending resources you cannot verify.
6. Organize a Complex Week
Help organize my week using these commitments and priorities: [list]. Identify conflicts, unrealistic assumptions, deep-work blocks, small tasks, recovery time, and items to postpone. Explain the trade-offs rather than filling every hour.
7. Develop Interview Questions
Create structured interview questions for a [role] focused on [skills]. Include a scoring rubric, evidence to listen for, fair follow-up questions, and bias risks. Do not ask about protected personal characteristics.
8. Explain Data for a Nontechnical Audience
Explain the data below to [audience]. Separate observations from possible explanations, note uncertainty and missing context, and suggest three questions to investigate next. Do not imply causation from correlation. Data: [data]
9. Create a Travel Research Checklist
Create a research checklist for a trip to [destination] during [dates]. Include entry requirements, transport, weather, accessibility, budget, local customs, safety, and information that must be verified close to departure. Do not invent current prices or rules.
10. Improve a Workflow
Analyze this workflow: [steps]. The goal is [goal]. Identify delays, repeated work, unclear ownership, error risks, and steps that require human judgment. Suggest a simpler version and metrics to determine whether it is actually better.
11. Verify a Current Rule or Policy Change
Investigate whether [rule/policy/requirement] currently applies to [person, organization, or location]. Prioritize official sources. For each source, record the issuing authority, effective date, jurisdiction, exact relevant language, and URL. Separate confirmed requirements from interpretations and unresolved questions. Do not rely on search-result snippets or assume an older rule is still current.
Use carefully: Confirm high-stakes conclusions with the responsible authority or a qualified professional.
12. Turn Mixed Files Into a Decision Packet
Using the approved files I provide, prepare a decision packet for [decision-maker] about [decision]. Create: a one-paragraph decision summary, evidence table with source locations, options and trade-offs, missing information, contradictions, risks, and questions that must be answered before approval. Do not fill gaps with outside facts unless I explicitly request research.
13. Audit Visual Content for Accessibility
Review the attached image, chart, or slide for accessibility. Describe the information it communicates, identify text that may be unreadable, color-only distinctions, low contrast, unclear reading order, and details missing from an equivalent text description. Draft concise alt text and a longer description, then list checks that still require a person or accessibility-testing tool.
14. Build a Claim Verification Table
Review these claims about [topic] and build a verification table. For each claim, state what evidence would confirm or disprove it, the strongest available source I supplied, publication date, source limitations, confidence, and next verification step. Mark opinions and predictions separately. Claims and approved sources: [paste material or links]
15. Design a Human-Supervised Automation Workflow
Design a proposed automation workflow for [repetitive process]. Map inputs, steps, decision points, outputs, data access, failure modes, and handoffs. Clearly identify tasks that require human judgment, approval, privacy review, or exception handling. Include a small pilot, success metrics, rollback plan, and audit log requirements. Do not assume automation is beneficial without evidence.
16. Create a Local-Service Verification Plan
Help me verify current information about [local service, office, program, or facility] in [location]. Prioritize the responsible organization and official local sources. Record address, eligibility, operating hours, appointment rules, accessibility information, contact method, source URL, and last-updated date. Mark anything that requires a phone call or in-person confirmation. Do not rely only on map listings or third-party directories.
17. Research Product Compatibility Before Purchase
Research whether [product/accessory/software] is compatible with [existing device, system, version, or constraint]. Build a table of required specifications, confirmed matches, conflicts, adapters or subscriptions needed, source dates, and unresolved questions. Prioritize manufacturer documentation and identify regional or model-number differences. Do not recommend a purchase until every essential requirement is verified.
Verification: Recheck model numbers, return terms, and current specifications with the seller before buying.
18. Compare Public Datasets Before Choosing One
Compare candidate public datasets for [research or project goal]. For each dataset, verify the publisher, purpose, collection method, coverage, dates, license, update frequency, missing-data notes, known limitations, and documentation URL. Explain which requirements each dataset can and cannot support. Do not treat a larger dataset as automatically better or combine datasets without checking compatibility.
19. Verify an Event Timeline From Current Sources
Build a sourced timeline of [public event or development] for [purpose]. Prioritize primary statements, official records, and dated source material. For each entry, include event date, publication date, confirmed fact, source URL, and unresolved disagreement. Separate later interpretation from what was known at the time. Do not include private individuals' personal information or use social posts as confirmation without corroboration.
20. Verify a Software Integration Before Enabling It
Research whether [integration] is appropriate for connecting [system A] and [system B]. Prioritize official documentation. Verify supported versions, permissions, data transferred, storage and retention, authentication method, regional availability, limits, failure behavior, pricing dependencies, and rollback steps. Create a checklist of questions that still require an administrator, security reviewer, or vendor response. Do not request or expose credentials.
21. Build a Current Funding or Grant Eligibility Brief
Research the current eligibility and application requirements for [public grant, scholarship, or funding program] for [applicant type and location]. Prioritize the administering organization and official documents. Record eligibility, exclusions, deadline with timezone, required evidence, permitted costs, selection process, official URL, and last-updated date. Separate confirmed requirements from unclear interpretations and advise direct confirmation before applying.
22. Verify Document Requirements for an Application
Research the current document requirements for [application, permit, enrollment, or process] in [jurisdiction or organization]. Prioritize official sources. Record required documents, accepted formats, translation or notarization rules, deadlines, fees if official, submission method, source URL, publication or updated date, and items that require direct confirmation. Do not rely on forum posts or outdated summaries.
23. Build a Source Watchlist for a Changing Topic
Create a source watchlist for tracking changes to [policy, product, standard, or market]. Include official pages, documentation feeds, regulatory or standards bodies if relevant, update frequency, signals worth monitoring, archive method, and a short template for recording changes. Separate primary sources from commentary and do not assume absence of news means no change occurred.
24. Verify Current Tool Feature Availability
Research whether [tool or platform] currently supports [feature] for [plan, region, device, or account type]. Prioritize official documentation, release notes, and support pages. Record the feature status, limitations, setup requirements, source URLs, last-updated dates where available, and anything that needs direct confirmation inside the account. Do not rely on old forum answers as final evidence.
25. Build a Local Market Research Source Pack
Create a source pack for understanding [market or audience] in [location]. Find reliable public sources for demand signals, regulations, competitors, pricing references, customer behavior, and local terminology. Separate official data, industry reports, company pages, and commentary. Include source URLs, dates, limits of each source, and questions that still require interviews or first-party data.
26. Compare Current Official Standards or Guidelines
Research and compare the current official standards, guidelines, or frameworks for [topic]. Prioritize standards bodies, regulators, official documentation, and primary publications. Create a table with scope, audience, date, status, key requirements or recommendations, limits, source URL, and how each source should or should not be used. Flag anything that requires specialist interpretation.
27. Verify Vendor Documentation Before Implementation
Review the current official documentation for implementing [vendor feature/API/integration]. Extract prerequisites, authentication requirements, permission scopes, data sent and stored, rate limits, error handling, versioning, regional limits, pricing dependencies, test environment options, and rollback steps. Include source URLs and dates where visible, and list questions that require vendor support confirmation.
28. Build an Event or Conference Research Brief
Research [event or conference] for [goal: attend, sponsor, speak, recruit, or learn]. Prioritize official event pages, organizer information, schedules, speaker pages, sponsor lists, accessibility information, location details, dates, and refund or registration terms. Create a brief with source URLs, what is confirmed, what changed recently if visible, and questions to verify before committing money or travel.
29. Check Citations Against Source Claims
Check whether these citations actually support the claims in [draft/report/page]. For each claim, inspect the cited source if available, state whether it fully supports, partly supports, does not support, or is outdated, and quote only the minimum needed excerpt. Flag missing dates, broken links, secondary sources, and claims that need a stronger primary source. Claims and citations: [paste list]
30. Verify a Supplier or Partner Before Outreach
Research [supplier, partner, or organization] before outreach for [purpose]. Prioritize official company pages, public filings if relevant, current contact pages, product documentation, leadership pages, and recent official announcements. Build a brief with confirmed services, locations served, contact route, red flags to verify, source URLs, source dates, and questions to ask directly. Do not rely on directory snippets as final evidence.
31. Build a Regional Compliance Source Map
Create a source map for researching [regulatory or compliance topic] in [region]. Identify the responsible authorities, official guidance pages, update feeds, forms or portals, definitions that matter, effective dates to check, and specialist questions that cannot be answered from public pages alone. Do not summarize obligations until the official sources are reviewed.
32. Verify Medical or Health Information Sources Safely
Research background information about [health topic] for general education. Prioritize official public health agencies, peer-reviewed reviews, hospital or university explainers, and dated clinical guidance where appropriate. Record source URL, date, intended audience, what it supports, and what it does not prove. Do not diagnose, recommend treatment, or replace a qualified professional.
33. Build a Current Documentation Change Brief
Check current official documentation for [tool, API, policy, or process] and summarize what changed since [date/version]. Include source URLs, visible dates, affected users, migration actions, deprecations, limits, and items requiring direct account verification. Separate confirmed changes from interpretation.
34. Build an Official Finance Source Map
Create a source map for researching [finance, accounting, payment, or reporting topic] in [region or organization type]. Prioritize official regulators, standards bodies, tax authorities, payment network documentation, and dated guidance. Record source URL, scope, date, authority, and what still requires a qualified finance or legal reviewer. Do not provide financial advice.
35. Verify Procurement Evidence Before Approval
Research and organize current evidence for approving [vendor/tool/service]. Prioritize official vendor documentation, security pages, pricing pages, status pages, contract notes provided by me, and support documentation. Create a brief covering data access, renewal terms to verify, export options, support limits, implementation risks, and unanswered questions. Do not infer contract terms.
Responsible Use
Review what information connected services may expose before using integrations. Keep high-stakes decisions and final verification with an accountable person.