Update to SVG Lab
Snapshot Oct 31, 2026 · 01:22 UTC · version 1.1.0
Collection source: downloaded plugin package.
Instructions updated for setup
Skill instructions — Now says: --- name: setup description: Use when the user runs setup for SVG Lab or asks how to get started. Checks the SVG Lab account, says where designs are saved,...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 10 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 29, 2026 · 12:07 UTC
--- name: setup description: Use when the user runs setup for SVG Lab or asks how to get started. Checks the SVG Lab account, says where designs are saved, asks what to design and starts the first design with the live view. --- # S...
Oct 31, 2026 · 01:22 UTC
--- name: setup description: Use when the user runs setup for SVG Lab or asks how to get started. Checks the SVG Lab account, says where designs are saved, asks what to design and starts the first design with the live view. --- # Set up...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,13 +1,15 @@ ---- -name: setup -description: Use when the user runs setup for SVG Lab or asks how to get started. Checks the SVG Lab account, says where designs are saved, asks what to design and starts the first design with the live view. ---- - -# Set up SVG Lab - -1. Call account_status with {}. If the account has no access to the SVG Lab MCP, say so plainly, give the plans link the reply carries, and stop there. Do not recommend or push a plan. -2. Tell the user in two short sentences how it works: SVG Lab designs in their own SVG Lab editor on SVG Lab's servers, and every design is saved to My Projects in their SVG Lab account, where they can open it at svglab.app and edit it by hand. -3. If the plugin was installed during a task, carry on with that task. Otherwise ask one question: what do they want to design (app screens, a website, a logo or icons, an illustration)? -4. Plan with the user once, as docs guide plan-with-the-user describes: the questions the request leaves open, each with a recommended answer. Ask in the same message whether the screens use photos, drawn illustrations or a mix, with a recommendation. -5. Start with new_project. Its reply carries live_view: give the user the live view link so they watch the design being made. -6. For every drawn illustration, follow the drawing-from-references skill. +--- +name: setup +description: Use when the user runs setup for SVG Lab or asks how to get started. Checks the SVG Lab account, says where designs are saved, asks what to design and starts the first design with the live view. +--- + +# Set up SVG Lab + +1. Call account_status with {}. If the account has no access to the SVG Lab MCP, say so plainly, give the plans link the reply carries, and stop there. Do not recommend or push a plan. If the reply has heads_up, tell the user that first. +2. Tell the user in two short sentences how it works: SVG Lab designs in their own SVG Lab editor on SVG Lab's servers, and every design is saved to My Projects in their SVG Lab account, where they can open it at svglab.app and edit it by hand. +3. If the plugin was installed during a task, carry on with that task. Otherwise ask one question: what do they want to design (app screens, a website, a logo or icons, an illustration)? +4. Every design starts with new_project. Its first reply lists the questions to ask, as docs guide plan-with-the-user describes, and a line about ChatGPT's permission prompt: ask them all in one message, each with a recommended answer, then call new_project again with the answers. The screens are built with SVG Lab's tools, never as a picture from your own image generation. +5. Imagery follows the user's ChatGPT plan, which you know. On ChatGPT Free, offer stock photos only and recommend them: no drawn illustrations, because ChatGPT Free makes only a few images a day. On other plans, ask whether the screens use photos, drawn illustrations or a mix, with a recommendation. +6. new_project's reply carries live_view: give the user the live view link so they watch the design being made. +7. For every drawn illustration, follow the drawing-from-references skill. +8. At the end, say what was made, anything not finished and why, the project link, and the credits left.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\r\nname: setup\r\ndescription: Use when the user runs setup for SVG Lab or asks how to get started. Checks the SVG Lab account, says where designs are saved, asks what to design and starts the first design with the live view.\r\n---\r\n\r\n# Set up SVG Lab\r\n\r\n1. Call account_status with {}. If the account has no access to the SVG Lab MCP, say so plainly, give the plans link the reply carries, and stop there. Do not recommend or push a plan.\r\n2. Tell the user in two short sentences how it works: SVG Lab designs in their own SVG Lab editor on SVG Lab's servers, and every design is saved to My Projects in their SVG Lab account, where they can open it at svglab.app and edit it by hand.\r\n3. If the plugin was installed during a task, carry on with that task. Otherwise ask one question: what do they want to design (app screens, a website, a logo or icons, an illustration)?\r\n4. Plan with the user once, as docs guide plan-with-the-user describes: the questions the request leaves open, each with a recommended answer. Ask in the same message whether the screens use photos, drawn illustrations or a mix, with a recommendation.\r\n5. Start with new_project. Its reply carries live_view: give the user the live view link so they watch the design being made.\r\n6. For every drawn illustration, follow the drawing-from-references skill.\r\n""---\nname: setup\ndescription: Use when the user runs setup for SVG Lab or asks how to get started. Checks the SVG Lab account, says where designs are saved, asks what to design and starts the first design with the live view.\n---\n\n# Set up SVG Lab\n\n1. Call account_status with {}. If the account has no access to the SVG Lab MCP, say so plainly, give the plans link the reply carries, and stop there. Do not recommend or push a plan. If the reply has heads_up, tell the user that first.\n2. Tell the user in two short sentences how it works: SVG Lab designs in their own SVG Lab editor on SVG Lab's servers, and every design is saved to My Projects in their SVG Lab account, where they can open it at svglab.app and edit it by hand.\n3. If the plugin was installed during a task, carry on with that task. Otherwise ask one question: what do they want to design (app screens, a website, a logo or icons, an illustration)?\n4. Every design starts with new_project. Its first reply lists the questions to ask, as docs guide plan-with-the-user describes, and a line about ChatGPT's permission prompt: ask them all in one message, each with a recommended answer, then call new_project again with the answers. The screens are built with SVG Lab's tools, never as a picture from your own image generation.\n5. Imagery follows the user's ChatGPT plan, which you know. On ChatGPT Free, offer stock photos only and recommend them: no drawn illustrations, because ChatGPT Free makes only a few images a day. On other plans, ask whether the screens use photos, drawn illustrations or a mix, with a recommendation.\n6. new_project's reply carries live_view: give the user the live view link so they watch the design being made.\n7. For every drawn illustration, follow the drawing-from-references skill.\n8. At the end, say what was made, anything not finished and why, the project link, and the credits left.\n"Full snapshot data
{
"description": "Use when the user runs setup for SVG Lab or asks how to get started. Checks the SVG Lab account, says where designs are saved, asks what to design and starts the first design with the live view.",
"included_files": [],
"name": "setup",
"skill_md_contents": "---\nname: setup\ndescription: Use when the user runs setup for SVG Lab or asks how to get started. Checks the SVG Lab account, says where designs are saved, asks what to design and starts the first design with the live view.\n---\n\n# Set up SVG Lab\n\n1. Call account_status with {}. If the account has no access to the SVG Lab MCP, say so plainly, give the plans link the reply carries, and stop there. Do not recommend or push a plan. If the reply has heads_up, tell the user that first.\n2. Tell the user in two short sentences how it works: SVG Lab designs in their own SVG Lab editor on SVG Lab's servers, and every design is saved to My Projects in their SVG Lab account, where they can open it at svglab.app and edit it by hand.\n3. If the plugin was installed during a task, carry on with that task. Otherwise ask one question: what do they want to design (app screens, a website, a logo or icons, an illustration)?\n4. Every design starts with new_project. Its first reply lists the questions to ask, as docs guide plan-with-the-user describes, and a line about ChatGPT's permission prompt: ask them all in one message, each with a recommended answer, then call new_project again with the answers. The screens are built with SVG Lab's tools, never as a picture from your own image generation.\n5. Imagery follows the user's ChatGPT plan, which you know. On ChatGPT Free, offer stock photos only and recommend them: no drawn illustrations, because ChatGPT Free makes only a few images a day. On other plans, ask whether the screens use photos, drawn illustrations or a mix, with a recommendation.\n6. new_project's reply carries live_view: give the user the live view link so they watch the design being made.\n7. For every drawn illustration, follow the drawing-from-references skill.\n8. At the end, say what was made, anything not finished and why, the project link, and the credits left.\n"
}SHA-256 of public snapshot: ccdaa76cbda9dd722d53606e4a961bbc6aeb54781c17048613bfe5ee89516653