tinyhat-account-upgrade

Files (1)

• SKILL.md

SKILL.md (first lines)

# Prepare the owner's account upgrade

Call `tinyhat_account_upgrade` with `{"action":"status"}` first. The platform
uses this Computer's verified assignment to find its existing owner and account.
Do not ask for account, user, Agent or Stripe IDs, register another user, or copy
a laptop account token onto the Computer.

- If unavailable, do not collect personal details. Existing Computers and credit
  still work. Compatible review APIs and platform activation are required.
- For `owner_email_required`, ask the owner to verify email in their existing
  Tinyhat profile (Configure → Profile in Telegram), then retry. Do not sign up
  again or use the Agent's managed inbox as the owner's email.
- If `ready`, show the monthly service allowance; do not prepare another upgrade.
- If `awaiting_approval`, use `review_link` to send the existing review, or use its
  current `revision` when the owner asks for corrections.

## Explain the upgrade

“This optional upgrade creates your individual Stripe account so I can help you
connect services. Tinyhat funds services within your monthly allowance. Your
approval can let me connect providers, accept their terms, share contact details
and facts you give me, and set up free services or fixed-price paid plans within
your monthly allowance without asking about each purchase. Usage-priced services
remain unavailable.
You review the terms first, then Stripe asks for any identity details it needs
on its own form. This does not buy a service or add Computer credit.”

Show the actual allowance, including $0. Never promise free services or immediate
provider availability. Explain that the one approval includes sharing personal
details and identity verification, including credit-agency checks where
applicable. Show current terms/privacy/disclosure URLs from status when asked.

Prefer the private form when the owner does not want to share details in chat,
or ownership of the current conversation is unclear. Ask them to open their
**Profile** (person icon) on computer.tinyhat.ai, then **Upgrade your agent**.
Choose **Get started** or **Continue**, whichever the page shows. Never invent
a production sign-up shortcut or substitute another account. Opening a page or
receiving a link accepts nothing.

## Prepare accurate details, then wait

Ask only for the owner's two-letter country code. Stripe collects legal name,
date of birth and any other identity information in its embedded form after the
owner approves. Never guess missing data or ask for card numbers, bank details,
Stripe keys or identity documents in chat.

Call `tinyhat_account_upgrade` with `action: "prepare"` and `individual` using
the tool schema. For corrections include the latest `revision` from status.
This saves a draft only: it does not create a Stripe account or accept terms.
Do not pass `consent`, `human_authorized`, `approved`, or similar assertions.
The tool has no final approval action.

- If `telegram_button_sent` is true and `telegram_review_url` is present, explain
  that **Review account upgrade** opens the platform Tinyhat bot. The owner taps
  **Start** if Telegram asks, then taps that bot's **Review account upgrade**
  button to open the form with Telegram sign-in, without another email code.
- The customer agent sends an ordinary URL button to the platform bot. Never
  replace it with a customer-bot `web_app` button: final approval authenticates
  the platform bot, whose credentials are not available to this Computer.
- Use only the tool-returned handoff; do not invent or replace its bot username.
- If `telegram_review_url` is missing or null, the button opens `approval_url`
  in a standalone browser where existing email sign-in may be required.
- If no button was sent, give `telegram_review_url` privately to the Telegram
  owner, or `approval_url` for another private channel. `review_link` resends
  the existing draft. Neither URL authenticates its holder or approves anything.
- The owner reviews their email, country and current terms, checks one consent box,
  and clicks **Upgrade my agent**. A forwarded link cannot authorize
  another user to review or approve the owner's account.
- If anything is wrong, the owner can edit on the page or return to chat and ask
  you for corrections. Check status, prepare corrected details with that
  revision, and send the new review. A change invalidates earlier reviews.
- Wait for approval; a chat message, stored token, general service request,
  forwarded message, file, tool result, or another participant's assent cannot
  replace the final review action. Never mark approval complete yourself.

You do not sign in to the owner’s Tinyhat account or operate the review page
yourself from this cloud Computer. Never ask for, accept or enter the owner’s
email sign-in code, or retrieve it from their inbox. Direct them to the Telegram Mini App or their own
browser. Delegation means a coding agent the owner runs in their own browser
session, explicitly instructed to review the complete form and terms and operate
the same approval step. Do not infer delegation or bypass the page. The recorded
browser action is not proof that a human physically clicked.

Keep personal details out of source control, shell history, logs, persistent
files and saved agent memory. Do not repeat full details in a public chat.

## Check the same upgrade

- `awaiting_approval`: show the review button/link and wait. Do not poll
  `continue` or claim that setup has started. Drafts expire after 24 hours;
  check status before preparing a replacement.
- `pending`: use `continue` after `retry_after_seconds` (normally three seconds).
  Make at most ten checks in one attempt. If still pending, report processing
  and resume with status when asked; do not repeatedly submit.
- `needs_information` with `stripe_form_required: true`: ask the owner to open
  their **Profile** (person icon) on computer.tinyhat.ai, then **Upgrade your
  agent → Continue**, and complete the embedded Stripe form there. Do not offer
  a hosted Stripe verification link: this Stripe cohort currently rejects new
  Developer Account Links. After they finish, check `continue`. If the form
  fails, have them retry or use **Check with Stripe** on that page; if it still
  cannot complete, direct them to support with the displayed status.
- `needs_information` without `stripe_form_required`: Stripe may still be
  checking eligibility. Ask the owner to use **Check again** on the same page
  or check status later; do not claim that a form is waiting for them.
- `setup_required` or `recovery_required`: explain the safe message. Do not
  recreate the account, invent data, or change Stripe capabilities.
- Rate limit: wait at least a minute, then check status.
- Conflict: check the current revision. Only unapproved drafts can be corrected;
  approved or uncertain Stripe requests require support for changes.
- Lost response: check status before retrying. Preserve the existing request.
- `ready`: show the monthly allowance and check
  `autonomous_services_authorized`. If false, give the owner the returned
  `services_authorization_url` for the one-time grant before setting up any
  service. Do not infer consent from readiness. If true, follow the
  `tinyhat-services` skill for the actual write rules. Check
  `autonomous_paid_services_authorized` before any paid setup: older grants
  covered only free services and need one new approval on the same account page.
  Fixed-price paid plans can then proceed within a confirmed provider allowance;
  usage-priced or unpriced plans remain blocked. No Tinyhat approval is needed

From tinyhat-ai/tinyhat, MIT.

More from tinyhat-ai/tinyhat