Qsr Ghost Inventory Hunter
v1.0.0Identifies unaccounted inventory loss in restaurant operations by cross-referencing sales volume against theoretical recipe yields. Pinpoints whether missing...
⭐ 0· 38·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
The skill's name and description (finding ghost inventory by comparing sales, yields, and counts) match the SKILL.md instructions. It requests no binaries, credentials, or installs — appropriate because it operates by asking the operator for POS, inventory, and delivery data.
Instruction Scope
The instructions direct the agent to ask the operator for sales reports, inventory counts, deliveries, and recipe yields and to compute theoretical vs actual usage and diagnose causes. The guidance is specific to the task and does not ask the agent to read system files, access unrelated environment variables, or exfiltrate data to external endpoints. It does recommend storing investigation summaries in agent memory, which is consistent with being an investigative assistant.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes risk because nothing is written to disk or fetched at install time.
Credentials
The skill requests no environment variables, credentials, or config paths. All required data is user-supplied during the investigation (POS reports, counts, yields), which is proportionate to the described function.
Persistence & Privilege
always:false and normal autonomous invocation settings. The only persistence the skill specifies is storing investigation entries in memory (a defined, limited format). It doesn't request system-wide changes or other skills' configurations.
Assessment
This skill is instruction-only and appears coherent with its purpose, but consider these practical points before installing: 1) The skill relies on you supplying POS exports, inventory counts, and delivery info — do not paste unrelated sensitive credentials or full customer PII into the conversation. 2) If you intend to integrate this with your POS/accounting systems later, prefer minimal-scoped API credentials and review any connector carefully. 3) The skill stores investigation summaries in agent memory; if you are concerned about retention, clear or limit agent memory after use. 4) Outputs (e.g., allegations of theft) may have legal or HR consequences—verify conclusions with physical audits before taking action. 5) If you want the skill to read data automatically, request an integration that explicitly lists required permissions; as-is, it only uses operator-provided data.Like a lobster shell, security has layers — review code before you run it.
latestvk976qsv40xyaww6xnyc637t2jh843jh3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.