Make your workshop pre-read.

Help me create my workshop pre-read 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/workshop-pre-read 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 workshop purpose, intended participants and decision authority if there is one. - Essential background evidence with dates and limits. - Open options, constraints and questions; distinguish them from decisions already made. - The requested preparation, proposed agenda and confirmed logistics if available. Creation task: Create a workshop pre-read from my authorized purpose, evidence, open options and preparation requirements. Ask for missing essentials. State whether the session explores, recommends or decides. Separate facts, interpretations and proposals; do not invent agreement, votes, effort estimates, logistics or decision authority. Lead with the discussion question and one concrete preparation task. Keep optional background separate. Use static HTML with no scripts or forms and my saved style if available. The page does not collect responses or attendance. Show the draft and unresolved questions; keep decisions in the existing workflow. Do not publish or change access without separate explicit approval. 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 "visual-report" and get_artifact_style with format "report" 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: - Is the session's actual authority clear? - Is essential reading separate from optional background? - Can participants identify the specific preparation task? - Are open options and missing evidence still visibly open? 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.