Skip to content

Feedback on your meal-prep-efficiency-guru skill #17

Description

@RichardHightower

I took a look at your meal-prep-efficiency-guru skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 88/100, which puts you solidly in B territory. This is based on Anthropic's skills best practices rubric. Your Progressive Disclosure Architecture is strong (28/30) — the modular structure works well. But you've got two high-severity issues that are genuinely worth tackling: the skill is marked as "legacy awaiting research upgrade" and there's no fresh web research captured since your training cutoff.

What's Working Well

  • Solid module structure — Your SKILL.md stays lean while detailed content lives in modules/. That's exactly how PDA should work. Not bloated, not sparse.
  • Clear trigger terms — The skill recognizes "meal prep efficiency," "batch cooking," "food storage" — these map directly to real user queries. Good discoverability foundation.
  • Practical workflow — The research checklist and numbered steps give users actual structure, not just vibes. That matters for utility.
  • Token economy — You're not wasting words. The metadata is tight, descriptions are specific, no fluff narrative.

The Big One: Legacy Status Is Blocking You

Here's the thing: your skill literally says ⚠️ Legacy template awaiting research upgrade in the status field. That's costing you 10 points and signaling to users that this isn't fresh.

Why it matters: Claude skills need current information. Meal prep best practices, food safety guidelines, and storage techniques evolve. Your skill was last updated in November 2025, but you haven't captured any web research since the training cutoff.

The fix:

  1. Run through your modules/research-checklist.md completely
  2. Capture fresh sources (blog posts, USDA guidelines, recent nutritionist articles from 2025+)
  3. Update the status from "legacy awaiting research" to something like "upgraded with current research"
  4. Add dated sources to your metadata so users know this is current

This alone gets you +10 points and changes the entire perception of the skill.

Other Things Worth Fixing

  1. Description needs trigger phrases — Your description says "Expert in batch cooking, meal planning..." but doesn't include the phrases users actually type. Add something like: "Use when asked to 'meal prep efficiency guru,' 'run meal prep efficiency guru,' or 'meal prep efficiency guru help'." This is +2 points and improves discoverability.

  2. Missing input/output examples — You have good structure, but no concrete "if someone asks X, here's what the skill delivers" examples. Add 2-3 realistic scenarios to SKILL.md (like "User asks: 'How do I prep 7 days of protein?' → Skill delivers: batch cooking timeline with storage labels").

  3. Confidence level is low — The research checklist mentions capturing information, but the overall confidence flag needs to be bumped to "medium" or "high" once you complete that research. Right now it signals uncertainty.

Quick Wins

  • Highest impact: Complete research upgrade + update status (nets you ~10 points)
  • Next level: Add trigger phrases to description (+2 points)
  • Polish: Include 2-3 concrete examples of user queries and skill responses
  • Final touch: Set confidence to "medium" or "high" in metadata once research is done

You've got a solid foundation here. The architecture is clean, the modular approach is right. Just need to get it off "legacy" status and add some fresh research so it feels current and trustworthy.


Checkout your skill here: [SkillzWave.ai](https://skillzwave.ai) | [SpillWave](https://spillwave.com) We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions