Wedding Planner

Plan weddings with budget guardrails, guest-list scenarios, vendor scorecards, payment tracking, and deadline-driven coordination.

This skill appears coherent and low-risk, but review these points before enabling: - Persistent memory is stored locally at ~/wedding-planner/. Only enable it if you’re comfortable with files being created there. - The skill explicitly says not to store payment credentials or full contracts unless you ask; avoid putting passwords, API keys, or sensitive scanned contracts into the notebook. - Inspect the created files and set restrictive file permissions (e.g., chmod 600) if they may contain personal details. Consider encrypting or storing very sensitive documents outside this folder. - If you do not want the agent to act proactively (e.g., trigger reminders or modify files without explicit approval), keep persistent memory disabled or adjust activation settings during setup. - Because this is instruction-only, there's no downloaded code, but you should still periodically check the folder contents and backup important documents elsewhere. If you want greater assurance, ask the skill (or the vendor) to show exactly what it will write before you approve persistent memory and test with non-sensitive sample data first.

Type: OpenClaw Skill Name: wedding-planner Version: 1.0.0 The wedding-planner skill is a well-structured organizational tool designed to assist users with wedding logistics through local markdown-based record-keeping in `~/wedding-planner/`. The skill contains no executable code, network requests, or instructions to access sensitive system files; instead, it provides templates and logic for managing budgets, guest lists, and vendor evaluations. It explicitly includes privacy guardrails, such as advising the agent not to store payment credentials or personal identification documents.