Update to FLORA

{
  "description": "Runs once after the FLORA plugin is installed. Confirms the FLORA sign-in, shows the skill catalog, and gets the user started on a new idea or an existing project.",
  "included_files": [],
  "name": "flora-onboarding",
  "skill_md_contents": "---\nname: flora-onboarding\ndescription: Runs once after the FLORA plugin is installed. Confirms the FLORA sign-in, shows the skill catalog, and gets the user started on a new idea or an existing project.\n---\n\n# Welcome to FLORA\n\nKeep this short: confirm access, show what is possible, then hand control to the user.\n\n`flora_discover_skills` and every other `flora_*` name below are tools on the FLORA app. Call them directly as tool calls — they are not resources or files, so never search resources for them, and never tell the user FLORA is unavailable without calling one.\n\n1. **Confirm access.** Call `flora_list_workspaces`. On success, use `current_workspace_id` when returned; otherwise use the sole workspace, or ask which to use if several are returned. If no workspaces are returned, explain the blocker and stop. Greet the user and name the selected workspace. On an auth error, ask them to finish connecting FLORA and stop.\n2. **Show the catalog.** Call `flora_discover_skills` with no name. It opens the skills gallery, so do not repeat the list in text.\n3. **Offer two ways in,** each as a prompt the user could type:\n   - **New work:** two starters drawn from the catalog, such as \"Generate 6 product variants of this photo\" or \"Turn this sheet of SKUs into one image per row\".\n   - **An existing project:** \"Open my <project> project\" or paste a canvas link. When they do, call `flora_discover_skills` with `name: \"flora-open-project\"` and follow it.\n4. **Stop and wait.** Do not generate anything during onboarding; generation spends credits.\n"
}