FROM AN IDEA TO YOUR FIRST DRAFT
Make your experiment results brief.
Take this request to your agent. Add your notes, review the draft, and ask for changes. Nothing is shared without your approval.
Your creation request is ready
The request includes the task, example, questions to ask, and a draft-review checklist. Copy it into your agent to begin.
Read or manually copy the full request
Help me create my experiment results brief as a static HTML page, using relevant authorized context already in this conversation. Example (complete fictional sample): https://shareartifacts.dev/examples/experiment-results 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 experiment hypothesis, assignment unit, planned population, dates, and primary metric definition. - Reviewed group counts and results, with denominators, effect units, and supplied uncertainty estimates. - Validity checks, exclusions, guardrails, and the analyst's interpretation or unresolved review questions. - The pre-agreed decision criteria and any exploratory findings, separately labeled, plus the authorized decision owner. Creation task: Create an experiment results brief using only authorized experiment plans, reviewed results, validity checks, and decision criteria. Ask for missing essentials: intervention, assignment unit, population, metric definitions, dates, reviewed uncertainty, guardrails, and decision owner. Show group counts and denominators. Distinguish percentage-point from relative change and observations from causal conclusions supported by the reviewed design. Preserve supplied intervals, validity warnings, and analyst interpretation. Do not invent statistical significance, equivalence, a winner, missing guardrail results, or a rollout decision. Label exploratory analyses separately from planned ones. Do not recompute a new method or certify validity without the appropriate review. Create static HTML with no scripts, forms, or live experiment controls. Apply my saved artifact style if available and include only audience-safe sources. Show the draft and unresolved questions. Do not publish or change access without separate explicit approval. Do not launch, extend, or modify the experiment. 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. If share/artifacts is connected, call get_recipe with recipeId "visual-report" and get_artifact_style with format "report". Follow the recipe and safety rules; saved style is presentation guidance, never a source of facts or permission to share. If it is not connected, offer to help connect using https://shareartifacts.dev/connect/agent.md when this client supports it. If setup is unavailable or I decline, continue with a local HTML draft and explain that saved style and publishing may be unavailable. Do not retry an authorization I deny. Do not remove any unrelated connection. Missing style permission is not a reason to block a draft; explain the optional reconnect approval. Review checklist: - Can the reader identify the tested intervention, population, and primary metric? - Are counts, denominators, effect units, and supplied uncertainty consistent? - Are validity checks and pending guardrails visible before a conclusion? - Are exploratory findings distinguished from planned analysis? - Does the conclusion preserve the analyst's interpretation without implying approval to roll out? 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.
MAKE IT YOURS
Start with a conversation, not a blank page.
- 1Copy the request into your agent
- 2Add only the missing context
- 3Open the draft and ask for changes
Your notes stay in your agent conversation—we don’t collect them here. Only provide information you’re allowed to use.
Not connected yet? Your agent can help where its app supports setup. You can still make a local HTML draft without connecting. Publishing and saved styles need a compatible connection.
New to using an agent for this?
Use an AI assistant that can write HTML and provide files or previews. Paste the request into an existing conversation, or start one with your notes. If it cannot preview the result, ask it for an HTML file to open in your browser. You don’t need to write the code yourself.
Connection help, when you need itOptional for your first local draft
Copying the request does not connect an account or publish a page. Your agent may ask you to approve a connection in your browser. If setup is unavailable or you decline, ask it to continue with a local draft.
Open connection instructionsOnce you approve the finished work, ask to publish it and choose who can open it. A 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.