Paprika

**Judgement:** Paprika is a solid, focused skill for accessing a user’s own Paprika Recipe Manager data (recipes, meal plans, grocery lists) via a CLI with JSON output. It is well-suited for agents that provide personalized cooking and meal-planning assistance, not for general web recipe search. **Strengths:** - Good coverage of the core Paprika reading flows: list/search recipes, view a specific recipe, view meal plans, and inspect grocery lists. - JSON mode (`--json`) makes it straightforward to parse results reliably in an automated agent. - Simple, well-documented commands with realistic usage examples that map directly to common user requests. **Key Risks / Limitations:** - Requires Paprika cloud sync and valid Paprika credentials (email + password or prior auth). This introduces privacy/security considerations in how credentials are stored and passed; they should be configured server-side, not solicited from users directly. - Read-centric: there is no visible support for creating or modifying recipes, meal plans, or grocery lists, so the agent is limited to retrieval and summarization. - The skill operates only on the user’s Paprika data; it cannot fetch arbitrary internet recipes, which may confuse users if not clearly communicated. **Recommended Scenarios:** - Personalized cooking assistants where the user already relies on Paprika for recipe storage and meal planning. - Meal planning and shopping helpers that surface “what’s on my plan” and “what’s on my grocery list” and can summarize or transform that data. - Contextual cooking help based on the user’s own recipes (e.g., suggest dinners from their “Dinner” category, or extract ingredients to build a shopping strategy). Use this skill when the user explicitly references “my recipes”, “my Paprika”, stored meal plans, or grocery lists, and when the environment is already configured with Paprika credentials and cloud sync enabled.