FROM AN IDEA TO YOUR FIRST DRAFT
Make your quarterly business review.
Copy this request into your agent to get started.
Your creation request
Read or manually copy the full request
Help me create my quarterly business review 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/quarterly-business-review 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 customer's agreed objectives and success measures, including any missing baseline. - Dated quarterly exports with consistent definitions, populations, and reporting periods. - Audience-safe customer feedback and the status of commitments from the previous review. - Confirmed owners, open blockers, and proposed next-quarter actions. Include renewal or commercial details only if authorized. Creation task: Create a quarterly business review for [customer audience] using only supplied or authorized objectives, dated metrics, feedback, and previous commitments. Ask only for missing essentials: reporting periods, definitions, customer objectives, evidence, and the next decision. Organize around the customer's goals. Separate adoption from measured business outcomes, and delivered work from acceptance. Preserve denominators, comparability limits, missing baselines, and unresolved owners. Do not invent ROI, savings, customer quotations, renewal intent, commitments, or dates. Label proposed next-quarter actions as proposals and keep actual agreement in our existing customer workflow. Use only audience-safe evidence and links; leave private account notes in my authorized tools. Create readable static HTML with no scripts, forms, or live-data claims. Use my saved artifact style if available. Show the draft and claims to verify. 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: - Does the opening address a customer objective rather than seller activity? - Are adoption and business outcomes separate, with missing baselines visible? - Are quarterly comparisons valid for the same population and definitions? - Are proposed actions, commercial terms, and commitments correctly labeled? - Has the customer-facing disclosure and recipient access been reviewed? 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
- 1Connect MCP if needed
- 2Add your notes
- 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 instructionsWhen 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.