Plan2meal

**Quick judgment** Plan2Meal is a focused, production-oriented skill for managing recipes and grocery lists tied to the Plan2Meal backend. It appears mature enough for real use (thousands of downloads) and is best suited to users who already rely on the Plan2Meal app and want conversational access to their existing data. **What it does well** - Provides a clear, well-scoped command surface for authenticating and then adding, listing, searching, showing, and deleting recipes. - Handles grocery list lifecycle (create, view, add recipe to list) within the same ecosystem. - Uses OAuth with established identity providers (GitHub required; Google/Apple optional), which is generally safer than handling passwords directly. - Includes explicit routing guardrails, reducing the risk of misusing the skill for generic nutrition or non-Plan2Meal tasks. **Key risks and limitations** - **Backend dependency:** All meaningful operations go through a Convex backend (`CONVEX_URL`, with a shared default if `ALLOW_DEFAULT_BACKEND=true`). Availability and latency depend on that service; outages or misconfiguration will break functionality. - **Privacy/data handling:** User recipe and grocery data are processed on the backend; this is not a local-only skill. Deployers must clearly communicate that data is sent to the configured Convex host and ensure they trust or control that infrastructure. - **Shared default backend option:** If `ALLOW_DEFAULT_BACKEND=true` is used with the shared endpoint, multiple deployments may share infrastructure, which can increase operational and privacy risk unless the operator fully understands and accepts this. - **Auth complexity:** Multiple OAuth environment variables and callback URLs must be set correctly. Misconfiguration will lead to login failures and blocked commands. **Recommended scenarios** - A user already uses the Plan2Meal React Native app and wants to manage their recipes and grocery lists through a conversational interface. - Assistants that help with “what can I cook from my saved recipes?” or “add this new recipe URL and put it on my shopping list” using the user’s existing Plan2Meal data. - Integrations where the operator controls or self-hosts the Convex backend (`CONVEX_URL`) and wants predictable, authenticated access to user recipe/grocery data. **Not recommended / out of scope** - General meal-planning, nutrition advice, or dietary analysis that doesn’t involve the user’s stored Plan2Meal data. - Managing tasks, reminders, or notes in systems other than Plan2Meal (e.g., Apple Reminders, Notes). - Deployments that require strict data-locality or offline processing, since this skill inherently depends on remote backend calls.