Agent skill · Security

wedding-budget

Build a wedding budget that survives to the wedding — allocation by real shares, the per-guest lever made explicit, the routinely-forgotten line items priced in from day one, and a contingency that isn't decorative. Use when asked make a wedding budget, how do people split X across a wedding, we have N dollars and M guests, or why is our wedding over budget. Produces the allocation table from the script, the guest-count math, the forgotten-items audit, and the track-against-actuals discipline.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorships scriptsMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill wedding-budget --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: yes
Path: skills/wedding-budget/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Wedding Budget Skill Wedding budgets die two deaths: the guest list (every name is a per-head catering multiple) and the forgotten line items (vendor meals, alterations, service charges, overtime — the ~10% that appears in month eleven with no budget line waiting for it). This skill builds the budget with both priced in from day one: allocation across categories with the shares stated as defaults not laws, the per-guest lever computed so trade-offs are conscious, and a contingency line defended as load-bearing rather than skimmed first. ## What This Skill Produces - **The allocation table** — every category with its share and amount, from the script, overridable per real quotes - **The guest math** — per-guest cost and what cutting/adding 10 names actually moves - **The forgotten-items audit** — the standard omissions, each assigned to a category's line now - **The tracking discipline** — budget vs. quoted vs. actual, and the rule for when a category busts ## Required Inputs Ask for these if not provided: - **The all-in number** — the real total including everything (rings, attire, the honeymoon in or out — decide and label), and who's contributing what (money with strings gets i

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Programmatic Helper
  4. Framework: The Survival Rules
  5. Output Format
  6. The Allocation
  7. The Guest Lever
  8. Forgotten Items — Now Budgeted
  9. Tracking
  10. Quality Checks
  11. Anti-Patterns
Ships with 1 file
  • scripts/wedding_budget.py
Commands it runs
python3 scripts/wedding_budget.py --budget 30000 --guests 110
python3 scripts/wedding_budget.py --budget 30000 --guests 110 --venue-food-pct 45 --json
More from pm-claude-skills
All skills →
About this skill
What does the wedding-budget skill do?

Build a wedding budget that survives to the wedding — allocation by real shares, the per-guest lever made explicit, the routinely-forgotten line items priced in from day one, and a contingency that isn't decorative. Use when asked make a wedding budget, how do people split X across a wedding, we have N dollars and M guests, or why is our wedding over budget. Produces the allocation table from the script, the guest-count math, the forgotten-items audit, and the track-against-actuals discipline.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill wedding-budget --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going