Restaurant Operator

v1.0.0

Manage restaurant operations with recipe creation, inventory prediction, menu optimization, staff scheduling, and food safety compliance.

0· 56·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description (recipe scaling, inventory prediction, menu engineering, scheduling, food-safety guidance) align with the SKILL.md content. The skill lists optional integrations (POS, weather, reservations) but does not require unrelated credentials or binaries, which is proportional to the stated purpose.
Instruction Scope
SKILL.md is high-level documentation and runtime instructions are only descriptive; there are no commands, file paths, or instructions to read system files or exfiltrate data. It does not ask the agent to access unrelated system state.
Install Mechanism
No install spec and no code files are present (instruction-only). Nothing is written to disk or downloaded by the skill bundle itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. It mentions optional integrations that would require credentials at integration time, which is expected and reasonable, but those are not requested by the skill as packaged.
Persistence & Privilege
Flags show normal privileges (always:false, agent-invocable allowed). The metadata includes agentRequired:true and an agentName, but the skill does not request persistent system changes or cross-skill configuration.
Assessment
This skill is instruction-only and internally consistent, but before installing or connecting it to live systems: 1) verify the vendor/author (El Rudo Larios LLC) and their support contact; 2) be prepared to provide POS, reservation, or weather API credentials only when you explicitly enable those integrations — store those secrets securely; 3) test the skill in a non-production environment first (especially pricing/enterprise features); and 4) confirm the commercial license and any data-sharing/privacy terms the vendor requires when you enable integrations.

Like a lobster shell, security has layers — review code before you run it.

latestvk978tw7szm3yrbmqrrk8s66n8n83tjq6

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments