A BETTER WAY TO SHARE THE WORK
Save the way you make a good report—not last month's answers
A useful reusable prompt remembers the job. It does not carry old numbers into the next edition.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
How do I create reusable instructions for recurring artifacts?
Describe the recurring reader task, required source inputs, output structure and checks that every edition must pass. Keep changing facts such as dates and numbers in a separate input section. Reference your saved style separately. Test the instructions on a second source bundle, including missing information, before relying on them.
01 / SEE THE DIFFERENCE
A reusable monthly completion brief that catches a missing denominator
Fictional Cedar service updates. Two synthetic editions test the same instructions.
Task: explain monthly request completion using closed requests divided by eligible requests. August has 18 closed of 24 eligible. September has 21 closed, eligible count missing. Use current sources only; do not carry August values into September.
- Fixed instruction
- Report the period, closed count, eligible count and completion rate when both counts are known.
- August run
- 18 / 24 = 75% completion for August.
- September run
- 21 requests closed. Completion rate unavailable because the eligible count is missing.
- Review gate
- Ask for September's eligible count; do not reuse 24 or claim an improving rate.
Open a complete fictional HTML example, with its source notes →
Create my reusable artifact instruction sheet02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
Extract the job, not the old content
Describe what the reader needs to learn or decide in each edition. Preserve useful structure and checks, but remove old names, dates, values and conclusions from the instructions. A previous report can be an example of shape without becoming evidence for the next report.
Separate fixed rules from fresh inputs
Use clear sections for the recurring task, current source bundle, optional references and review requirements. Mark which inputs are essential and what to do when they are missing. A prompt with placeholders is not a connection to the source system; the user or authorized agent still provides current data.
Keep style and authority separate
Saved style guides typography, palette and tone. Task instructions define the question, evidence and checks. Neither authorizes publication or access changes. Store the instructions where your workflow can deliberately retrieve them; do not assume every client remembers previous conversations.
Test with a different and incomplete edition
Run the instructions on a new source bundle with changed values, then one with an omitted definition or denominator. Check that the agent uses fresh facts and asks about the gap rather than copying the old answer. Revise the instructions when a recurring error becomes visible.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
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.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- 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?
When HTML fits
A portable instruction sheet for repeat creation, with an input checklist and observable review tests.
When another format fits better
This is not an installed agent skill, automatic memory, scheduler or data connector. Use your client's actual supported storage and scheduling workflow when needed.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
Is this the same as a saved style?
No. Style covers reusable visual and editorial preferences. Task instructions cover the reader question, required evidence, output and checks. You can use one style across many different task instructions.
Will my agent remember these instructions automatically?
Do not assume so. Store them in a location your chosen workflow supports and deliberately provide or retrieve them for the next task. Availability varies by client and setup.
Does this schedule the next report?
No. These instructions define how to create and review an edition. Scheduling, authorized data access and publishing operations are separate workflows, and the instruction sheet does not configure them.