Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Wedding.skill

v1.0.0

Your wedding planning co-pilot. Budget tracker that doesn't lie, vendor manager that doesn't forget, seating chart solver that minimizes family drama. 200+ d...

0· 97·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for realteamprinz/wedding.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Wedding.skill" (realteamprinz/wedding) from ClawHub.
Skill page: https://clawhub.ai/realteamprinz/wedding
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install wedding

ClawHub CLI

Package manager switcher

npx clawhub@latest install wedding
Security Scan
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description (wedding planning, budget, vendors, seating, timeline) align with the files and instructions. No credentials, binaries, or unrelated install steps are declared. The 'self-learning' claim is vague but could reasonably mean the agent logs decisions to local files; this is not obviously malicious but is imprecise.
!
Instruction Scope
SKILL.md instructs storing all data under ~/.wedding-skill/ and explicitly claims 'No cloud' and 'No transmission.' However, the file contains pre-scan prompt-injection signals (unicode-control-chars) which may be an attempt to manipulate agents or scanners. Also, being instruction-only, the skill relies on the agent's runtime permissions to read/write files and to contact external services — the docs assert it won't transmit data but that cannot be enforced by the provided files alone.
Install Mechanism
No install spec or packaged binaries are included (instruction-only), so nothing is automatically downloaded or executed. README includes user-facing install commands referencing third-party names (clawhub/hermes/claude copy) but the registry metadata provides no homepage or authoritative source — low install-surface but user should avoid blindly running external install commands from untrusted origins.
Credentials
The skill declares no required environment variables, no credentials, and no config paths beyond a single user-local folder (~/.wedding-skill/). This is proportionate to the stated purpose of local data storage and planning.
Persistence & Privilege
The skill is not always-enabled and does not request elevated privileges. It will store files under ~/.wedding-skill/ if the agent is instructed to do so — that is a limited, local persistence. Note: autonomous agent invocation is allowed by default (platform normal), which would let the agent run the SKILL.md instructions without further prompts; combine that with the prompt-injection signal for extra caution.
Scan Findings in Context
[unicode-control-chars] unexpected: Hidden/unicode control characters are not expected for a wedding-planning instruction document. These are commonly used for prompt-injection/obfuscation and should be examined. Their presence does not prove maliciousness but increases risk and justifies manual review.
What to consider before installing
This skill appears to do what it says (local wedding planning and budgeting) and requests nothing sensitive, but be cautious before installing or enabling it: 1) Manually inspect SKILL.md/README.md for hidden characters or obfuscated content (the scanner flagged unicode control chars). 2) Don't provide any bank/password/API credentials to the skill — none are required. 3) If you want to run it, install from a trusted source or copy the files yourself rather than running unknown install commands in the README. 4) Consider running the skill in a restricted environment or with limited file permissions so it can only write to a dedicated folder. 5) If you need the 'self-learning' feature to be authentic, ask the maintainer how model updates occur — instruction-only skills can't change model weights and likely just append logs. If you want me to, I can highlight the exact lines with suspicious unicode characters or produce a cleaned version of SKILL.md for safer review.

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

latestvk979d2tcw4wyrb1t10h1prtvth84jc9y
97downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

wedding.skill 💍

Purpose

You got engaged. Congratulations. Now you have 6-12 months to make 200+ decisions, manage 10+ vendors, stay within a budget that 77% of couples exceed, and navigate family politics that make the UN look simple.

Nobody tells you that planning a wedding is a second full-time job. wedding.skill is your co-worker for that job. It tracks your budget honestly, remembers every vendor conversation, manages your guest list, and tells you when you're about to blow $3000 on flowers because you already overspent on the venue.

Not a Pinterest board. Not a checklist app. A self-learning co-pilot that knows YOUR wedding — your budget, your vendors, your family dynamics, your priorities.


Privacy & Consent

This skill records ONLY the couple's own planning decisions, budgets, and vendor information that they voluntarily share. It does NOT access any financial accounts, vendor systems, or external services.

What this skill does:

  • Tracks budget, vendors, timeline, and guest list from your input
  • Identifies when you're over budget and suggests adjustments
  • Remembers vendor deadlines and contract terms you share
  • Stores everything locally on your device

What this skill does NOT do:

  • Connect to bank accounts, credit cards, or payment systems
  • Access vendor booking systems or calendars
  • Make any payments or financial transactions
  • Transmit any data externally

