🍳 Intermediate Recipe Submission #1

[taniandjerry]

🍳 Intermediate Recipe Submission

Thanks for contributing to the Goose Cookbook!
This issue represents an Intermediate Recipe Slot (6–7 points).

Intermediate recipes use 2 extensions working together. They may also include 1 sub-recipe for specialization.

---

✅ Acceptance Criteria

Your recipe will be accepted if it:

• Uses 2 extensions (e.g., GitHub + Summarizer, Browser + Developer).
• Demonstrates integration or chaining between the extensions.
• Optionally includes 1 sub-recipe for a specialized task.
• Includes required YAML fields: title, description, instructions, and at least one activity.
• Validates against the Recipe Reference Guide.
• Has been tested locally in Goose.
• Follows the Cookbook Contributing Guide.

---

📋 Submission Checklist

Before opening your PR, make sure you've:

• [ ] Chosen a unique and descriptive filename (e.g., meeting-summarizer.yaml).
• [ ] Matched the recipe title to the filename.
• [ ] Confirmed your YAML validates.
• [ ] Listed both extensions in your recipe.
• [ ] Included clear instructions and at least one activity.
• [ ] Verified the recipe works locally in Goose.

---

✨ Inspiration Examples

(These are just ideas — you can submit any real workflow you've used with Goose.)

• GitHub PR summarizer (GitHub + Summarizer).
• Meeting transcript summarizer (Filesystem + Summarizer).
• Data cleaner (Filesystem + Developer).
• API caller + formatter (Web Browser + Developer).

---

📚 Resources

• Recipe Reference Guide
• Cookbook Contributing Guide
• Goose Recipes Tutorial (YouTube)
• Existing Recipes

---

🚀 Next Steps

1. Claim this slot by commenting .take below.
2. Fork the repository and create a new branch for your recipe.
3. Create your recipe file in:
   documentation/src/pages/recipes/data/recipes/
4. Create a pull request from your fork and reference this issue in the PR description.

🎉 Once merged, your recipe will be added to the Goose Cookbook!

---

💡 Tips for Success

• Base your recipe on a real workflow you've tried with Goose.
• Show how the two extensions interact — don't just use them separately.
• Keep the workflow useful and reproducible.

[shalmonTitree]

.take

[github-actions[bot]]

Thanks for taking this issue! Let us know if you have any questions!

[the-matrixneo]

.take

[github-actions[bot]]

The issue you are trying to assign to yourself is already assigned.

[the-matrixneo]

Hey @taniandjerry!

If this issue is open, do let me know. I would like to work on this.

[taniandjerry]

Hey @the-matrixneo ! Thank you so much for commenting. I've gone ahead and assigned this issue to you, as @shalmonTitree hasn't responded and resolved their DCO check to merge their contribution. As we approach the end of Hacktoberfest, I'm reopening issues to help get contributors that are working hard to get more chances to earn more points, and worry less about taking one issue on at a time. Thank you!

[taniandjerry]

Hi @the-matrixneo - wanted to give you a gentle nudge and let you know that with Hacktoberfest ending officially on the 31st (this Friday), you will need all of your PRs merged before that time to count both towards our repo and the official event. The team will need time to finalize PRs and rankings, so any open issues without a PR ready for review will be closed tomorrow (the 30th). So please be sure to submit ahead of time if you'd like this issue to count!