Update to Dreambooth Studio
Snapshot Nov 3, 2026 · 18:27 UTC · version 2.1.1
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for getting-started
Skill instructions — Now says: it, sign in with Google and approve. The link is Google only; a Google account with the same email as their Dreambooth account connects that account. **Do...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Sep 30, 2026 · 22:57 UTC
it and approve with Google. **Do not call the tool again while waiting.** It returns immediately by design and finishes in the background; calling it again starts a second flow and invalidates the first. Once they say they are done, just...
Nov 3, 2026 · 18:27 UTC
it, sign in with Google and approve. The link is Google only; a Google account with the same email as their Dreambooth account connects that account. **Do not call the tool again while waiting.** It returns immediately by design and fini...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -21,15 +21,15 @@ When they do want to connect, or when they ask something that needs their own data, call `connect_account` **once** and read `status`: -- **`awaiting_approval`** — give them the link, ask them to open it and approve with Google. **Do not call the tool again while waiting.** It returns immediately by design and finishes in the background; calling it again starts a second flow and invalidates the first. Once they say they are done, just answer their question — the other tools start working on their own. +- **`awaiting_approval`** — give them the link, ask them to open it, sign in with Google and approve. The link is Google only; a Google account with the same email as their Dreambooth account connects that account. **Do not call the tool again while waiting.** It returns immediately by design and finishes in the background; calling it again starts a second flow and invalidates the first. Once they say they are done, just answer their question — the other tools start working on their own. -- **`unsupported_here`** — this client does not keep a session between messages, so an in-conversation link would be approved and then forgotten. Do not offer one. Tell them to connect Dreambooth from their client's own connector or app settings instead, and relay the tool's message rather than inventing steps. +- **`use_client_sign_in`** — this client does not keep a session between messages, so an in-conversation link would be approved and then forgotten. Do not offer one. Tell them to connect Dreambooth from their client's own connector or app settings instead (that sign-in takes an email and password or Google), and relay the tool's message rather than inventing steps. - **`already_connected`** — nothing to do; answer the question. Never present a sign-in link that the tool did not give you. -If someone has no Dreambooth account, approving still works: it creates one, with a 14-day Pro trial. Say that when it is relevant, but do not push it on someone who only asked a product question. +If someone has no Dreambooth account, approving still works: it creates one. Do not advertise plans, trials or upgrades, and do not push signing up on someone who only asked a product question. ## Tone
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: getting-started\ndescription: Answer questions from someone who does not have a Dreambooth account yet — what a photobooth business needs, what hardware to buy, how pricing and plans work, how printing and payments are handled — and connect them when they are ready. Use for any product, pricing, hardware or setup question, and whenever someone asks a Dreambooth question before an account is connected.\n---\n\n# Helping someone before they have an account\n\nMost of this can be answered **without connecting anything**. `search_docs` needs no account. Reach for it first and do not ask anyone to sign in to learn what the product does.\n\n## Answer from the documentation, not from memory\n\nCall `search_docs` before answering any question about the product: pricing, plans, packages, hardware, printers, cameras, payments, printing, subscriptions, or troubleshooting. It searches the real Dreambooth documentation.\n\nIf the docs do not cover it, say so plainly rather than filling the gap with a plausible guess. Pricing and hardware answers that turn out to be wrong cost someone real money.\n\nEach result carries a `href`. Link it, so the person can read the full page.\n\n## Only connect when there is a reason\n\nConnecting is for questions about **their own booths** — earnings, sessions, device status. It is not needed to learn about the product.\n\nWhen they do want to connect, or when they ask something that needs their own data, call `connect_account` **once** and read `status`:\n\n- **`awaiting_approval`** — give them the link, ask them to open it and approve with Google. **Do not call the tool again while waiting.** It returns immediately by design and finishes in the background; calling it again starts a second flow and invalidates the first. Once they say they are done, just answer their question — the other tools start working on their own.\n\n- **`unsupported_here`** — this client does not keep a session between messages, so an in-conversation link would be approved and then forgotten. Do not offer one. Tell them to connect Dreambooth from their client's own connector or app settings instead, and relay the tool's message rather than inventing steps.\n\n- **`already_connected`** — nothing to do; answer the question.\n\nNever present a sign-in link that the tool did not give you.\n\nIf someone has no Dreambooth account, approving still works: it creates one, with a 14-day Pro trial. Say that when it is relevant, but do not push it on someone who only asked a product question.\n\n## Tone\n\nThe audience is often a small business owner or an event operator, not an engineer. Prefer plain answers about cost, effort and outcome over feature lists. If a question is really \"is this worth doing\", the honest shape of the answer usually involves what a booth costs to run and what a session earns — both of which are in the docs.\n"
"---\nname: getting-started\ndescription: Answer questions from someone who does not have a Dreambooth account yet — what a photobooth business needs, what hardware to buy, how pricing and plans work, how printing and payments are handled — and connect them when they are ready. Use for any product, pricing, hardware or setup question, and whenever someone asks a Dreambooth question before an account is connected.\n---\n\n# Helping someone before they have an account\n\nMost of this can be answered **without connecting anything**. `search_docs` needs no account. Reach for it first and do not ask anyone to sign in to learn what the product does.\n\n## Answer from the documentation, not from memory\n\nCall `search_docs` before answering any question about the product: pricing, plans, packages, hardware, printers, cameras, payments, printing, subscriptions, or troubleshooting. It searches the real Dreambooth documentation.\n\nIf the docs do not cover it, say so plainly rather than filling the gap with a plausible guess. Pricing and hardware answers that turn out to be wrong cost someone real money.\n\nEach result carries a `href`. Link it, so the person can read the full page.\n\n## Only connect when there is a reason\n\nConnecting is for questions about **their own booths** — earnings, sessions, device status. It is not needed to learn about the product.\n\nWhen they do want to connect, or when they ask something that needs their own data, call `connect_account` **once** and read `status`:\n\n- **`awaiting_approval`** — give them the link, ask them to open it, sign in with Google and approve. The link is Google only; a Google account with the same email as their Dreambooth account connects that account. **Do not call the tool again while waiting.** It returns immediately by design and finishes in the background; calling it again starts a second flow and invalidates the first. Once they say they are done, just answer their question — the other tools start working on their own.\n\n- **`use_client_sign_in`** — this client does not keep a session between messages, so an in-conversation link would be approved and then forgotten. Do not offer one. Tell them to connect Dreambooth from their client's own connector or app settings instead (that sign-in takes an email and password or Google), and relay the tool's message rather than inventing steps.\n\n- **`already_connected`** — nothing to do; answer the question.\n\nNever present a sign-in link that the tool did not give you.\n\nIf someone has no Dreambooth account, approving still works: it creates one. Do not advertise plans, trials or upgrades, and do not push signing up on someone who only asked a product question.\n\n## Tone\n\nThe audience is often a small business owner or an event operator, not an engineer. Prefer plain answers about cost, effort and outcome over feature lists. If a question is really \"is this worth doing\", the honest shape of the answer usually involves what a booth costs to run and what a session earns — both of which are in the docs.\n"
Full snapshot data
{
"description": "Answer questions from someone who does not have a Dreambooth account yet — what a photobooth business needs, what hardware to buy, how pricing and plans work, how printing and payments are handled — and connect them when they are ready. Use for any product, pricing, hardware or setup question, and whenever someone asks a Dreambooth question before an account is connected.",
"included_files": [],
"name": "getting-started",
"skill_md_contents": "---\nname: getting-started\ndescription: Answer questions from someone who does not have a Dreambooth account yet — what a photobooth business needs, what hardware to buy, how pricing and plans work, how printing and payments are handled — and connect them when they are ready. Use for any product, pricing, hardware or setup question, and whenever someone asks a Dreambooth question before an account is connected.\n---\n\n# Helping someone before they have an account\n\nMost of this can be answered **without connecting anything**. `search_docs` needs no account. Reach for it first and do not ask anyone to sign in to learn what the product does.\n\n## Answer from the documentation, not from memory\n\nCall `search_docs` before answering any question about the product: pricing, plans, packages, hardware, printers, cameras, payments, printing, subscriptions, or troubleshooting. It searches the real Dreambooth documentation.\n\nIf the docs do not cover it, say so plainly rather than filling the gap with a plausible guess. Pricing and hardware answers that turn out to be wrong cost someone real money.\n\nEach result carries a `href`. Link it, so the person can read the full page.\n\n## Only connect when there is a reason\n\nConnecting is for questions about **their own booths** — earnings, sessions, device status. It is not needed to learn about the product.\n\nWhen they do want to connect, or when they ask something that needs their own data, call `connect_account` **once** and read `status`:\n\n- **`awaiting_approval`** — give them the link, ask them to open it, sign in with Google and approve. The link is Google only; a Google account with the same email as their Dreambooth account connects that account. **Do not call the tool again while waiting.** It returns immediately by design and finishes in the background; calling it again starts a second flow and invalidates the first. Once they say they are done, just answer their question — the other tools start working on their own.\n\n- **`use_client_sign_in`** — this client does not keep a session between messages, so an in-conversation link would be approved and then forgotten. Do not offer one. Tell them to connect Dreambooth from their client's own connector or app settings instead (that sign-in takes an email and password or Google), and relay the tool's message rather than inventing steps.\n\n- **`already_connected`** — nothing to do; answer the question.\n\nNever present a sign-in link that the tool did not give you.\n\nIf someone has no Dreambooth account, approving still works: it creates one. Do not advertise plans, trials or upgrades, and do not push signing up on someone who only asked a product question.\n\n## Tone\n\nThe audience is often a small business owner or an event operator, not an engineer. Prefer plain answers about cost, effort and outcome over feature lists. If a question is really \"is this worth doing\", the honest shape of the answer usually involves what a booth costs to run and what a session earns — both of which are in the docs.\n"
}SHA-256 of public snapshot: c9e688d761359ddb26adb5d1cac73a1e9c4e0b5077326c19ae1242fedb7782b0