People Data
sickn33/agentic-awesome-skills
Research LinkedIn professional profiles and public business-contact data, including email/phone lookup, people search, and YouTube channel business-email discovery.
Practical skills for cooking and hosting groups of 10-50 people.
$ npx skills add LeoYeAI/openclaw-master-skills --skill hosting-feeding-groups -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills hosting-feeding-groups --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hosting-feeding-groups .claude/skills/hosting-feeding-groups && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hosting-feeding-groups" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/hosting-feeding-groups into .claude/skills/hosting-feeding-groups/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hosting-feeding-groups", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/hosting-feeding-groupsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill hosting-feeding-groups -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills hosting-feeding-groups --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/hosting-feeding-groups .agents/skills/hosting-feeding-groups && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hosting-feeding-groups" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/hosting-feeding-groups into .agents/skills/hosting-feeding-groups/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hosting-feeding-groups", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill hosting-feeding-groups -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills hosting-feeding-groups --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/hosting-feeding-groups .cursor/skills/hosting-feeding-groups && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hosting-feeding-groups" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/hosting-feeding-groups into .cursor/skills/hosting-feeding-groups/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hosting-feeding-groups", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/hosting-feeding-groups--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill hosting-feeding-groups -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills hosting-feeding-groups --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/hosting-feeding-groups .gemini/skills/hosting-feeding-groups && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hosting-feeding-groups" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/hosting-feeding-groups into .gemini/skills/hosting-feeding-groups/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hosting-feeding-groups", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills hosting-feeding-groupsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill hosting-feeding-groups -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/hosting-feeding-groups .github/skills/hosting-feeding-groups && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hosting-feeding-groups" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/hosting-feeding-groups into .github/skills/hosting-feeding-groups/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hosting-feeding-groups", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill hosting-feeding-groups -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills hosting-feeding-groups --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/hosting-feeding-groups .opencode/skills/hosting-feeding-groups && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hosting-feeding-groups" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/hosting-feeding-groups into .opencode/skills/hosting-feeding-groups/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hosting-feeding-groups", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
hosting-feeding-groupsPractical skills for cooking and hosting groups of 10-50 people.
Hosting Feeding Groups is an agent skill from LeoYeAI/openclaw-master-skills. Practical skills for cooking and hosting groups of 10-50 people. Use when someone needs to feed a crowd for events, community gatherings, family reunions, block parties, or regular group meals on a budget.
Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).
The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and agent-adaptation).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
fsis.usda.govservsafe.comfeedingamerica.organthropic.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Hosting Feeding Groups loads about 5.2k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 779 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 779 words, ~5,158 tokens.
.claude/skills/hosting-feeding-groups/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Feeding 4 people is cooking. Feeding 20 is logistics. The difference isn't just multiplying ingredients -- it's timing, equipment, food safety, and setup. Most people either panic and overspend, or wing it and run out of food at a party. Neither has to happen. This skill covers the practical mechanics of feeding 10-50 people well, safely, and cheaply. The core move: pick foods that are forgiving, scale reliably, and serve themselves.
# Localization note
- Portion sizes vary by culture (US portions run large, ~8oz protein; many other
countries serve 4-6oz portions with more sides)
- Common crowd-feeding foods differ: rice and curry (South/Southeast Asia),
asado/BBQ (South America), tagine (North Africa), stews (West Africa),
pierogi/dumplings (Eastern Europe), rice and beans (Caribbean/Latin America)
- Temperature units: Fahrenheit in US, Celsius elsewhere
140F = 60C (hot holding), 40F = 4C (cold holding)
- Food safety regulations for community events vary by jurisdiction
- Swap unit measurements: cups/ounces/pounds vs. grams/kilograms/liters
- Dietary restriction prevalence varies (celiac awareness higher in Northern Europe,
vegetarian baseline higher in India)Agent action: Teach the user how recipe scaling actually works -- because it's not just multiplication.
RECIPE SCALING -- WHAT MULTIPLIES AND WHAT DOESN'T
THE BASIC RULE:
- Original recipe serves 6, you need to serve 24
- Multiplier = 24 / 6 = 4x
WHAT SCALES LINEARLY (multiply directly):
- Meat, beans, rice, pasta, vegetables
- Butter, oil, cream
- Canned goods (tomatoes, broth, coconut milk)
- Sugar in baked goods (mostly)
WHAT DOES NOT SCALE LINEARLY:
- SALT: Use 70-80% of the multiplied amount, then taste and adjust
(Example: Recipe calls for 1 tsp salt, 4x = 4 tsp, use 3 tsp and taste)
- SPICES AND HERBS: Use 60-75% of the multiplied amount
Spices get stronger in larger volumes -- start low, taste, adjust
- LIQUID IN SOUPS/STEWS: Use 80% of multiplied amount
Less evaporation per volume in a bigger pot
- GARLIC: Use 75% of multiplied amount (gets sharper at scale)
- CHILI/HOT PEPPERS: Use 50-60% of multiplied amount
Heat compounds unpredictably -- you can always add more
- BAKING POWDER/SODA: For batches over 3x, reduce to 70% and
test one batch first. Chemistry changes at scale.
- THICKENERS (flour, cornstarch): Use 80% of multiplied amount
THE GOLDEN RULE: You can always add more. You can't take it out.
Season incrementally at scale.Agent action: Help the user choose dishes that work for crowds. The criteria: holds well, serves itself, scales reliably, and is affordable.
MENU PLANNING FOR CROWDS
THE BEST CROWD FOODS SHARE THESE TRAITS:
- One-pot or sheet-pan (minimal timing coordination)
- Good at room temperature or held warm for 1-2 hours
- Self-serve friendly (people can plate themselves)
- Cheap per serving
- Forgiving (won't ruin if overcooked by 15 minutes)
WORST CROWD FOODS:
- Anything that must be served immediately (souffle, eggs, fried food)
- Anything requiring individual plating
- Anything with a narrow doneness window (steaks, fish fillets)
- Anything with expensive per-serving costs ($$$)
MENU STRUCTURE FOR 20 PEOPLE:
1. ONE main protein dish (chili, pulled pork, chicken thighs)
2. ONE starch (rice, pasta, bread, tortillas, potatoes)
3. ONE vegetable side (roasted vegetables, coleslaw, green salad)
4. ONE "extra" (bread/rolls, chips and salsa, fruit)
5. ONE dessert (optional but appreciated -- brownies, cookies)
PORTION PLANNING:
- Protein: 6-8 oz per adult (1/3 to 1/2 pound raw)
- Starch: 1 cup cooked per person
- Vegetable/salad: 1/2 cup to 1 cup per person
- Total food: Plan for 1 to 1.25 pounds of food per adult
- Always make 15-20% more than headcount (seconds, surprises, leftovers)
- If alcohol is served, people eat 10-15% less food
- If it's a potluck, plan as if 1/3 of promised dishes won't show upAgent action: Show the user specific cost breakdowns for feeding groups at different budget levels.
COST PER HEAD ANALYSIS (US prices, 2026 approximate)
$3/HEAD -- THE BARE BONES:
- Rice and beans with salsa and tortillas
- Pasta with red sauce, garlic bread
- Soup and bread (potato soup, minestrone, chili)
- Bulk oatmeal bar with toppings (for breakfast events)
$5/HEAD -- THE SWEET SPOT:
- Taco bar (ground beef or chicken, shells, toppings)
- Chili bar (chili, rice, cheese, sour cream, cornbread)
- Pasta bar (2 sauces, garlic bread, salad)
- Sheet-pan chicken thighs, rice, roasted vegetables
$8/HEAD -- IMPRESSIVE ON A BUDGET:
- Pulled pork (buy pork shoulder on sale ~$2/lb), coleslaw, rolls
- Baked potato bar with chili, broccoli, cheese, sour cream
- Chicken and rice with 2 sides and rolls
- Enchilada assembly (can prep day before)
$12-15/HEAD -- NICE EVENT:
- BBQ spread (2 meats, 3 sides, rolls, dessert)
- Italian spread (lasagna, salad, garlic bread, dessert)
- Fajita bar with guacamole and all the fixings
WHERE TO SAVE:
- Buy protein in bulk or on sale and freeze (pork shoulder, chicken
thighs, ground beef/turkey)
- Costco/Sam's Club for cheese, tortillas, bread, condiments
- Restaurant supply stores (open to public) for disposable
serving ware -- much cheaper than grocery store party supplies
- Generic/store brand for anything going into a big pot
- Root vegetables (potatoes, carrots, onions) are always cheapAgent action: Help the user create a reverse timeline so everything is ready at the same time.
REVERSE TIMELINE METHOD
TARGET SERVING TIME: ___:___ (fill in)
Work backwards from there.
EXAMPLE: Taco bar for 20, serving at 6:00 PM
5:45 Set out toppings (cheese, sour cream, lettuce, salsa, etc.)
5:40 Warm tortillas (oven at 300F, wrapped in foil, 10 min)
5:30 Final taste/season check on meat
5:00 Rice into rice cooker (or finish stovetop rice)
4:30 Start browning ground beef (season at 4:45)
4:00 Prep all toppings (chop lettuce, dice tomatoes, open cans,
grate cheese, slice limes)
3:00 Go to store for anything missing
DAY BEFORE: Make salsa. Grate cheese. Prep any slow-cook items.
GENERAL TIMING RULES:
- Anything that can be prepped the day before, should be
- Starches (rice, pasta) take 20-45 min, start 1 hour before serving
- Proteins take 30 min to 6 hours depending on method
- Slow cooker proteins: start 6-8 hours before serving
- Oven proteins: start 1.5-3 hours before serving
- Stovetop proteins: start 45-90 minutes before serving
- Toppings/sides: prep 2 hours before, set out 15 min before
- ALWAYS add 30-minute buffer. Something will take longer than planned.
DELEGATING:
- Give helpers the prep work (chopping, grating, setting up)
- Keep the cooking to 1-2 people who know the recipes
- Assign ONE person to manage drinks and ice
- Assign ONE person to manage setup (tables, plates, utensils)Agent action: Help the user figure out what equipment they need and how to get it without buying everything.
EQUIPMENT NEEDS BY GROUP SIZE
10-15 PEOPLE (your normal kitchen can handle this):
- Your largest pot (8+ quart)
- 2 sheet pans
- Rice cooker or large pot for starch
- Serving spoons and tongs
16-30 PEOPLE (borrow or supplement):
- Second large pot (borrow from a neighbor)
- Slow cooker or Instant Pot (6-8 quart)
- Chafing dishes for keeping food warm (buy disposable: $8-12 each
at restaurant supply or Amazon)
- Extra sheet pans (2-4 total)
- Large mixing bowls for salads and toppings
- Insulated beverage dispenser for coffee/tea
30-50 PEOPLE (you're running a small operation):
- Multiple slow cookers (borrow 3-4 from friends)
- Turkey roaster/electric roaster oven ($30-50, reusable, holds
20+ quarts -- the secret weapon for large group cooking)
- Folding tables for serving line ($30 each or borrow)
- Full chafing dish setup (3-4 stations)
- Large coolers for cold items and drinks
- Possibly a second grill if doing BBQ
WHERE TO GET EQUIPMENT WITHOUT BUYING:
1. Borrow from neighbors (tool-lending network from mutual aid skill)
2. Church/community center kitchens (many let you use facilities)
3. Ask the group -- "I'm cooking, who can bring a slow cooker?"
4. Restaurant supply stores sell cheap basics
5. Rental companies rent chafing dishes, tables, chairs ($50-100/event)Agent action: Cover the food safety basics that matter when serving groups. Foodborne illness at a group event is a real risk.
FOOD SAFETY -- NON-NEGOTIABLE AT SCALE
THE DANGER ZONE: 40F - 140F (4C - 60C)
Food in this range grows bacteria rapidly.
Maximum time food can sit in the danger zone: 2 HOURS.
If the ambient temperature is above 90F/32C: 1 HOUR.
HOT FOOD: Keep above 140F/60C
- Chafing dishes with sterno cans
- Slow cookers on "warm" setting
- Oven at lowest setting (170F) with door cracked
- Check with a food thermometer every 30 minutes
COLD FOOD: Keep below 40F/4C
- Serve on ice (fill a tray with ice, nest serving bowl in it)
- Coolers with ice for backup supplies
- Don't put everything out at once -- refill from cold storage
THE 2-HOUR RULE:
After 2 hours at room temperature, toss it. No exceptions.
This is the rule that prevents making 20 people sick.
Set a timer when food goes out.
HAND WASHING:
- Set up a hand-washing station if no convenient sink
(water jug with spigot + soap + paper towels)
- Every cook washes hands before starting
- After touching raw meat, wash before touching anything else
LEFTOVERS:
- Refrigerate within 2 hours of serving
- Divide into shallow containers (cools faster)
- Label with date
- Use within 3-4 days or freeze
ALLERGIES:
- Label every dish with its major allergens
- Keep at least one dish that is: gluten-free, dairy-free, nut-free
- When in doubt, print ingredient lists and put them next to each dishAgent action: Provide these tested recipes that scale reliably to 20 servings.
RECIPE 1: ALL-PURPOSE CHILI (serves 20)
5 lbs ground beef or turkey (or 4 cans black beans for vegetarian)
3 large onions, diced
8 cloves garlic, minced
4 cans (28 oz each) crushed tomatoes
4 cans (15 oz each) kidney beans, drained
4 cans (15 oz each) black beans, drained
3 tbsp chili powder
2 tbsp cumin
1 tbsp smoked paprika
2 tsp salt (adjust to taste)
1 tsp black pepper
Optional: 2 chipotle peppers in adobo sauce (adds smoky heat)
Brown meat in batches in largest pot. Add onions, cook 5 min.
Add garlic, spices, cook 1 min. Add tomatoes and beans.
Simmer 45-90 minutes. The longer, the better.
Serve with: shredded cheese, sour cream, diced onion, cornbread.
Cost: ~$3.50/serving with toppings.
---
RECIPE 2: PULLED PORK (serves 20-25)
8-10 lbs pork shoulder (bone-in is cheaper and more flavorful)
Your favorite BBQ rub (or: 2 tbsp brown sugar, 2 tbsp paprika,
1 tbsp each garlic powder, onion powder, black pepper, salt,
1 tsp cayenne)
2 cups apple cider vinegar
2 cups BBQ sauce (plus more for serving)
Rub pork shoulder all over with spice rub. Refrigerate overnight.
Slow cooker: Add vinegar, cook on low 10-12 hours.
Oven: 275F in covered Dutch oven for 6-8 hours.
When it falls apart with a fork, it's done.
Shred with two forks. Mix in BBQ sauce. Serve on buns.
Cost: ~$2-3/serving (buy shoulder on sale at $1.50-2/lb).
---
RECIPE 3: PASTA BAR (serves 20)
4 lbs pasta (penne or rigatoni -- holds sauce better than spaghetti)
SAUCE 1 -- Red: 4 jars (24 oz) marinara + 1 lb browned Italian sausage
SAUCE 2 -- Alfredo: 3 jars (15 oz) Alfredo sauce, heated
TOPPINGS: Parmesan, red pepper flakes, fresh basil, garlic bread
Cook pasta in batches (your pot probably holds 2 lbs max).
Slightly undercook (1 min less than package says) -- it'll keep
cooking in the warm serving vessel. Toss with a little oil to
prevent sticking. Keep warm in covered pot or chafing dish.
Cost: ~$3/serving with garlic bread.
---
RECIPE 4: TACO BAR (serves 20)
5 lbs ground beef or chicken thighs
3 packets taco seasoning (or make your own: 3 tbsp chili powder,
2 tbsp cumin, 1 tbsp garlic powder, 1 tbsp onion powder,
2 tsp salt, 1 tsp paprika, 1/2 tsp cayenne)
40 taco shells or 40 small flour/corn tortillas (or both)
TOPPINGS: shredded lettuce, diced tomatoes, shredded cheese,
sour cream, salsa, diced onion, cilantro, lime wedges,
hot sauce, canned jalapenos
Brown meat in batches. Add seasoning and 1.5 cups water per batch.
Simmer 10 min until thickened. Keep warm in slow cooker.
Set up assembly line: shells/tortillas > meat > toppings.
Cost: ~$4/serving with all toppings.
---
RECIPE 5: SHEET-PAN CHICKEN AND RICE (serves 20)
10 lbs chicken thighs (bone-in, skin-on -- cheapest and most flavor)
Olive oil, salt, pepper, garlic powder, paprika, Italian seasoning
6 cups uncooked rice (makes ~18 cups cooked)
3 lbs mixed vegetables (broccoli, bell peppers, zucchini, onions)
Season chicken generously. Spread on sheet pans (5-6 thighs per pan,
you'll need 3-4 pans). Roast at 425F for 35-40 minutes until
internal temp hits 165F. On separate pans, roast vegetables with
oil, salt, pepper at 400F for 20-25 minutes.
Cook rice in batches or use rice cooker(s).
Cost: ~$4-5/serving (buy thighs in bulk at $1-2/lb).Agent action: If the user is coordinating a potluck rather than cooking everything themselves, provide a system that prevents the "15 desserts and no entree" problem.
POTLUCK COORDINATION SYSTEM
ASSIGN CATEGORIES, NOT SPECIFIC DISHES:
Tell each person which category to bring, not what specific dish.
This avoids duplicates while letting people make what they're good at.
CATEGORIES AND RATIOS (for 20 people, 12 contributors):
- Main dish / protein: 3 people (each brings enough for 8-10)
- Starch / carb side: 2 people (each brings enough for 10-12)
- Vegetable / salad: 3 people (each brings enough for 8-10)
- Bread / snack / appetizer: 2 people
- Dessert: 2 people
- Drinks: Host provides, or assign 1 person
WHAT THE HOST PROVIDES:
- Plates, utensils, napkins, cups
- Ice and coolers
- Serving utensils (many people forget these)
- Table setup and serving area
- At minimum: one main dish as backup
POTLUCK COMMUNICATION TEMPLATE (send to group):
"[Event Name] Potluck -- [Date, Time, Location]
We have [X] people coming. To avoid 12 desserts and no main course,
I'm assigning categories. Please bring enough of your dish to
serve [8-10] people.
Your assignment: [CATEGORY]
Please bring your dish in/on something you don't mind losing track
of (or label it with your name). Bring your own serving utensil.
If your dish contains common allergens (nuts, dairy, gluten, shellfish),
please put a note card next to it.
Reply with what you're planning to bring so we can avoid duplicates.
See you there!"
TRACKING (simple):
Name | Category | Bringing | Serves
______________|_____________|___________________|_______
| | |hosting:
event_type: null
guest_count: null
budget: null
budget_per_head: null
menu_planned: false
dishes:
- name: null
serves: null
prep_time: null
cost: null
timeline_created: false
equipment_needed: []
equipment_secured: []
dietary_restrictions: []
potluck_assignments: []
shopping_list_created: false
day_before_prep_done: falsetriggers:
- name: timeline_creation
condition: "menu_planned IS true AND timeline_created IS false"
action: "You've planned your menu but don't have a cooking timeline yet. Let's build a reverse timeline from your serving time so everything is ready together."
- name: shopping_list
condition: "menu_planned IS true AND shopping_list_created IS false"
action: "Menu is set. Let's build a shopping list with quantities scaled for your group size, organized by store section."
- name: day_before_reminder
condition: "event is tomorrow AND day_before_prep_done IS false"
action: "Your event is tomorrow. Here's what to prep tonight: chop vegetables, make sauces, marinate proteins, set up the serving area, and confirm your equipment is clean and ready."
- name: food_safety_timer
condition: "event is in progress"
action: "Food safety check: has any dish been sitting out for more than 90 minutes? If approaching 2 hours, either refresh from hot/cold storage or remove from the serving line."© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/hosting-feeding-groups of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Hosting Feeding Groups next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hosting Feeding Groups this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.2k | Automated safety check: Pass | MIT | |
| People Datasickn33/agentic-awesome-skills | 47k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Groupsparcadei/Continuous-Claude-v3 | 3.9k | 1 repos | ~956 | Automated safety check: Notes | MIT | |
| Feedsalsk1992/CloddsBot | 3k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Escaping Containers To Hostmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Cross Host Federationruvnet/ruflo | 74k | — | ~1.1k | Automated safety check: Pass | MIT |
sickn33/agentic-awesome-skills
Research LinkedIn professional profiles and public business-contact data, including email/phone lookup, people search, and YouTube channel business-email discovery.
parcadei/Continuous-Claude-v3
Problem-solving strategies for groups in abstract algebra. An agent skill from parcadei/Continuous-Claude-v3.
alsk1992/CloddsBot
Real-time market data feeds from 8 prediction market platforms
mukul975/Anthropic-Cybersecurity-Skills
Exploits privileged pods, host mounts, runC CVEs, and exposed Docker sockets to break out of a container and reach the underlying host during an authorized container-security assessment.
ruvnet/ruflo
Join and operate a signed cross-host agentbbs federation, and coordinate work claims across nodes.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Practical skills for cooking and hosting groups of 10-50 people. Hosting Feeding Groups is an agent skill from LeoYeAI/openclaw-master-skills. Practical skills for cooking and hosting groups of 10-50 people.
Hosting Feeding Groups fits situations like: someone needs to feed a crowd for events; community gatherings; family reunions; regular group meals on a budget.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill hosting-feeding-groups -a claude-code`. Or copy the skill folder (skills/hosting-feeding-groups in LeoYeAI/openclaw-master-skills) into .claude/skills/hosting-feeding-groups in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill hosting-feeding-groups -a codex`. Or copy the skill folder (skills/hosting-feeding-groups in LeoYeAI/openclaw-master-skills) into .agents/skills/hosting-feeding-groups in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill hosting-feeding-groups -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hosting-feeding-groups, .gemini/skills/hosting-feeding-groups, .github/skills/hosting-feeding-groups and .opencode/skills/hosting-feeding-groups in your project.
SKILL.md names no scripts, command-line tools or credentials: Hosting Feeding Groups is instructions for the agent only. Our summary lists: Node.js.
SKILL.md names 4 domains. As links in the text: fsis.usda.gov, servsafe.com, feedingamerica.org and anthropic.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Hosting Feeding Groups is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.2k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Hosting Feeding Groups: People Data (sickn33/agentic-awesome-skills, 47k stars), Groups (parcadei/Continuous-Claude-v3, 3.9k stars), Feeds (alsk1992/CloddsBot, 3k stars) and Escaping Containers To Host (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.