Salon Skill

v0.0.1

A comprehensive skill for beauty salon operations — covering hair, nails, and skin services. Use this skill whenever anyone asks about salon appointments, bo...

0· 84·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (salon operations: bookings, menus, consultations, marketing) align with the skill's contents. There are no unrelated required binaries, environment variables, or install steps; referenced files (services.md, consultation.md) are consistent with a salon assistant.
Instruction Scope
Runtime instructions are limited to conversational intake, generating confirmations, recommending services, and creating marketing copy. This is within scope, but the skill explicitly directs collecting PII (full name, contact number, notes about health/allergies) and creating WhatsApp/SMS blasts — activities that carry privacy and consent implications. The SKILL.md does not include guidance on data retention, consent/opt-in for marketing, or safe handling of sensitive client medical/allergy info.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is downloaded or written to disk. This is the lowest-risk install profile and matches the skill's purpose.
Credentials
The skill declares no environment variables, credentials, or config paths. That is proportionate given it is a conversational/template skill. Note: for real-world deployment you will likely add booking-system API keys or SMS provider credentials — these are not present and should be added only when necessary and with least privilege.
Persistence & Privilege
always:false and normal model invocation are used. The skill does not request persistent/system-level privileges or attempt to modify other skills. Nothing here indicates elevated platform privileges.
Assessment
This skill appears coherent for salon use, but take these practical precautions before enabling it for real clients: 1) Fill in the placeholders (salon name, contact info, cancellation policy, real service prices and staff names) so the skill does not output placeholders to customers. 2) Be aware it collects personal data (names, phone numbers, allergies). Ensure you have explicit consent to store and message clients and implement appropriate data-retention and access controls. 3) If you connect this skill to a booking system, SMS/WhatsApp provider, or CRM, add only the minimum credentials required and store them securely (do not paste secrets into skill text). 4) Add explicit opt-in messaging and an unsubscribe method before sending campaigns (legal/regulatory risk for mass SMS/WhatsApp). 5) Review generated confirmations and marketing copy for accuracy and brand/tone before sending, and test flows with dummy data. 6) If you need the skill to integrate with external systems, require a reviewed install/credential flow — the current instruction-only skill will not perform automated bookings until such integrations are added. If you want a security review after adding integration code or install steps, provide those artifacts for re-evaluation.

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

latestvk9758hv53wpg6sr94brkfx92vn84aypp

License

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

Comments