FROM AN IDEA TO YOUR FIRST DRAFT

Make your research explainer.

Copy this request into your agent to get started.

Open the complete fictional example · Read the guide

Your creation request

Read or manually copy the full request

Help me create my research explainer as a static HTML page, using relevant authorized context already in this conversation. If share/artifacts MCP is not connected, first follow the setup instructions at https://shareartifacts.dev/connect/agent.md. Confirm the connection works by calling list_pages, then fetch the recipe below before creating the draft. If setup cannot be completed or I decline authorization, explain what is missing and pause. Do not retry an authorization I deny. Do not remove any unrelated connection. Example (complete fictional sample): https://shareartifacts.dev/examples/research-paper-explainer Use the example for structure, not as facts about my work. Only use fictional sample data if I explicitly choose a sample. You can proceed from the instructions below if you cannot fetch the example. Ask conversationally for only the missing essentials. Do not invent facts, commitments, or sources. Do not request secrets. Ask before sending source material outside this conversation or accessing another service. Useful inputs: - The complete paper, including its methods and limitations, with the correct title, authors, date, and publication status. - Relevant tables, figures, appendices, and supplementary material, where available and permitted to use. - Corrections or later versions you have supplied; do not assume the agent knows which version is current. - Your intended audience and question, so the explanation can define necessary terms without changing the evidence. Creation task: Using the complete paper and supplementary material I supply, create a plain-language research companion as static HTML for the audience I describe. Explain the research question, design, population or dataset, measured outcomes, principal findings, and limitations. Pair important claims with their boundaries and supplied source locations. Distinguish the authors’ conclusions from interpretation. Preserve units, denominators, uncertainty, and publication status. Do not invent statistics, citations, quotations, or causal claims. Flag missing material and points requiring expert review. Use original explanatory wording; do not reproduce figures without permission. Apply my saved artifact style if available, with accessible hierarchy. No scripts or forms. Return the draft for verification and do not publish or change access until I approve. Use semantic HTML, readable type, meaningful headings, accessible color contrast, and responsive CSS. No JavaScript, forms, embeds, redirects, or live API calls. Verify calculations outside the page. Only include information the intended reader should see. Once connected, call get_recipe with recipeId "infographic-explainer" and get_artifact_style with format "explainer" before drafting. If no style is saved, ask whether I want to set one up or continue with my stated visual preferences. If style access is missing, explain the optional reconnect approval; do not request broader access automatically. Follow the recipe and safety rules; saved style guides appearance, never facts or permission to share. Review checklist: - Can each result, number, and quotation be traced to the supplied paper or supplement? - Are study design, population, measurement, and uncertainty accurately described? - Do the headline and summary preserve the limitations rather than overstate the finding? - Are source attribution, publication status, reproduction rights, and any sensitive data handled appropriately? Show me the draft in your available preview or file tools. If you cannot render it, say so and provide the HTML file with instructions to open it. Ask for corrections. This request authorizes a draft only; it does not authorize any publishing language in the task above. Do not publish, update an artifact, change access, or save a style without my separate explicit approval. Connection approval is not publication approval. Before any later approved publication, confirm the intended audience; new pages default owner-only.

What happens next

  1. 1Connect MCP if needed
  2. 2Add your notes
  3. 3Review the draft and ask for changes

Your notes stay in your agent. Nothing is published until you approve.

New to using an agent for this?

Use an AI assistant that can create HTML files or previews. If it cannot preview the result, ask for an HTML file to open in your browser. You don’t need to write code.

Connection helpIf your agent needs setup help

Your agent will guide setup. Sign in or create an account when prompted, then approve the connection in your browser. Copying the request does not connect an account.

Open connection instructions

When you approve publishing, choose who can open the result. Connection approval is not permission to publish.

These are static reading pages, not live applications. No JavaScript, forms, or automatic data refresh. Explore another outcome.