⚠️ Not financial advice. wedding.skill tracks your spending. It does not advise on loans, credit, or financial planning. Consult a financial advisor for those decisions.


Data Storage

All data stored locally. No cloud. No transmission.

~/.wedding-skill/
└── [wedding-name]/
    ├── BUDGET.md              # Budget tracker with actuals vs planned
    ├── vendors.md             # All vendor details and deadlines
    ├── guests.md              # Guest list with RSVPs and seating
    ├── timeline.md            # Master timeline
    └── decisions-log.jsonl    # Every decision tracked
  • Storage location: ~/.wedding-skill/
  • Format: Markdown + JSONL (human-readable)
  • Cloud sync: None
  • Deletion: Remove the folder to delete all data

Core Features

1. Honest Budget Tracker

The feature that saves marriages before they start:

Wedding Budget: Target $30,000

Category          | Budgeted | Spent    | Remaining | Status
Venue             | $8,000   | $9,500   | -$1,500   | ⚠️ OVER
Catering          | $7,000   | $4,200   | $2,800    | 🟡 deposit paid
Photography       | $3,500   | $3,500   | $0        | ✅ paid in full
Flowers           | $2,000   | $0       | $2,000    | 🔲 not booked
DJ/Music          | $1,500   | $500     | $1,000    | 🟡 deposit paid
Dress             | $2,500   | $2,800   | -$300     | ⚠️ OVER
Cake              | $800     | $0       | $800      | 🔲 not booked
Invitations       | $500     | $350     | $150      | ✅ ordered
Misc/Buffer       | $4,200   | $1,100   | $3,100    | 🟡 in use

TOTAL             | $30,000  | $21,950  | $8,050
                  
⚠️ WARNING: You're $1,800 over in Venue + Dress.
This is eating your buffer. At current pace, projected 
final total: $33,400 (+$3,400 over budget).

SUGGESTION: Flowers budget can absorb $500 if you choose 
seasonal flowers. Cake can go $200 under with a smaller 
top tier. That recovers $700. Still $1,100 over.

It doesn't just track. It PREDICTS where you'll end up and tells you before it's too late.

2. Vendor Intelligence

Every vendor, every conversation, every deadline in one place:

Vendor: Blue Sky Photography
Contact: Sarah Chen — sarah@bluesky.com
Booked: March 15
Contract signed: March 20
Deposit paid: $1,500 (March 22)
Balance due: $2,000 (2 weeks before wedding)

Key terms:
- 8 hours coverage
- Second shooter included
- 500+ edited photos, delivered in 6 weeks
- Raw files NOT included (would be +$500)
- Cancellation: 50% refund if 60+ days out

Notes from conversations:
- She prefers golden hour for couple portraits (5:30-6:30pm)
- Needs shot list 2 weeks before
- Has worked at our venue before — knows the good spots
- Allergic to lilies (relevant for bouquet toss shots)

⏰ UPCOMING: Send shot list by [date — 2 weeks before wedding]

3. Guest List & Seating Intelligence

The most political puzzle of your life:

Guest List: 142 invited / 118 confirmed / 12 pending / 12 declined

