Make your service overview.

Help me create my service overview 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/service-overview 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: - Current service scope, intended audience and situations where it is not suitable. - Concrete deliverables, examples permitted for sharing and client prerequisites. - Approved pricing or timing if supplied, with conditions and exclusions. - The verified enquiry process and who can confirm fit and availability. Creation task: Create a service overview from my authorized service scope, intended audience, deliverables, prerequisites and exclusions. Ask for missing essentials. Explain fit and not-for situations before capabilities. Distinguish deliverables from unproven business outcomes. Preserve conditions on supplied price, timing and availability; do not invent certifications, customer references, testimonials or commitments. Use only the confirmed enquiry route. Make static HTML with no scripts or forms and my saved style if available. State that specific scope and availability require confirmation in our existing process. Show me the draft. 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: - Can a prospective client tell whether this is for their situation? - Are deliverables and required client inputs concrete? - Are exclusions and unconfirmed commercial details clear? - Does the next step avoid implying a booking or contract? 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.