Qsr Food Cost Diagnostic
v1.0.1Weekly food cost variance diagnostic for restaurant and franchise operators. Four-lever system that catches COGS drift weekly instead of monthly — ordering,...
⭐ 0· 83·0 current·0 all-time
byBlake Mcpherson@blake27mc
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and runtime instructions all describe a conversational diagnostic workflow for weekly food-cost variance and the resources asked for (operator answers, recipe/inventory checks) match that purpose; there are no unrelated credentials, binaries, or install steps requested.
Instruction Scope
Instructions stay within the operator-guided diagnostic scope (questions to ask, checklist of levers, and recommended remediations). One notable point: the skill instructs the agent to store each diagnostic run in memory (a defined format). That means business-sensitive operational data (COGS %, top items, actions) will be persisted to the agent's memory — make sure you consent to that and understand retention/visibility settings.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing is downloaded or written to disk by the skill itself, which minimizes installation risk.
Credentials
The skill requires no environment variables, credentials, or config paths. It asks users to reference their POS, vendor invoices, or ordering system manually but does not request direct access tokens or unrelated credentials.
Persistence & Privilege
always is false and the skill is user-invocable (normal). However, the SKILL.md explicitly requests persistent memory entries for each diagnostic run; this is reasonable for trend tracking but is a persistence decision you should review (who can read those memories, how long they are kept).
Assessment
This skill appears internally consistent and safe to install, but review how the agent's memory is configured before use: the skill asks to store each diagnostic run (COGS %, items, actions) which may contain sensitive business data. If you don't want that data persisted, disable or clear memory for this skill or avoid entering confidential vendor/account details. Also confirm the agent will not be given direct access to your POS or vendor systems (the skill expects the operator to look things up manually). Finally, test the workflow with non-sensitive example data and verify retention and access controls for the stored diagnostics before using it on live operations.Like a lobster shell, security has layers — review code before you run it.
latestvk97b0v7cy6g0q0vxsrskx15ges83p06h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.