snack-batching

Consolidates weekly Slack snack requests into a budget-checked vendor cart pending approval.

20.2k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill snack-batching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: snack-batching
Source: https://github.com/kortix-ai/suna/tree/main/packages/starter/templates/marketplace/runtime/skills/snack-batching
Command: npx skills add https://github.com/kortix-ai/suna --skill snack-batching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Office snack requests arrive scattered across a Slack channel all week, and someone has to manually collect them, deduplicate them, stay within budget, and place the order. This Skill automates that entire cycle while keeping a human approval gate before any money is spent.

Core Features & Use Cases

  • Request Collection and Consolidation: Reads snack-request shortcut submissions from a Slack channel since the last batch, merges duplicate items, and always adds configurable standing staples like coffee and sparkling water.
  • Budget-Aware Cart Building: Searches the preferred vendor, builds a cart within the weekly budget, trims low-demand items when over budget, and flags substitutions for unavailable products.
  • Approval-Gated Checkout: Posts a draft order to the channel and only checks out after an explicit written approval in the thread; questions or emoji reactions never trigger a purchase.
  • Use Case: An office manager sets a weekly cron; every Friday the agent posts a consolidated draft order in the office channel, and the order is placed only after the manager replies "approved".

Quick Start

Ask the agent to run this week's snack batch for the office channel and post the draft order for approval.

Frequently Asked Questions about snack-batching

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate weekly office snack orders from Slack requests?

Set up a Slack shortcut in your office channel for submissions and a weekly cron that triggers the batching run. The agent collects all requests since the last draft, consolidates duplicates, builds a cart within budget, and posts it for approval.

How does the snack order approval workflow prevent accidental purchases?

Checkout only happens after an explicit written approval in the draft's Slack thread, such as "approved" or "yes, place it". Emoji reactions, questions, or silence never trigger a purchase, and unanswered drafts roll into the next batch.

What happens when the snack order exceeds the weekly budget?

The agent trims non-staple items with the fewest requesters first, breaking ties by cheapest price, until the cart fits the budget. Standing staples like coffee and sparkling water are never trimmed to make room.

Can I change the vendor, budget, or standing staple items?

Yes, the preferred vendor, weekly budget, and standing staples are defined directly in the SKILL.md file as editable values. Changes should be proposed as a reviewed change request rather than ad hoc overrides during a run.

What happens if a requested snack item is unavailable from the vendor?

The agent substitutes the closest matching product from the same vendor and flags the substitution in the draft post. If no reasonable substitute exists, it drops the line item and flags the omission instead of guessing.