30 Best Manus Prompts

<context> Topic: [MARKET OR INDUSTRY] Geography: [REGION / COUNTRY] Time horizon: [E.G. NEXT 18 MONTHS] Reader: [WHO WILL USE THIS, E.G. OUR EXEC TEAM] Constraints: only cite sources from the last 24 months; flag anything older as dated </context> <task> Produce a structured market landscape report. End-to-end, autonomously: 1. Browse the web and identify the 8-12 most credible primary sources (analyst reports, regulator filings, company disclosures, reputable press). 2. Map market size, growth rate, and the 5-7 leading players with their positioning and recent moves. 3. Identify 3-4 key trends and 3 material risks, each backed by a cited source. 4. Write a 1,500-2,000 word report with an executive summary, sections per the above, and a sources table (claim, source, date, URL). 5. Deliver as a single formatted document (Markdown or PDF). List any gaps where evidence was thin. </task>

<context> Question: [THE SPECIFIC QUESTION YOU WANT ANSWERED] Field: [DISCIPLINE OR DOMAIN] Quality bar: prioritize peer-reviewed studies, meta-analyses, and primary data over blog posts </context> <task> Run an evidence review and resolve the question above. 1. Search for the most relevant studies and authoritative sources; collect at least 10. 2. For each source, extract the finding, sample/method, and any stated limitations. 3. Group findings by where they agree, conflict, or remain uncertain. 4. Write a synthesis that answers the question directly, with a confidence rating and the reasoning behind it. 5. Deliver the synthesis plus an appendix table of every source (citation, finding, link). </task>

<context> Company: [COMPANY NAME + URL] Purpose: [E.G. PARTNERSHIP, INVESTMENT, COMPETITIVE ANALYSIS] Depth: medium — public information only, no speculation presented as fact </context> <task> Build a due-diligence brief on the company. 1. Gather company background: founding, leadership, funding, headcount, business model. 2. Map products, pricing, and primary customer segments. 3. Assess market position vs. 3-5 named competitors. 4. Collect recent signals: news, hiring, product launches, reviews, sentiment. 5. Flag risks or red flags with the source for each. 6. Deliver a 1-page summary plus a detailed appendix, all claims cited with URLs. </task>

<context> Topic: [COMPLEX TOPIC] Audience: [E.G. NON-TECHNICAL EXECUTIVES / NEW HIRES] Length: [E.G. 1,200 WORDS] Tone: clear, concrete, no jargon without a plain-language definition </context> <task> Research the topic and write an explainer the audience can act on. 1. Verify the current state of the topic from at least 6 reliable sources. 2. Structure the piece: what it is, why it matters now, how it works, what to do about it. 3. Use one worked example and one analogy the audience will recognize. 4. Add a short "common misconceptions" section. 5. Deliver the formatted explainer plus a 5-bullet TL;DR at the top and a sources list. </task>

<context> Decision: [WHAT YOU ARE CHOOSING BETWEEN] Options: [OPTION A], [OPTION B], [OPTION C] Criteria that matter most: [E.G. COST, TIME-TO-VALUE, SUPPORT, LOCK-IN] </context> <task> Research each option and produce a decision-ready comparison. 1. Gather current, accurate facts on each option from official and independent sources. 2. Score every option against each criterion, showing the evidence behind each score. 3. Build a comparison table and a weighted recommendation based on the stated priorities. 4. Note the strongest argument for the option you did NOT recommend, for balance. 5. Deliver the table, a 1-paragraph recommendation, and a sources appendix. </task>

<context> Target data: [WHAT TO COLLECT, E.G. TOP 100 SAAS TOOLS IN CATEGORY X] Fields per row: [NAME], [URL], [PRICING], [FOUNDED], [CATEGORY], [OTHER] Source preference: official sites first, then reputable directories </context> <task> Collect the dataset and deliver it as a clean spreadsheet. 1. Browse the web to find entries that match the target; aim for the requested count. 2. For each row, populate every field; leave blank (not guessed) where data is unavailable. 3. Normalize formats: consistent currency, dates as YYYY-MM-DD, trimmed text. 4. Add a "source_url" column for each row so every value is verifiable. 5. De-duplicate and deliver a .csv plus a short note on coverage and any fields that were hard to find. </task>

<context> Data: [UPLOADED FILE / LINK TO DATASET] Goal: [WHAT DECISION OR QUESTION THIS DATA SHOULD INFORM] Audience: [WHO READS THE FINDINGS] </context> <task> Analyze the dataset and report the insights that matter. 1. Load and profile the data: row count, columns, types, missing values, obvious anomalies. 2. Run the analysis needed to answer the goal — write and execute the code yourself. 3. Surface the 5 most decision-relevant findings, each with the supporting number or chart. 4. Generate clear visualizations for the top findings. 5. Deliver a short findings report (charts embedded), the analysis code, and a caveats section on data quality. </task>

