@heylemon/lemonade 0.3.7 → 0.3.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/build-info.json
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
c684050231d4a94e46f69c43b39c26d0cf49e6dea297b89aaf5da9baec6086b1
|
package/package.json
CHANGED
package/skills/browser/SKILL.md
CHANGED
|
@@ -28,7 +28,8 @@ Before using browser for any of these services, **use the `lemon-*` CLI tool ins
|
|
|
28
28
|
**Spotify:** Use AppleScript ONLY (see spotify skill). Never use a CLI, never use browser. The native Spotify macOS app is controlled via AppleScript.
|
|
29
29
|
|
|
30
30
|
**When browser fallback is allowed:**
|
|
31
|
-
-
|
|
31
|
+
- If the CLI binary itself is missing ("command not found") or the service is genuinely not connected.
|
|
32
|
+
- If `lemon://connect` fails or OAuth is unavailable for a service (e.g. Jira, Trello, Asana, Figma). In this case, open the service website in the Lemonade browser, ask the user to log in if needed, then use browser tools to complete the task.
|
|
32
33
|
- NEVER because a search returned no results, a user wasn't found, a name didn't match, etc. Those are normal — retry with different input or ask the user.
|
|
33
34
|
|
|
34
35
|
## When to Use Browser
|
|
@@ -19,3 +19,23 @@ The generated skills are placed in `~/.lemonade/skills/` and include:
|
|
|
19
19
|
- Proper authentication tokens
|
|
20
20
|
|
|
21
21
|
If integrations aren't working, restart the Lemon app to regenerate them.
|
|
22
|
+
|
|
23
|
+
## Browser Fallback for Unsupported Integrations
|
|
24
|
+
|
|
25
|
+
Some services (e.g. Jira, Trello, Asana, Figma, ClickUp, Monday.com, Zendesk, Intercom, Shopify, Stripe, Airtable, HubSpot) may not have OAuth configured. When connecting fails or a CLI tool is unavailable for a service:
|
|
26
|
+
|
|
27
|
+
1. **Use the browser to complete the task directly.** Open the service website in the Lemonade browser, ask the user to log in if needed, then use browser tools (navigate, click, type, snapshot) to perform the requested action.
|
|
28
|
+
2. **Don't give up.** If `lemon://connect` fails or the user says it didn't work, immediately switch to browser-based execution instead of telling the user to try again later.
|
|
29
|
+
3. **Common fallback URLs:**
|
|
30
|
+
- Jira: `https://id.atlassian.com` (login), then the user's Jira instance
|
|
31
|
+
- Trello: `https://trello.com`
|
|
32
|
+
- Asana: `https://app.asana.com`
|
|
33
|
+
- Figma: `https://figma.com`
|
|
34
|
+
- ClickUp: `https://app.clickup.com`
|
|
35
|
+
- Monday.com: `https://monday.com`
|
|
36
|
+
- HubSpot: `https://app.hubspot.com`
|
|
37
|
+
- Airtable: `https://airtable.com`
|
|
38
|
+
- Todoist: `https://app.todoist.com`
|
|
39
|
+
- Shopify: `https://admin.shopify.com`
|
|
40
|
+
|
|
41
|
+
**Flow:** Try CLI tool first → if unavailable, offer `lemon://connect` → if connect fails, use browser to do the task.
|