Plan2meal

Commands

Recipe Commands

Grocery List Commands

Help

Usage Examples

Adding a Recipe

plan2meal add https://www.allrecipes.com/recipe/12345/pasta

Output:

✅ Recipe added successfully!

📖 Recipe Details
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Name: Classic Pasta
Source: allrecipes.com
Method: firecrawl-json (credit used)
Time: 15 min prep + 20 min cook

🥘 Ingredients (4 servings)
• 1 lb pasta
• 2 cups marinara sauce
• 1/2 cup parmesan

🔪 Steps
1. Boil water...

Searching Recipes

plan2meal search pasta

Creating a Grocery List

plan2meal list-create Weekly Shopping

Adding Recipe to List

plan2meal list-add <listId> <recipeId>

Recipe Limits

The free tier allows up to 5 recipes. You'll receive a warning when approaching this limit.

Authentication Architecture

How It Works

Skill Owner Setup (one-time):

1. Configure your Plan2Meal backend API URL in the skill
2. Your backend handles all OAuth (GitHub credentials configured in Convex environment variables)
3. Your backend is configured with the Convex URL (stays private)

End User Flow:

1. User sends a command (e.g., plan2meal list)
2. Skill responds with a link to your Plan2Meal sign-in page (app.plan2meal.com/sign-in)
3. User clicks the link and authenticates with GitHub via your web app
4. Your backend (using Convex Auth) handles the GitHub OAuth flow
5. After successful authentication, your backend shows the user a session token
6. User copies the token and sends it back to Telegram (or types token: <token>)
7. Skill validates the token with your backend and stores it securely

Backend Processing:

• Your Plan2Meal backend uses Convex Auth with GitHub provider
• GitHub OAuth credentials are stored in Convex environment variables (never exposed)
• After GitHub auth, backend generates a session token for the user
• Skill sends session token to your backend API for all requests
• Your backend validates the token and makes Convex API calls on behalf of the user
• Convex URL is never exposed to users or the skill

Key Points

• Public Skill: No secrets in the skill - safe to publish on ClawdHub
• Backend OAuth: All OAuth credentials (GitHub, Convex) stay in your backend
• User Identification: Your backend maps session tokens to Convex users internally
• Privacy: Convex URL stays private in your backend only
• Security: Session tokens are validated with your backend before use

License

MIT