More screenshots
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsParallax Document Publisher
1
Format your article, handbook or ebook into a clean reading document with a table of contents, images, references and print styling.
$9
Security scanned
Parallax Document Publisher
Example session with this skill installed
Normal test request
Use Parallax Document Publisher to turn the original fictional fixtures/normal/manuscript.md and its image into a finished handbook. Preserve the prose, numbers, procedure order, code, and warning exactly. Produce a self-contained HTML file, editable Markdown, and production notes. Use Letter print layout and a calm dark-blue/teal palette. The diagram is our own supplied SVG and may be embedded. Make the contents links work even though two headings have the same text.
If a PDF converter is already available, also create and inspect a PDF. Do not install anything just for this test. Clearly distinguish generated files from formats that were not generated. Do not browse or distribute the handbook.
Supplied fictional example files
assets/ticket-flow.svg
<svg xmlns="http://www.w3.org/2000/svg" width="720" height="180" viewBox="0 0 720 180" role="img" aria-labelledby="title desc">
<title id="title">Harbor Bench ticket flow</title>
<desc id="desc">Three connected stations: Intake, Work, and Return. The ticket stays with the object.</desc>
<rect width="720" height="180" rx="12" fill="#eef6f6"/>
<g fill="#15364c"><rect x="30" y="45" width="180" height="70" rx="10"/><rect x="270" y="45" width="180" height="70" rx="10"/><rect x="510" y="45" width="180" height="70" rx="10"/></g>
<g stroke="#267e82" stroke-width="5" fill="none"><path d="M218 80H254M244 70L254 80L244 90"/><path d="M458 80H494M484 70L494 80L484 90"/></g>
<g fill="#ffffff" font-family="sans-serif" font-size="23" text-anchor="middle"><text x="120" y="88">Intake</text><text x="360" y="88">Work</text><text x="600" y="88">Return</text></g>
<text x="360" y="150" text-anchor="middle" fill="#15364c" font-family="sans-serif" font-size="18">The ticket stays with the object.</text>
</svg>
manuscript.md
---
title: Harbor Bench Repair Handbook
author: Harbor Bench Volunteer Team
edition: 1
language: en
---
# Harbor Bench Repair Handbook
This handbook describes an invented neighborhood repair desk. Its procedures are fictional training material, not instructions for electrical repair. The desk's job is to make the next action clear: record the object, name the person responsible for it, and return it with an understandable account of the work.
The handbook is for volunteers who share one room on Saturday mornings. A customer may meet three people during a visit, but should not have to explain the same problem three times. The record travels with the object. If the record is unclear, the next volunteer asks for clarification before treating an assumption as a fact.
## 1. Opening the desk
The opening pair arrives at 08:30. One person prepares the intake table while the other checks the supply drawer. They compare their notes at 08:45 and open the doors at 09:00. The timing leaves a short interval to fix missing labels before customers arrive.
Use a new date sheet for each session. Carry over unfinished work by its existing ticket ID; do not create a second ticket merely because an object returned the following week. A new problem on the same object can be recorded as a linked follow-up rather than overwriting the original description.
| Item | Opening quantity | Reorder when below | Storage location |
| --- | ---: | ---: | --- |
| Paper ticket sleeves | 30 | 8 | Drawer A |
| Removable labels | 60 | 15 | Drawer B |
| Small parts bags | 24 | 6 | Shelf 2 |
| Return envelopes | 18 | 4 | Shelf 3 |
The quantities are counts of individual items, not packs. Record what is actually present; an unopened pack with an unknown count is marked "count pending." A supply total should never be made to look complete by substituting a guess.
### Check-in
Ask each volunteer which station they will cover. A person may help elsewhere later, but the opening sheet should identify one initial station so that everyone knows where to ask for help. Record the handover when a station changes hands.
1. Write the session date and the two opening volunteers' names.
2. Count the four supply items in the table.
3. Place blank ticket sleeves beside the intake pen.
4. Put the unfinished-work tray on the shelf behind the desk.
5. Confirm that each carried-over object has its original ticket.
> Stop intake if an object has no owner contact record. Label it "identity unresolved" and ask the session lead to resolve it before work begins.
## 2. Recording an object
Describe what arrived before describing what might be wrong. "Blue wooden drawer, left handle loose" helps the next person recognize an object. "Needs fixing" does not. Use the customer's account for the reported problem and label a volunteer's explanation as a working hypothesis.
The intake volunteer writes the ticket ID on both the sleeve and the small parts bag. If no small parts are removed, the bag remains empty with the ticket until return. This small duplication prevents a screw or bracket from becoming an unexplained item in the drawer at closing time.
!Ticket flow from intake through work and return
Figure 1. The ticket accompanies the object through all three stations. A return is recorded even when no repair was attempted.
### Check-in
The customer confirms the description and the preferred contact route. Read the short description aloud if the handwriting is difficult to interpret. A correction belongs on the record immediately; it should not wait for the next volunteer to discover the discrepancy.
Use this plain-text record format. Keep the field names unchanged when copying it into a shared note:
```text
ticket_id: HB-0042
received_at: 2026-04-18 09:20
object: blue wooden drawer
reported_problem: left handle loose
owner_confirmed: yes
next_station: assessment
```
## 3. Passing work between volunteers
A handover answers three questions: what changed, what remains uncertain, and what should happen next. Avoid a vague status such as "almost done." If a part is missing, name it. If a check was not performed, say that it was not performed.
Use one sentence for the current condition and one for the next action. For example: "The handle is attached, but the drawer has not been checked in its cabinet. Ask the owner to confirm fit before closing the ticket." This wording separates a completed action from an untested result.
Do not erase a failed attempt. Cross out an incorrect note with a single line on paper, or append a correction in the digital record. A later volunteer may need to know which approach was already tried and why it was abandoned.[^records]
<!-- pagebreak -->
## 4. Returning an object
Return begins with the ticket, not the appearance of the object. Check that the ID on the sleeve matches the object and any bag of loose parts. Explain what was done using the same plain language used at intake. If the team could not complete the work, name the limit without turning it into a promise about another provider.
Invite the owner to compare the result with the recorded problem. Record their response as a response, not as independent proof that every possible issue has been resolved. Close the ticket only when the object and all associated parts have left the desk or an explicit collection arrangement has been recorded.
| Return status | Meaning | Required note |
| --- | --- | --- |
| Collected | Object and parts handed to owner | Collection time |
| Awaiting collection | Work ended; object still on site | Contact attempt and next date |
| Referred | Desk could not complete the work | Limit explained to owner |
## 5. Closing and next-session notes
At 12:15, pause new intake and finish the records already open. Count the unfinished objects and compare that count with the open-ticket list. A difference is investigated before the room is locked; it is not carried forward as an unexplained adjustment.
Leave three things for the next opening pair: the supply count, a list of carried-over ticket IDs, and one short note about anything that changed in the room. A detailed story is unnecessary when a precise record will do. "Labels moved to Drawer B" is more useful than "We reorganized a little."
For a quick return to intake, use Recording an object. The record template is part of this handbook and needs no online account. For the format of the fictional session archive, see [Archive note][archive].
## References
[^records]: Harbor Bench internal training note, "Corrections remain visible," fictional document supplied for this handbook, April 2026.
[archive]: https://example.invalid/harbor-bench/archive "Fictional reference; no external validation requested"
- Read your context and instructions
- Compiled the parallax document publisher
- Generated the UI component
Fictional demonstration from an actual local trial. This is not a real customer result. Local links and machine-specific paths are displayed as text.
Created the finished handbook as self-contained HTML, editable Markdown, and a four-page Letter PDF. Production notes record the checks and formatting decisions.
The prose, numbers, procedure order, warning, and code are preserved. The supplied diagram is embedded; both Check-in sections have separate working contents links. No external resources are required to display the HTML.
Checked source fidelity, table/code contents, internal navigation, desktop/mobile/print rendering, and PDF text/page size. All four final PDF pages were rendered and visually inspected. External reference links were preserved but not visited. Nothing was distributed or uploaded.
publication.html
<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Harbor Bench Repair Handbook</title><style>:root{--ink:#15364c;--teal:#267e82}body{font:17px/1.65 system-ui,sans-serif;margin:0;background:#eef3f5;color:#203744}main{max-width:820px;padding:48px 40px;margin:auto;background:white}h1,h2,h3{color:var(--ink);line-height:1.25}h1{font-size:38px}h2{margin-top:1.6em;font-size:25px}h3{font-size:20px}nav{background:#edf5f5;padding:12px 24px;margin:25px 0}nav h2{font-size:18px;margin:0}nav ol{columns:2;padding-left:20px}.level-3{font-size:14px}.byline{color:#4a6673}a{color:#176d78;overflow-wrap:anywhere}table{border-collapse:collapse;width:100%;font-size:14px}th{background:#15364c;color:white}th,td{border:1px solid #c8d8de;padding:9px;text-align:left;vertical-align:top}tr:nth-child(even){background:#f1f6f7}.table-wrap{overflow:auto}blockquote{border-left:4px solid var(--teal);margin:22px 0;padding:3px 18px;background:#edf5f5}pre{padding:18px;background:#eef2f4;white-space:pre-wrap;overflow-wrap:anywhere;font:14px/1.6 monospace}code{overflow-wrap:anywhere}p{overflow-wrap:anywhere}figure{margin:25px 0}figure img{display:block;max-width:100%;height:auto}.asset-gap{display:block;border:2px dashed #8c6a36;background:#fff8e9;padding:18px;margin:20px 0;color:#664914;overflow-wrap:anywhere}.editorial{background:#fff1cd;color:#674b10;padding:2px 4px}sup a{font-size:12px}@media(max-width:550px){main{padding:25px 18px}h1{font-size:30px}nav ol{columns:1}}@media print{@page{size:Letter;margin:18mm}body{background:white;font-size:10.5pt;line-height:1.5}main{max-width:none;padding:0}nav{background:white}nav a{color:#15364c;text-decoration:none}h1{font-size:24pt}h2{font-size:16pt;break-after:avoid}h3{font-size:12pt;break-after:avoid}.pagebreak,.chapter{break-before:page}.table-wrap{overflow:visible}table{font-size:9.5pt}thead{display:table-header-group}tr,figure,blockquote{break-inside:avoid}td,th{padding:6px}pre{font-size:9pt;white-space:pre-wrap;overflow-wrap:anywhere}p{orphans:3;widows:3}a{color:inherit}}nav ol{list-style:none;padding-left:0}.level-3{margin-left:18px}</style></head><body><main><h1 id="harbor-bench-repair-handbook">Harbor Bench Repair Handbook</h1><p class="byline">Harbor Bench Volunteer Team · Edition 1</p><nav aria-label="Contents"><h2>Contents</h2><ol><li class="level-2"><a href="#1-opening-the-desk">1. Opening the desk</a></li><li class="level-3"><a href="#check-in">Check-in</a></li><li class="level-2"><a href="#2-recording-an-object">2. Recording an object</a></li><li class="level-3"><a href="#check-in-2">Check-in</a></li><li class="level-2"><a href="#3-passing-work-between-volunteers">3. Passing work between volunteers</a></li><li class="level-2"><a href="#4-returning-an-object">4. Returning an object</a></li><li class="level-2"><a href="#5-closing-and-next-session-notes">5. Closing and next-session notes</a></li><li class="level-2"><a href="#references">References</a></li></ol></nav>
<p>This handbook describes an invented neighborhood repair desk. Its procedures are fictional training material, not instructions for electrical repair. The desk's job is to make the next action clear: record the object, name the person responsible for it, and return it with an understandable account of the work.</p>
<p>The handbook is for volunteers who share one room on Saturday mornings. A customer may meet three people during a visit, but should not have to explain the same problem three times. The record travels with the object. If the record is unclear, the next volunteer asks for clarification before treating an assumption as a fact.</p>
<h2 id="1-opening-the-desk">1. Opening the desk</h2>
<p>The opening pair arrives at 08:30. One person prepares the intake table while the other checks the supply drawer. They compare their notes at 08:45 and open the doors at 09:00. The timing leaves a short interval to fix missing labels before customers arrive.</p>
<p>Use a new date sheet for each session. Carry over unfinished work by its existing ticket ID; do not create a second ticket merely because an object returned the following week. A new problem on the same object can be recorded as a linked follow-up rather than overwriting the original description.</p>
<div class="table-wrap"><table>
<thead>
<tr>
<th>Item</th>
<th align="right">Opening quantity</th>
<th align="right">Reorder when below</th>
<th>Storage location</th>
</tr>
</thead>
<tbody><tr>
<td>Paper ticket sleeves</td>
<td align="right">30</td>
<td align="right">8</td>
<td>Drawer A</td>
</tr>
<tr>
<td>Removable labels</td>
<td align="right">60</td>
<td align="right">15</td>
<td>Drawer B</td>
</tr>
<tr>
<td>Small parts bags</td>
<td align="right">24</td>
<td align="right">6</td>
<td>Shelf 2</td>
</tr>
<tr>
<td>Return envelopes</td>
<td align="right">18</td>
<td align="right">4</td>
<td>Shelf 3</td>
</tr>
</tbody></table></div>
<p>The quantities are counts of individual items, not packs. Record what is actually present; an unopened pack with an unknown count is marked "count pending." A supply total should never be made to look complete by substituting a guess.</p>
<h3 id="check-in">Check-in</h3>
<p>Ask each volunteer which station they will cover. A person may help elsewhere later, but the opening sheet should identify one initial station so that everyone knows where to ask for help. Record the handover when a station changes hands.</p>
<ol>
<li>Write the session date and the two opening volunteers' names.</li>
<li>Count the four supply items in the table.</li>
<li>Place blank ticket sleeves beside the intake pen.</li>
<li>Put the unfinished-work tray on the shelf behind the desk.</li>
<li>Confirm that each carried-over object has its original ticket.</li>
</ol>
<blockquote>
<p>Stop intake if an object has no owner contact record. Label it "identity unresolved" and ask the session lead to resolve it before work begins.</p>
</blockquote>
<h2 id="2-recording-an-object">2. Recording an object</h2>
<p>Describe what arrived before describing what might be wrong. "Blue wooden drawer, left handle loose" helps the next person recognize an object. "Needs fixing" does not. Use the customer's account for the reported problem and label a volunteer's explanation as a working hypothesis.</p>
<p>The intake volunteer writes the ticket ID on both the sleeve and the small parts bag. If no small parts are removed, the bag remains empty with the ticket until return. This small duplication prevents a screw or bracket from becoming an unexplained item in the drawer at closing time.</p>
<p><figure><img src="data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI3MjAiIGhlaWdodD0iMTgwIiB2aWV3Qm94PSIwIDAgNzIwIDE4MCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsbGVkYnk9InRpdGxlIGRlc2MiPgogIDx0aXRsZSBpZD0idGl0bGUiPkhhcmJvciBCZW5jaCB0aWNrZXQgZmxvdzwvdGl0bGU+CiAgPGRlc2MgaWQ9ImRlc2MiPlRocmVlIGNvbm5lY3RlZCBzdGF0aW9uczogSW50YWtlLCBXb3JrLCBhbmQgUmV0dXJuLiBUaGUgdGlja2V0IHN0YXlzIHdpdGggdGhlIG9iamVjdC48L2Rlc2M+CiAgPHJlY3Qgd2lkdGg9IjcyMCIgaGVpZ2h0PSIxODAiIHJ4PSIxMiIgZmlsbD0iI2VlZjZmNiIvPgogIDxnIGZpbGw9IiMxNTM2NGMiPjxyZWN0IHg9IjMwIiB5PSI0NSIgd2lkdGg9IjE4MCIgaGVpZ2h0PSI3MCIgcng9IjEwIi8+PHJlY3QgeD0iMjcwIiB5PSI0NSIgd2lkdGg9IjE4MCIgaGVpZ2h0PSI3MCIgcng9IjEwIi8+PHJlY3QgeD0iNTEwIiB5PSI0NSIgd2lkdGg9IjE4MCIgaGVpZ2h0PSI3MCIgcng9IjEwIi8+PC9nPgogIDxnIHN0cm9rZT0iIzI2N2U4MiIgc3Ryb2tlLXdpZHRoPSI1IiBmaWxsPSJub25lIj48cGF0aCBkPSJNMjE4IDgwSDI1NE0yNDQgNzBMMjU0IDgwTDI0NCA5MCIvPjxwYXRoIGQ9Ik00NTggODBINDk0TTQ4NCA3MEw0OTQgODBMNDg0IDkwIi8+PC9nPgogIDxnIGZpbGw9IiNmZmZmZmYiIGZvbnQtZmFtaWx5PSJzYW5zLXNlcmlmIiBmb250LXNpemU9IjIzIiB0ZXh0LWFuY2hvcj0ibWlkZGxlIj48dGV4dCB4PSIxMjAiIHk9Ijg4Ij5JbnRha2U8L3RleHQ+PHRleHQgeD0iMzYwIiB5PSI4OCI+V29yazwvdGV4dD48dGV4dCB4PSI2MDAiIHk9Ijg4Ij5SZXR1cm48L3RleHQ+PC9nPgogIDx0ZXh0IHg9IjM2MCIgeT0iMTUwIiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBmaWxsPSIjMTUzNjRjIiBmb250LWZhbWlseT0ic2Fucy1zZXJpZiIgZm9udC1zaXplPSIxOCI+VGhlIHRpY2tldCBzdGF5cyB3aXRoIHRoZSBvYmplY3QuPC90ZXh0Pgo8L3N2Zz4K" alt="Ticket flow from intake through work and return"></figure></p>
<p>Figure 1. The ticket accompanies the object through all three stations. A return is recorded even when no repair was attempted.</p>
<h3 id="check-in-2">Check-in</h3>
<p>The customer confirms the description and the preferred contact route. Read the short description aloud if the handwriting is difficult to interpret. A correction belongs on the record immediately; it should not wait for the next volunteer to discover the discrepancy.</p>
<p>Use this plain-text record format. Keep the field names unchanged when copying it into a shared note:</p>
<pre><code class="language-text">ticket_id: HB-0042
received_at: 2026-04-18 09:20
object: blue wooden drawer
reported_problem: left handle loose
owner_confirmed: yes
next_station: assessment
</code></pre>
<h2 id="3-passing-work-between-volunteers">3. Passing work between volunteers</h2>
<p>A handover answers three questions: what changed, what remains uncertain, and what should happen next. Avoid a vague status such as "almost done." If a part is missing, name it. If a check was not performed, say that it was not performed.</p>
<p>Use one sentence for the current condition and one for the next action. For example: "The handle is attached, but the drawer has not been checked in its cabinet. Ask the owner to confirm fit before closing the ticket." This wording separates a completed action from an untested result.</p>
<p>Do not erase a failed attempt. Cross out an incorrect note with a single line on paper, or append a correction in the digital record. A later volunteer may need to know which approach was already tried and why it was abandoned.<sup id="ref-records"><a href="#note-records">1</a></sup></p>
<div class="pagebreak" aria-hidden="true"></div>
<h2 id="4-returning-an-object">4. Returning an object</h2>
<p>Return begins with the ticket, not the appearance of the object. Check that the ID on the sleeve matches the object and any bag of loose parts. Explain what was done using the same plain language used at intake. If the team could not complete the work, name the limit without turning it into a promise about another provider.</p>
<p>Invite the owner to compare the result with the recorded problem. Record their response as a response, not as independent proof that every possible issue has been resolved. Close the ticket only when the object and all associated parts have left the desk or an explicit collection arrangement has been recorded.</p>
<div class="table-wrap"><table>
<thead>
<tr>
<th>Return status</th>
<th>Meaning</th>
<th>Required note</th>
</tr>
</thead>
<tbody><tr>
<td>Collected</td>
<td>Object and parts handed to owner</td>
<td>Collection time</td>
</tr>
<tr>
<td>Awaiting collection</td>
<td>Work ended; object still on site</td>
<td>Contact attempt and next date</td>
</tr>
<tr>
<td>Referred</td>
<td>Desk could not complete the work</td>
<td>Limit explained to owner</td>
</tr>
</tbody></table></div>
<h2 id="5-closing-and-next-session-notes">5. Closing and next-session notes</h2>
<p>At 12:15, pause new intake and finish the records already open. Count the unfinished objects and compare that count with the open-ticket list. A difference is investigated before the room is locked; it is not carried forward as an unexplained adjustment.</p>
<p>Leave three things for the next opening pair: the supply count, a list of carried-over ticket IDs, and one short note about anything that changed in the room. A detailed story is unnecessary when a precise record will do. "Labels moved to Drawer B" is more useful than "We reorganized a little."</p>
<p>For a quick return to intake, use <a href="#2-recording-an-object">Recording an object</a>. The record template is part of this handbook and needs no online account. For the format of the fictional session archive, see <a href="https://example.invalid/harbor-bench/archive" title="Fictional reference; no external validation requested">Archive note</a>.</p>
<h2 id="references">References</h2>
<section aria-label="Notes"><ol><li id="note-records">Harbor Bench internal training note, "Corrections remain visible," fictional document supplied for this handbook, April 2026. <a href="#ref-records" aria-label="Back to note reference">Back</a></li></ol></section></main></body></html>
manuscript.md
---
title: Harbor Bench Repair Handbook
author: Harbor Bench Volunteer Team
edition: 1
language: en
---
# Harbor Bench Repair Handbook
This handbook describes an invented neighborhood repair desk. Its procedures are fictional training material, not instructions for electrical repair. The desk's job is to make the next action clear: record the object, name the person responsible for it, and return it with an understandable account of the work.
The handbook is for volunteers who share one room on Saturday mornings. A customer may meet three people during a visit, but should not have to explain the same problem three times. The record travels with the object. If the record is unclear, the next volunteer asks for clarification before treating an assumption as a fact.
## 1. Opening the desk
The opening pair arrives at 08:30. One person prepares the intake table while the other checks the supply drawer. They compare their notes at 08:45 and open the doors at 09:00. The timing leaves a short interval to fix missing labels before customers arrive.
Use a new date sheet for each session. Carry over unfinished work by its existing ticket ID; do not create a second ticket merely because an object returned the following week. A new problem on the same object can be recorded as a linked follow-up rather than overwriting the original description.
| Item | Opening quantity | Reorder when below | Storage location |
| --- | ---: | ---: | --- |
| Paper ticket sleeves | 30 | 8 | Drawer A |
| Removable labels | 60 | 15 | Drawer B |
| Small parts bags | 24 | 6 | Shelf 2 |
| Return envelopes | 18 | 4 | Shelf 3 |
The quantities are counts of individual items, not packs. Record what is actually present; an unopened pack with an unknown count is marked "count pending." A supply total should never be made to look complete by substituting a guess.
### Check-in
Ask each volunteer which station they will cover. A person may help elsewhere later, but the opening sheet should identify one initial station so that everyone knows where to ask for help. Record the handover when a station changes hands.
1. Write the session date and the two opening volunteers' names.
2. Count the four supply items in the table.
3. Place blank ticket sleeves beside the intake pen.
4. Put the unfinished-work tray on the shelf behind the desk.
5. Confirm that each carried-over object has its original ticket.
> Stop intake if an object has no owner contact record. Label it "identity unresolved" and ask the session lead to resolve it before work begins.
## 2. Recording an object
Describe what arrived before describing what might be wrong. "Blue wooden drawer, left handle loose" helps the next person recognize an object. "Needs fixing" does not. Use the customer's account for the reported problem and label a volunteer's explanation as a working hypothesis.
The intake volunteer writes the ticket ID on both the sleeve and the small parts bag. If no small parts are removed, the bag remains empty with the ticket until return. This small duplication prevents a screw or bracket from becoming an unexplained item in the drawer at closing time.
!Ticket flow from intake through work and return
Figure 1. The ticket accompanies the object through all three stations. A return is recorded even when no repair was attempted.
### Check-in
The customer confirms the description and the preferred contact route. Read the short description aloud if the handwriting is difficult to interpret. A correction belongs on the record immediately; it should not wait for the next volunteer to discover the discrepancy.
Use this plain-text record format. Keep the field names unchanged when copying it into a shared note:
```text
ticket_id: HB-0042
received_at: 2026-04-18 09:20
object: blue wooden drawer
reported_problem: left handle loose
owner_confirmed: yes
next_station: assessment
```
## 3. Passing work between volunteers
A handover answers three questions: what changed, what remains uncertain, and what should happen next. Avoid a vague status such as "almost done." If a part is missing, name it. If a check was not performed, say that it was not performed.
Use one sentence for the current condition and one for the next action. For example: "The handle is attached, but the drawer has not been checked in its cabinet. Ask the owner to confirm fit before closing the ticket." This wording separates a completed action from an untested result.
Do not erase a failed attempt. Cross out an incorrect note with a single line on paper, or append a correction in the digital record. A later volunteer may need to know which approach was already tried and why it was abandoned.[^records]
<!-- pagebreak -->
## 4. Returning an object
Return begins with the ticket, not the appearance of the object. Check that the ID on the sleeve matches the object and any bag of loose parts. Explain what was done using the same plain language used at intake. If the team could not complete the work, name the limit without turning it into a promise about another provider.
Invite the owner to compare the result with the recorded problem. Record their response as a response, not as independent proof that every possible issue has been resolved. Close the ticket only when the object and all associated parts have left the desk or an explicit collection arrangement has been recorded.
| Return status | Meaning | Required note |
| --- | --- | --- |
| Collected | Object and parts handed to owner | Collection time |
| Awaiting collection | Work ended; object still on site | Contact attempt and next date |
| Referred | Desk could not complete the work | Limit explained to owner |
## 5. Closing and next-session notes
At 12:15, pause new intake and finish the records already open. Count the unfinished objects and compare that count with the open-ticket list. A difference is investigated before the room is locked; it is not carried forward as an unexplained adjustment.
Leave three things for the next opening pair: the supply count, a list of carried-over ticket IDs, and one short note about anything that changed in the room. A detailed story is unnecessary when a precise record will do. "Labels moved to Drawer B" is more useful than "We reorganized a little."
For a quick return to intake, use Recording an object. The record template is part of this handbook and needs no online account. For the format of the fictional session archive, see [Archive note][archive].
## References
[^records]: Harbor Bench internal training note, "Corrections remain visible," fictional document supplied for this handbook, April 2026.
[archive]: https://example.invalid/harbor-bench/archive "Fictional reference; no external validation requested"
production-notes.md
# Production notes
Generated a complete handbook as self-contained HTML, editable Markdown, and a four-page Letter PDF. The original Markdown remains byte-identical in both `manuscript.md` and `source-original.md`. No prose or measurements were rewritten. The supplied SVG was inspected, checked for executable content, and embedded as a data URI; no remote resource is needed to display the handbook.
The dark-blue/teal layout preserves the original chapter order and the explicit break before chapter 4. The two Check-in headings have unique targets (`check-in` and `check-in-2`). The contents links were clicked in Chromium. Reference-style links resolve to their supplied destinations; the footnote has a backlink. External hyperlinks were preserved but not visited or validated.
Executed checks: source-copy equality; twenty prose blocks checked against visible text; original warning wording and five-step order checked; code block and table contents compared with browser DOM; duplicate IDs, broken anchors, page errors, and page-width overflow checked at 1280 px, 390 px, and print media. No network resource requests occurred. PDF text was read back, Letter page dimensions and nonempty pages checked, and all four final PDF pages rendered with Poppler and visually inspected. No clipping, missing diagram, or blank page was observed. The whitespace before the explicit chapter-4 break preserves the source's requested page break.
The contents initially displayed redundant automatic numbering beside chapter numbers; the list style was corrected and the HTML/PDF rerendered before final inspection. Target Word/EPUB readers were not involved. No upload, distribution, or publication occurred.
publication.html
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Give finished writing a clean, readable layout. Turn your article, handbook or multi-chapter manuscript into a document with working navigation and consistent formatting.
What you get
- A self-contained HTML document you can open in a browser.
- Editable Markdown source with headings, tables, images and references preserved.
- Print styling and a list of missing images or unresolved references to check.
Bring your manuscript and any images. DOCX, PDF and EPUB exports are optional and require suitable tools in your assistant.
Load this reusable skill through Agensi in an assistant with file tools. It formats your supplied content; it does not write a missing book or publish it to a store. AI service fees are separate.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scanned
Verified clean 3 days ago
- Passed all security checks, Safe to install
Listed3 days ago