Make your reusable artifact instruction sheet.

Help me create my reusable artifact instruction sheet 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/reusable-artifact-instructions 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: - A recurring audience question and an approved example of a useful result. - The fresh input checklist: reporting period, source dates, definitions and evidence. - Required sections, limits, factual review checks and publication boundaries. - Optional saved style plus where you will store and deliberately reuse the instructions. Creation task: Help me create reusable instructions for [recurring reader task]. Use my authorized example to identify useful structure, required fresh inputs and review checks—not reusable factual conclusions. Separate fixed task rules, current source data, optional references and saved style. Specify what to do when essential facts are missing or contradictory. Test the instructions with a clearly labeled synthetic second edition if I choose, including a missing input. Do not assume persistent memory, automatic retrieval, scheduling or publication. The artifact output should be static HTML without scripts, forms or live queries. Ask only for missing essentials from existing authorized context. Show the instruction sheet and test results for review. 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: - Are dates, values and conclusions kept out of the fixed instructions? - Does each new edition require current source material and definitions? - Does a missing-input test produce a question or limitation rather than an invented answer? - Are style reuse, storage, scheduling and publish approval treated as separate concerns? 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.