More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Manual Handover — a user manual with real screenshots

    1

    Walks your running app role by role, one action per step, captures real screenshots, and writes the manual your client's staff can follow alone, without passwords, customer data or developer jargon.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Manual Handover — a user manual with real screenshots

    Manual Handover — a user manual with real screenshots

    Example session with this skill installed

    Write a user manual for my client's staff. Test site is running locally; there are owner and staff test accounts.

    • Read your context and instructions
    • Compiled the manual handover

    Bean & Kettle Back Office: User manual

    Version 2026-11-09 · For shop owner and staff

    Fictional example. Every step below was performed in the included example back office, and every screenshot (11 in the full manual) was taken from it.

    Before you start

    • Web address: the back-office link you received with your account.
    • Browser: a current version of Chrome or Edge.
    • Your account: your email address is your sign-in name. Your password is sent to you separately; keep it private.
    RoleWhat you can do
    OwnerSee all orders, refund orders, see monthly revenue
    StaffSee all orders

    Try it in 10 minutes (owner)

    1. Sign in and look at the order list. 👀 Notice: the coloured label shows where each order is: paid, shipped, cancelled or refunded.
    2. Choose paid in the Status filter. 👀 Notice: these are the orders still waiting to be shipped.
    3. Open

    Revenue. 👀 Notice: revenue counts paid and shipped orders only, so cancelled and refunded orders never inflate your numbers.

    Chapter 1: Owner

    1.1 Sign in

    Goal: open the back office with your owner account.

    1. Open the back-office web address. The Sign in page appears. [screenshot: the sign-in form]
    2. Type your email in Email and your password in Password.
    3. Click Sign in. [screenshot: Sign in button highlighted]

    You should see: the order list, with Signed in as

    Owner at the top right and two menus:

    Orders and

    Revenue.

    If this happens: "Email or password is incorrect." This appears when the email is not a back-office account or the password field is left empty. Check the email for typos and fill in both fields.

    1.2 Find orders by status

    1. On Orders, open the Status list.
    2. Choose paid. [screenshot: only paid orders shown; the count updates to 3]

    You should see: only orders with the orange paid label.
    Tip: choose All statuses to see every order again.

    1.3 Refund an order

    Goal: return the money for an order that was paid or shipped.

    1. On Orders, click the order row (for example #754). The order page opens.
    2. Click Refund order. [screenshot: the button appears only for paid or shipped orders]
    3. A confirmation box shows the amount. Check it, then click

    Yes, refund. Click

    Cancel if you opened the wrong order.

    You should see: a green message, "Order #754 has been refunded. The customer will see the money in 5–10 working days.", and the status changes to

    refunded.

    Tip: the refund is taken off that month's revenue straight away. In the example, October went from 86 orders / 10,981.00 to 85 orders / 10,837.00.

    1.4 See monthly revenue

    1. Click Revenue in the top menu.

    You should see: one row per month with the number of orders and the revenue.
    How it's counted: paid and shipped orders only. Cancelled orders, refunded orders and the shop's internal test accounts are left out.

    1.5 Sign out

    Click Sign out at the top right. Always sign out on a shared computer.

    Chapter 2: Staff

    1. Sign in as in 1.1 with your staff email.

    You should see: Signed in as Staff, and only the Orders menu.

    1. Click an order to see its details. Filtering works as in 1.2.

    Things that work differently than you might expect

    • Staff don't see Revenue, and have no Refund button. This is intentional: money matters are owner-only.
    • The Refund button is missing on some orders. Cancelled and already-refunded orders can't be refunded.

    The money is returned in the payment provider's dashboard. Refund order records the refund in the back office; the owner then returns the money in the provider's dashboard.

    • In this version a refund is not kept after the page is reloaded. This is fixed before go-live, and this section is re-checked then.
    • In this version's sign-in, the password is not checked. The real password check is added before go-live.
    • In this version the Revenue screen shows fixed sample figures. They are replaced by live figures before go-live.

    When something goes wrong

    1. Refresh the page (Ctrl + F5).
    2. Sign out and sign in again.
    3. Still stuck? Send your contact a screenshot of the screen and the time it happened.

    Not covered

    • Password reset: this version has no "forgot password" option; ask your contact to reset it.
    • Changing product prices: not part of this version of the back office.

    Delivered as manual.md plus a print-ready HTML with all screenshots embedded.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The system works, but the client calls you every time they need to do something. Manual Handover writes the manual that stops those calls.

    • Real screenshots, never mock-ups: it drives your test environment (browser tools or Playwright), one screenshot per screen change, with the button to click highlighted.
    • One action per step, button names exactly as on screen, and the result the reader should see at the end of every task.
    • Per role: a chapter for each role (owner, staff, admin…), plus a "Try it in 10 minutes" path for the decision-maker.
    • Things that work differently than expected: intentional behaviour that looks like a bug, explained before the client reports it.
    • Honest scope: tasks it couldn't walk through are listed under Not covered, not written from imagination.
    • Safe to hand over: no passwords, tokens, real customer data, install commands or internal notes.

    If a step fails during the walk-through, it stops and tells you; it won't document a broken path as if it worked. (In the included example the walk-through stopped when the revenue screen didn't update after a refund; the example app was fixed and walked again before the manual was written.)

    Every manual also comes as a styled single-file HTML with screenshots embedded, print-ready for PDF. Writes in your language (English, Chinese, Japanese and more).

    Works with Claude Code, Codex CLI, Gemini CLI, Cursor and other agents that can read files and run shell commands.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.

    Steps it can't drive (file pickers, email inboxes, payments, hardware) are done by you or listed as not covered.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by 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 scan

    Security scan passed 8 days ago

    Software
    Python

    Permissions

    Terminal / Shell
    Browser
    Network Access
    Write Files
    Read Files

    Opens your local or test site in a browser to take screenshots, runs the included render script, and writes the manual into your project folder. It uses test accounts you name and never stores their passwords.

    Listed8 days ago

    What's inside

    Frequently Asked Questions

    No. It uses your agent's browser tools if available, or Playwright with its own Chromium or your installed Chrome/Edge.

    No. Accounts are named by role; passwords are never written.

    It walks through read-only screens only and lists the write actions as steps for you to confirm, so nothing is changed in production.

    Every manual also comes as a print-ready HTML file you can save as PDF.

    A software company in Taiwan that builds, hands over and rescues business systems. Contact: youllook@gmail.com

    New in Technical Documentation