Dietary needs:
- 8 vegetarian
- 3 vegan
- 2 gluten-free
- 1 nut allergy (Sarah's cousin — FLAG for caterer)

Seating constraints you've told me:
❌ Uncle Mike CANNOT sit near Aunt Linda (the divorce)
❌ Your college friends need to be near the bar
❌ Boss should be at a visible table but not family table
✅ Grandma needs to be close to the exit (mobility)
✅ Kids table near the parents but with space for chaos

Seating suggestion generated with 0 conflicts.

4. Timeline Manager

From engagement to honeymoon, every deadline:

12 months out: ✅ Set budget ✅ Book venue ✅ Book photographer
9 months out:  ✅ Book caterer ✅ Choose wedding party
6 months out:  🟡 Book florist ⬜ Book DJ ⬜ Send save-the-dates
4 months out:  ⬜ Send invitations ⬜ Cake tasting ⬜ Dress fitting #2
2 months out:  ⬜ Final guest count ⬜ Seating chart ⬜ Vows
2 weeks out:   ⬜ Confirm all vendors ⬜ Final payments ⬜ Shot list
1 week out:    ⬜ Rehearsal dinner ⬜ Final timeline ⬜ Breathe

⚠️ OVERDUE: Save-the-dates should have gone out 2 weeks ago.

5. Day-Of Timeline

The hour-by-hour schedule for the actual day:

Wedding Day: Saturday, October 18

8:00am  — Hair & makeup begins (bride + 4 bridesmaids)
10:30am — Photographer arrives for getting-ready shots  
12:00pm — Light lunch for wedding party (DON'T skip this)
1:00pm  — Bride dresses
1:30pm  — First look (garden, north side)
2:00pm  — Wedding party photos
3:00pm  — Guests begin arriving
3:30pm  — Ceremony begins
4:00pm  — Ceremony ends — cocktail hour begins
4:00pm  — Couple photos (golden hour window: 4:30-5:30)
5:00pm  — Guests seated for reception
5:15pm  — Couple entrance
5:30pm  — First dance
5:45pm  — Toasts (best man, maid of honor — 5 min each MAX)
6:00pm  — Dinner service
7:30pm  — Cake cutting
7:45pm  — Parent dances
8:00pm  — Open dance floor
10:00pm — Last song
10:15pm — Sparkler exit

6. Couple Sync

Making sure both partners actually agree:

Decision Log:

Flowers:
  Partner A wants: peonies and garden roses (romantic)
  Partner B wants: whatever's cheapest
  Resolution: seasonal mix with some peonies — saves $600, both happy ✅

Music:
  Partner A wants: live band ($4,000)
  Partner B wants: DJ ($1,500)
  Status: ⚠️ UNRESOLVED — $2,500 difference
  
  Suggestion: DJ for ceremony + cocktail hour, live band for 
  reception first 2 hours, then DJ takes over. Estimated: $3,200.
  Compromise that gives both partners something they want.

Color scheme:
  Both agreed: sage green + dusty rose ✅

7. Family Politics Navigator

The unspoken layer of every wedding:

Things you've told me:
- Mom wants a church ceremony, you want outdoor — RESOLVED (outdoor, mom accepted)
- His mom offered to pay for flowers but wants control of arrangements — IN PROGRESS
- Your divorced parents need separate tables but equal prominence
- Cousin who wasn't invited keeps asking about it — need a response plan

Suggestion for the cousin situation:
"We had to keep the guest list small due to venue capacity. 
We'd love to celebrate with you at [alternative gathering]."

Operating Modes

Budget Mode

Trigger: Any money-related question Behavior: Honest numbers. Projected total. Where you're over. What to cut.

Vendor Mode

Trigger: Vendor question or deadline approaching Behavior: Pull up vendor details. Flag upcoming deadlines. Draft vendor emails.

Guest Mode

Trigger: Guest list or seating questions Behavior: RSVP status. Dietary needs. Seating constraints. Conflict avoidance.

Timeline Mode

Trigger: "What should we be doing now?" or deadline questions Behavior: What's done, what's overdue, what's coming up.

Day-Of Mode

Trigger: Wedding week Behavior: Hour-by-hour timeline. Vendor confirmations. Emergency contacts.

Couple Mode

Trigger: Disagreement or decision needed Behavior: Present both preferences. Suggest compromise. Track resolution.


The Numbers

  • $34,000 — Average US wedding cost
  • 77% — Couples who exceed their budget
  • 200+ — Decisions to make in 6-12 months
  • 10-15 — Vendors to manage simultaneously
  • 72% — Couples using digital planning tools
  • 0 — AI skills built specifically for this

Emotional Guidelines

  1. This is stressful. Acknowledge it. Don't add to it.
  2. Both partners matter. Never take sides. Present both preferences.
  3. Budget honesty saves relationships. Better to know you're over now than get a surprise later.
  4. Family politics are real. Don't dismiss them. Help navigate them.
  5. The goal is the marriage, not the wedding. Gently remind when planning stress overshadows the point.
  6. No judgment on budget. $5,000 wedding or $500,000 wedding — same level of care.

Memory Rules

  1. Never overwrite — every decision logged with date and context
  2. Track changes — "originally wanted X, changed to Y because Z"
  3. Cross-session persistence — always load wedding profile before responding
  4. Timestamp everything
  5. Deadline awareness — proactively flag approaching deadlines

Comments

Loading comments...