01 / The familiar format
You could share this as a wiki page.
A fictional wiki entry with the same underlying facts. Read it here, then compare how the HTML version presents the information.
Team wiki · Fictional example
Cedar monthly service briefing — reusable instructions and test cases
Recurring task
September 7, 2026. This is an invented instruction-testing exercise, not performance data. Explain current-month request completion with closed count, eligible count and rate where both counts are available: closed / eligible × 100.
Fixed rules and style
Use only the current edition’s authorized bundle. State period and definitions, show calculations where possible, ask for missing inputs, and never fill a gap with previous-period values. Do not infer causes or compare incompatible definitions. Use readable headings and one restrained accent; style does not determine arithmetic or permission to share.
Test inputs and expected results
August A1 has 18 closed / 24 eligible, with matching August definitions: 18 / 24 × 100 = 75%. September S1 has 21 closed but no eligible count. A September rate or rate comparison cannot be established; 21 / 24 would misuse August’s denominator. Ask for September’s eligible count, without inventing a deadline or claiming improvement.
Review and setup boundaries
The creator reviews period, definitions, arithmetic, gaps and audience. Show these instructions and both test outcomes in a static reading page. Saving the instructions does not configure memory, scheduling, access or publication; no client installation is requested.
02 / The HTML version
Same information. See what needs your attention.
This is the complete static HTML example, not a screenshot. Scroll inside the preview to read it all. It has no live data, scripts, forms, or external resources.
Inspect the complete HTML source
This is the authored source for the example. The preview above passes through our HTML sanitizer before rendering in an isolated frame.
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Cedar monthly brief: instructions tested on two editions</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#faf6fa;color:#302439;font:17px/1.65 system-ui,sans-serif}main{max-width:1000px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.14 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.3 Georgia,serif;overflow-wrap:anywhere}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.6 system-ui,sans-serif;letter-spacing:.08em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#53355f;color:white;padding:24px;margin:28px 0}.lead p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,230px),1fr));gap:20px;margin:24px 0}.card{background:white;border:1px solid #bbc5c4;padding:24px}.metric{font:500 38px/1.2 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{font-size:14px}.warning{border-left:5px solid #956118;padding-left:20px}a{color:inherit;text-underline-offset:4px}a:focus-visible,summary:focus-visible{outline:3px solid #956118;outline-offset:4px}table{width:100%;border-collapse:collapse;table-layout:fixed;font-size:15px}th,td{text-align:left;vertical-align:top;border-bottom:1px solid #bbc5c4;padding:12px 8px;overflow-wrap:anywhere}caption{text-align:left;font-weight:700;padding:12px 0}pre,code{white-space:pre-wrap;overflow-wrap:anywhere}footer{border-top:1px solid #bbc5c4;padding-top:24px;margin-top:40px;font-size:14px}@media(max-width:480px){th,td{padding:10px 4px;font-size:14px}}@media print{body{background:white}.card,.lead{break-inside:avoid}h2,h3{break-after:avoid}}
</style></head><body><main><header><p class="label">Cedar / Fictional instruction test / September 7, 2026</p><h1>Reuse the task. Never reuse a missing denominator.</h1><p class="intro">A portable instruction sheet tested against one complete month and one incomplete month.</p></header><section><h2>The fixed task instructions</h2><div class="card"><ol><li>Use the current month's authorized source bundle only.</li><li>Show the period, closed requests and eligible requests.</li><li>Calculate completion as closed ÷ eligible × 100 only when both counts and their definitions are supplied.</li><li>If an essential input is missing, report what is known and ask for the gap. Do not copy an earlier value or invent a cause.</li><li>Review facts, arithmetic and audience before any separate publication approval.</li></ol><p class="note">Sources T1, F1 and R1. Style is a separate preference, not a calculation rule.</p></div></section><section><h2>Test one: a complete August bundle</h2><div class="lead"><p class="label">A1 · August</p><h3>18 of 24 eligible requests closed</h3><p>18 ÷ 24 × 100 = <strong>75% completion</strong>.</p><p>Both counts cover August and use the same request definition.</p></div></section><section><h2>Test two: an incomplete September bundle</h2><div class="card"><p class="label">S1 · September</p><h3>21 requests closed. Rate unavailable.</h3><p>The eligible request count is missing. Ask for September's eligible count before calculating a completion rate.</p><p class="warning">Do not calculate 21 ÷ 24: 24 belongs to August. These inputs cannot establish that the completion rate improved.</p></div></section><section><h2>What stays fixed—and what must change</h2><h3>Reuse boundary</h3><table><thead><tr><th scope="col">Keep in the instructions</th><th scope="col">Supply for each edition</th></tr></thead><tbody><tr><td>Reader task and rate definition</td><td>Current period and current source counts</td></tr><tr><td>Missing-input behavior and review gate</td><td>Current evidence and unresolved questions</td></tr><tr><td>Readable style preference</td><td>Audience and separate sharing approval</td></tr></tbody></table></section><section><h2>Use deliberately next time</h2><p>Store these instructions in a location supported by your chosen workflow and deliberately provide or retrieve them. This page does not install a skill, remember a future conversation, schedule a report, access a source system or publish an edition.</p><p class="note">Sources V1, R1 and O1. No deadline or causal explanation is supplied.</p></section><footer>Fictional worked example by share/artifacts. Names, dates, figures and records are invented for demonstration. Static snapshot; no live data or automatic updates.</footer></main></body></html>
Make the next one about your work.
- Take the task to your agent. We provide a request with the goal, example, and checks. Copy it into the conversation where your context lives.
- Supply only what is missing. Use material your agent is authorized to access. Don’t substitute the example’s invented facts for your own.
- Review a draft before sharing. Check facts, readability, and sensitive information. Publishing and choosing who can open it are separate, explicit decisions.
Make this with my agentNo publishing connection is needed for an initial local draft. Your agent needs to be able to create an HTML file; preview and connection support vary by client.