<context> Responses: [UPLOADED OPEN-TEXT RESPONSES / FEEDBACK EXPORT] Question they answered: [THE PROMPT THEY RESPONDED TO] What I need: themes, sentiment, and representative quotes </context> <task> Synthesize the open-text responses into actionable themes. 1. Read all responses and cluster them into 6-10 distinct themes. 2. For each theme, report frequency, overall sentiment, and 2-3 verbatim example quotes. 3. Rank themes by a combination of frequency and intensity. 4. Note any contradictions or notable minority views. 5. Deliver a themes report and a tagged spreadsheet mapping each response to its theme(s). </task>

<context> Items to track: [LIST OF PRODUCTS / URLS] Attributes: [PRICE], [AVAILABILITY], [KEY SPECS] Reference baseline: [PRIOR VALUES IF YOU HAVE THEM] </context> <task> Gather current values for each item and build a comparison snapshot. 1. Visit each source URL and read the current price, availability, and listed specs. 2. Record values in a table with a timestamp and the source URL per row. 3. If a baseline was provided, compute the delta and flag meaningful changes. 4. Highlight the best current option per a stated criterion (e.g. lowest price in stock). 5. Deliver the table as a spreadsheet plus a 3-bullet summary of what changed. </task>

<context> Document: [UPLOADED PDF / REPORT / CONTRACT] What I need extracted: [E.G. ALL OBLIGATIONS, DATES, AND DOLLAR AMOUNTS] Output shape: a structured table plus a plain-language summary </context> <task> Parse the document and extract the requested information. 1. Read the full document, noting section/page references as you go. 2. Extract every instance of the requested data into structured rows with a page citation. 3. Summarize the document in plain language in under 300 words. 4. Flag anything ambiguous, conflicting, or that appears to be missing. 5. Deliver the structured table (with page references) and the summary in one file. </task>

<context> Product: [WHAT IT IS, ONE LINE] Audience: [WHO IT IS FOR] Primary action: [E.G. JOIN WAITLIST / BOOK DEMO] Brand: [COLORS / TONE / ANY REFERENCE SITE] </context> <task> Build and deliver a working landing page. 1. Write the copy: a clear headline, subhead, 3 benefit blocks, social-proof placeholder, and one strong CTA. 2. Build a responsive single-page site (HTML/CSS, or a clean static framework) matching the brand. 3. Wire the primary action to a simple form that captures the input (note where submissions go). 4. Ensure it loads fast, looks right on mobile, and passes basic accessibility checks. 5. Deliver the deployable files plus a preview link and a short note on how to publish it. </task>

<context> App idea: [WHAT IT DOES IN ONE SENTENCE] Core user flow: [THE ONE THING A USER MUST BE ABLE TO DO] Must-haves: [3-5 FEATURES] Out of scope for v1: [WHAT TO SKIP] </context> <task> Build a working MVP that delivers the core flow end-to-end. 1. Define the minimal data model and tech stack, then state it before building. 2. Implement the core user flow first, then the must-have features. 3. Add basic input validation and graceful error states. 4. Test the primary flow yourself and fix what breaks. 5. Deliver running code, a preview link, setup instructions, and a list of known limitations. </task>

<context> Purpose: [WHAT THIS TOOL HELPS A TEAM DO] Data source: [UPLOADED FILE / API / SAMPLE DATA] Key views: [E.G. SUMMARY KPIS, TABLE WITH FILTERS, ONE CHART] Users: [WHO USES IT, HOW OFTEN] </context> <task> Build an internal dashboard that surfaces the key views. 1. Connect to or load the data source and confirm the fields available. 2. Build the summary KPIs, a filterable/searchable table, and the requested chart. 3. Make filters and sorting actually work against the data. 4. Handle empty and loading states cleanly. 5. Deliver the running tool, a preview link, and a one-page guide for the team. </task>

<context> Concept: [GAME OR INTERACTIVE IDEA] Rules / mechanics: [HOW IT WORKS] Visual style: [E.G. MINIMAL, RETRO PIXEL, NEON] Target: playable in any modern browser, no install </context> <task> Build a polished, self-contained interactive experience. 1. Implement the core mechanic so it is fun and bug-free on the first try. 2. Add a start screen, score/state tracking, and a clear win/lose or reset state. 3. Apply the requested visual style consistently. 4. Ensure it runs on desktop and mobile with touch support. 5. Deliver a single deployable build plus a preview link. </task>

<context> Reference: [URL OR SCREENSHOT TO MATCH] Goal: [E.G. RECREATE THIS LAYOUT FOR MY CONTENT / MODERNIZE IT] My content: [WHAT TEXT/IMAGES SHOULD GO IN] What to change: [ANY DELIBERATE DIFFERENCES] </context> <task> Recreate the reference layout with my content. 1. Analyze the reference: layout grid, sections, spacing, typography, and color system. 2. Rebuild the structure as clean, responsive code (do not copy proprietary assets). 3. Populate it with my content and apply the requested changes. 4. Match the look on desktop and mobile, then run a quick QA pass. 5. Deliver the deployable files plus a side-by-side note of intentional differences. </task>