Freelance back office

Price your work, invoice it, chase late payments, and match every receipt to your books.

Install the 5 skills below in order, one at a time. Each block is one complete install prompt. After the last skill, list each skill with its trigger phrases.

===== SKILL 1 OF 5: Freelance Rate Calculator =====

To install the Freelance Rate Calculator skill, save the skill source below as ~/workspace/skills/freelance-rate-calculator/SKILL.md, then tell Muse to use it whenever you want to work out what to charge.

--- SOURCE ---
---
name: freelance-rate-calculator
description: Work out a freelance hourly rate, day rate, and project quote from target income, business expenses, taxes set aside, and realistic billable hours. Use when the user says "freelance rate", "what should I charge", "calculate my rate", "hourly rate calculator", "day rate", "quote this project", or wants to raise, check, or defend a price for client work.
---

## Purpose
Turn a freelancer's real numbers into a rate that covers income, costs, and time off, with math the user can check and a range they can negotiate from, instead of a price guessed from what others charge.

## Workflow
1. Gather the inputs: target annual take-home pay, yearly business expenses, a taxes set-aside percentage, weeks worked per year, and realistic billable hours per week. Ask for missing numbers, and never fill them in silently.
2. Show the math step by step: add expenses and the taxes set-aside to the target income to get the revenue needed, then divide by total billable hours to get the hourly floor.
3. Build the range: present the hourly floor as the low end, a target rate above it for profit and slow months, and a stretch rate for premium or rush work, each labeled clearly.
4. Price the project: multiply estimated hours by the target rate, add a line for revisions or scope risk when the brief is vague, and show the day rate as eight times the hourly rate or the user's own working day length.
5. Sense-check the result: compare it with the user's current rate, flag it when the floor lands above what the market for that work usually pays, and suggest honest levers: fewer expenses, more billable hours, or a narrower service.
6. Write the quote note: a short paragraph the user can paste into a proposal, stating what the rate covers, what is out of scope, and that revisions beyond the agreed count are billed extra.

## Output Contract
- Inputs used: every number, with any assumption flagged as an assumption to confirm.
- Math breakdown: revenue needed, billable hours, and each division shown line by line.
- Rate range: low, target, and stretch hourly rates, plus the day rate.
- Project quote: estimated hours, rate used, total, and any scope-risk line.
- Sense-check: how the new rate compares with the current rate, and levers if the floor looks high.
- Quote note: ready to paste, covering scope and extra revisions.

## Operating Rules
- Never invent expenses, hours, weeks worked, or a tax percentage. If the user does not give a number, ask for it or mark it plainly as an assumption.
- Never present the result as tax advice, legal advice, or financial advice. Suggest the user check tax figures with their own accountant.
- Never send a quote to a client, accept work, or agree to a price on the user's behalf. The user always makes the final call.
- Never round away the story: show the full math, even when the answer is awkward, so the user can spot a wrong input.
- Never price from a competitor's rate alone. The floor comes from the user's own numbers first, and market comparison is only a sense-check.
- If the brief is vague, price with a stated hours range and a scope-risk line, not a single confident total.

===== END OF SKILL 1 OF 5 =====

===== SKILL 2 OF 5: Invoice Drafter =====

Install the "Invoice Drafter" skill. Its full source is below. Create it
at ~/workspace/skills/invoice-drafter/SKILL.md following skill-creator
conventions (name and description frontmatter; Purpose, Workflow,
Output Contract, Operating Rules sections). Then confirm it is
installed and tell me the trigger phrases.

--- SOURCE ---
---
name: invoice-drafter
description: Turn completed work and timesheet lines into a draft invoice and a client-ready summary. Trigger phrases: "draft an invoice", "make an invoice for", "invoice my client".
---
# Purpose

Turn a list of completed work into a draft invoice plus a
plain-language summary a client can read without asking follow-up
questions. The human always reviews and sends; the skill never
sends anything.

# Workflow

1. Read the work: timesheet lines, project notes, or a paste of
   completed tasks. Ask for the client name, rate, currency, and
   billing period if any are missing.
2. Group the lines into invoice items: date or milestone, a
   description of the work in client language, hours or quantity,
   rate, line total.
3. Compute subtotal, tax if the user gives a rate, and total. Show
   the math so the human can check it.
4. Draft a client-ready summary: what was done, in what period,
   and the total due, in two or three short paragraphs.
5. Write the draft in the Output Contract shape. Never mark it
   final, never send it, never change a price without asking.

# Output Contract

- Draft invoice: client name, billing period, line items
  (description, hours or quantity, rate, line total), subtotal,
  tax, total due, payment terms placeholder.
- Client summary: short prose recap of the work and the total.
- Questions list: everything the skill had to assume, so the
  human can verify before sending.

# Operating Rules

- Never send the invoice or contact the client.
- Never finalize, mark paid, or change a price on your own.
- Never invent hours, rates, or dates; flag gaps as questions.
- A human reviews and sends. Every time.

===== END OF SKILL 2 OF 5 =====

===== SKILL 3 OF 5: Invoice Chaser =====

Install the "Invoice Chaser" skill. Its full source is below. Create it
at ~/workspace/skills/invoice-chaser/SKILL.md following skill-creator
conventions (name and description frontmatter; Purpose, Workflow,
Output Contract, Operating Rules sections). Then confirm it is
installed and tell me the trigger phrases.

--- SOURCE ---
---
name: invoice-chaser
description: Draft polite, escalating payment reminders for overdue invoices: gentle nudge, firm follow-up, and final notice. Trigger phrases: "chase my invoice", "draft a payment reminder", "follow up on overdue invoice".
---
# Purpose

Help freelancers and small businesses get paid on time without the
awkwardness. Invoice Chaser takes an overdue invoice and drafts the
right reminder for the moment: a friendly nudge early on, a firmer
follow-up when silence stretches, and a final notice when patience
runs out.

# Workflow

1. Collect the facts: client name, invoice number, amount, original
   due date, days overdue, and any contact already attempted.
2. Choose the stage by days overdue and prior contact:
   - Stage 1 (1-14 days): gentle nudge, assumes an oversight.
   - Stage 2 (15-44 days): firm follow-up, asks for a payment date.
   - Stage 3 (45+ days): final notice, states consequences from the
     contract and a deadline for response.
3. Draft the reminder in the stage's tone, using only facts the user
   provided or confirmed.
4. Include a clear subject line, the invoice details, the amount
   due, and one specific ask (pay by a date, or reply with a date).
5. Save the client, invoice number, stage, and date to memory, so
   the next run escalates instead of repeating the same message.

# Output Contract

Each reminder has three parts, in this order:

- Subject: one line, includes the invoice number and amount.
- Body: short, professional, stage-appropriate tone.
- Next step: what to do if this one gets no reply (for example,
  "escalate to Stage 2 after 7 days").

Never send. Present the draft and wait for the user's approval.

# Operating Rules

- Never send a reminder without the user's explicit approval.
- Never invent an invoice number, amount, due date, or payment
  terms. Use only what the user provides.
- Never mention late fees, interest, or penalties unless the user's
  contract includes them.
- Never threaten legal action, collections, or public complaints.
- Keep every message professional and brief. Frustration stays out
  of the draft.
- If the client already paid or disputed the invoice, stop and say
  so instead of drafting.

===== END OF SKILL 3 OF 5 =====

===== SKILL 4 OF 5: Expense Receipt Wrangler =====

Install the "Expense Receipt Wrangler" skill. Its full source is
below. Create it at ~/workspace/skills/expense-receipt-wrangler/SKILL.md
following skill-creator conventions (name and description
frontmatter; Purpose, Workflow, Output Contract, Operating Rules
sections). Then confirm it is installed and tell me the trigger
phrases.

--- SOURCE ---
---
name: expense-receipt-wrangler
description: Turn receipt photos into a running expense log: merchant, date, total, and category appended to one CSV. Trigger phrases: "log this receipt", "add this expense", "track this receipt".
---
# Purpose

Keep a running expense log with zero bookkeeping effort. The user
photos a receipt; the skill extracts the fields and appends one
row.

# Workflow

1. Read the receipt photo. Extract: merchant name, transaction
   date, total amount, and payment method if shown.
2. Assign a category from the user's category list. Ask the user to
   set the list once; until then use: groceries, dining,
   transport, home, health, entertainment, other.
3. If any field is unreadable, ask the user for that field only.
   Never guess an amount.
4. Append one row to expenses.csv in the workspace:
   date, merchant, category, total, payment method, photo file
   name.
5. Confirm back in one line: merchant, total, category.
6. On request ("summarize my spending"), total by category for a
   date range the user names.

# Output Contract

- expenses.csv: date,merchant,category,total,payment_method,photo
- Confirmations: one line per receipt
- Summaries: category totals for the requested range, plain text

# Operating Rules

- Never guess a total or a date. Ask when the photo is unclear.
- Never move, rename, or delete the receipt photo.
- The log lives in the user's workspace only. Nothing is sent
  anywhere.
- Never ask for banking logins or card numbers; the photo is the
  only input.

===== END OF SKILL 4 OF 5 =====

===== SKILL 5 OF 5: Reconciliation Checker =====

Install the "Reconciliation Checker" skill. Its full source is below.
Create it at ~/workspace/skills/reconciliation-checker/SKILL.md
following skill-creator conventions (name and description frontmatter;
Purpose, Workflow, Output Contract, Operating Rules sections). Then
confirm it is installed and tell me the trigger phrases.

--- SOURCE ---
---
name: reconciliation-checker
description: Compares two money sources (invoices vs spreadsheet, payouts vs bank export) and flags every mismatch. Trigger phrases: "reconcile my invoices", "check my reconciliation", "find the mismatches".
---
# Purpose

Find every line that does not agree between two records of the same
money. Typical pairs: invoices against a tracking spreadsheet,
payout reports against a bank export, donation receipts against a
ledger, platform sales against deposited amounts. Reconciliation
Checker normalizes the two sources, matches their lines, and reports
what matches, what is missing on either side, and what disagrees.

# Workflow

1. Ask which two sources to compare, and get both in a readable
   form: CSV, spreadsheet, pasted text, or a structured list the
   user provides. Do not proceed on only one side.
2. Ask which field is the match key: invoice number, order ID,
   date plus amount, or a combination. Confirm the date format and
   the currency before matching.
3. Normalize both sources: trim whitespace, standardize dates to one
   format, and express amounts as plain numbers. Note which side
   needed the most cleanup; that is where errors hide.
4. Match lines on the agreed key. Mark each line as: matched, only
   in source A, only in source B, or matched but with a differing
   field.
5. For lines matched but disagreeing, record the field, the value on
   each side, and the difference in plain numbers.
6. Sort findings by impact: amount differences first (largest
   first), then lines present on one side only.
7. Write the report in the Output Contract shape and send it.

# Output Contract

- Summary: counts of matched lines, lines only in A, lines only in
  B, and lines with amount differences, plus the total dollar
  value of all differences.
- Mismatch table: one row per issue, in impact order. Each row has
  the match key, the issue type, the value in source A, the value
  in source B, and the difference.
- Cleanup note: what was normalized, so the user can judge whether
  the matches are trustworthy.
- Next step suggestion: a plain sentence on where to look first
  (for example, "two payouts are missing on the bank side; check
  the payout delay policy"). No diagnosis is presented as fact.

# Operating Rules

- Never edit, overwrite, or append to either source file. Work on
  copies in memory and report the findings.
- Never move money, pay a bill, or contact a bank, client, or
  platform on the user's behalf. Flag only.
- Never treat a guessed match as confirmed. If the match key is
  ambiguous, say so and list the candidates separately.
- Never fabricate a line to make the totals balance. Unmatched
  lines stay unmatched in the report.
- Never share the report or the source data with anyone but the
  user.

===== END OF SKILL 5 OF 5 =====

Ready to copy.

Before you install

A shared skill carries somebody else's instructions. Read the source before you install it.
Never paste an API key, password, or token into anything a skill asks for. Legitimate skills use Muse's own secure flows.
Installing copies the setup into your own environment. It gives the author nothing.

Skills in this pack

Freelance Rate Calculator
Turns target income, expenses, and billable hours into an hourly floor and a day rate.
skillMoney & financehourly floorday rateproject quotenegotiation rangemath breakdownquote note
by Muse Skills editors · Written for this directory
ViewTo install the Freelance Rate Calculator skill, save the skill source below as ~/workspace/skills/freelance-rate-calculator/SKILL.md, then tell Muse to use it whenever you want to work out what to charge. --- SOURCE --- --- name: freelance-rate-calculator description: Work out a freelance hourly rate, day rate, and project quote from target income, business expenses, taxes set aside, and realistic billable hours. Use when the user says "freelance rate", "what should I charge", "calculate my rate", "hourly rate calculator", "day rate", "quote this project", or wants to raise, check, or defend a price for client work. --- ## Purpose Turn a freelancer's real numbers into a rate that covers income, costs, and time off, with math the user can check and a range they can negotiate from, instead of a price guessed from what others charge. ## Workflow 1. Gather the inputs: target annual take-home pay, yearly business expenses, a taxes set-aside percentage, weeks worked per year, and realistic billable hours per week. Ask for missing numbers, and never fill them in silently. 2. Show the math step by step: add expenses and the taxes set-aside to the target income to get the revenue needed, then divide by total billable hours to get the hourly floor. 3. Build the range: present the hourly floor as the low end, a target rate above it for profit and slow months, and a stretch rate for premium or rush work, each labeled clearly. 4. Price the project: multiply estimated hours by the target rate, add a line for revisions or scope risk when the brief is vague, and show the day rate as eight times the hourly rate or the user's own working day length. 5. Sense-check the result: compare it with the user's current rate, flag it when the floor lands above what the market for that work usually pays, and suggest honest levers: fewer expenses, more billable hours, or a narrower service. 6. Write the quote note: a short paragraph the user can paste into a proposal, stating what the rate covers, what is out of scope, and that revisions beyond the agreed count are billed extra. ## Output Contract - Inputs used: every number, with any assumption flagged as an assumption to confirm. - Math breakdown: revenue needed, billable hours, and each division shown line by line. - Rate range: low, target, and stretch hourly rates, plus the day rate. - Project quote: estimated hours, rate used, total, and any scope-risk line. - Sense-check: how the new rate compares with the current rate, and levers if the floor looks high. - Quote note: ready to paste, covering scope and extra revisions. ## Operating Rules - Never invent expenses, hours, weeks worked, or a tax percentage. If the user does not give a number, ask for it or mark it plainly as an assumption. - Never present the result as tax advice, legal advice, or financial advice. Suggest the user check tax figures with their own accountant. - Never send a quote to a client, accept work, or agree to a price on the user's behalf. The user always makes the final call. - Never round away the story: show the full math, even when the answer is awkward, so the user can spot a wrong input. - Never price from a competitor's rate alone. The floor comes from the user's own numbers first, and market comparison is only a sense-check. - If the brief is vague, price with a stated hours range and a scope-risk line, not a single confident total.
Invoice Drafter
Turns completed work and timesheet lines into a draft invoice; a human always sends it.
Tested in MuseskillMoney & financeinstructionsworkflowtemplates
by Muse Skills editors · Written for this directory
ViewInstall the "Invoice Drafter" skill. Its full source is below. Create it at ~/workspace/skills/invoice-drafter/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: invoice-drafter description: Turn completed work and timesheet lines into a draft invoice and a client-ready summary. Trigger phrases: "draft an invoice", "make an invoice for", "invoice my client". --- # Purpose Turn a list of completed work into a draft invoice plus a plain-language summary a client can read without asking follow-up questions. The human always reviews and sends; the skill never sends anything. # Workflow 1. Read the work: timesheet lines, project notes, or a paste of completed tasks. Ask for the client name, rate, currency, and billing period if any are missing. 2. Group the lines into invoice items: date or milestone, a description of the work in client language, hours or quantity, rate, line total. 3. Compute subtotal, tax if the user gives a rate, and total. Show the math so the human can check it. 4. Draft a client-ready summary: what was done, in what period, and the total due, in two or three short paragraphs. 5. Write the draft in the Output Contract shape. Never mark it final, never send it, never change a price without asking. # Output Contract - Draft invoice: client name, billing period, line items (description, hours or quantity, rate, line total), subtotal, tax, total due, payment terms placeholder. - Client summary: short prose recap of the work and the total. - Questions list: everything the skill had to assume, so the human can verify before sending. # Operating Rules - Never send the invoice or contact the client. - Never finalize, mark paid, or change a price on your own. - Never invent hours, rates, or dates; flag gaps as questions. - A human reviews and sends. Every time.
Invoice Chaser
Drafts polite, escalating payment reminders for overdue invoices.
Tested in MuseskillMoney & financeinstructionsworkflowtemplates
by Muse Skills editors · Written for this directory
ViewInstall the "Invoice Chaser" skill. Its full source is below. Create it at ~/workspace/skills/invoice-chaser/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: invoice-chaser description: Draft polite, escalating payment reminders for overdue invoices: gentle nudge, firm follow-up, and final notice. Trigger phrases: "chase my invoice", "draft a payment reminder", "follow up on overdue invoice". --- # Purpose Help freelancers and small businesses get paid on time without the awkwardness. Invoice Chaser takes an overdue invoice and drafts the right reminder for the moment: a friendly nudge early on, a firmer follow-up when silence stretches, and a final notice when patience runs out. # Workflow 1. Collect the facts: client name, invoice number, amount, original due date, days overdue, and any contact already attempted. 2. Choose the stage by days overdue and prior contact: - Stage 1 (1-14 days): gentle nudge, assumes an oversight. - Stage 2 (15-44 days): firm follow-up, asks for a payment date. - Stage 3 (45+ days): final notice, states consequences from the contract and a deadline for response. 3. Draft the reminder in the stage's tone, using only facts the user provided or confirmed. 4. Include a clear subject line, the invoice details, the amount due, and one specific ask (pay by a date, or reply with a date). 5. Save the client, invoice number, stage, and date to memory, so the next run escalates instead of repeating the same message. # Output Contract Each reminder has three parts, in this order: - Subject: one line, includes the invoice number and amount. - Body: short, professional, stage-appropriate tone. - Next step: what to do if this one gets no reply (for example, "escalate to Stage 2 after 7 days"). Never send. Present the draft and wait for the user's approval. # Operating Rules - Never send a reminder without the user's explicit approval. - Never invent an invoice number, amount, due date, or payment terms. Use only what the user provides. - Never mention late fees, interest, or penalties unless the user's contract includes them. - Never threaten legal action, collections, or public complaints. - Keep every message professional and brief. Frustration stays out of the draft. - If the client already paid or disputed the invoice, stop and say so instead of drafting.
Expense Receipt Wrangler
Photo a receipt; it logs merchant, date, total, and category.
Tested in MuseskillMoney & financeinstructionsworkflowexpense-log
by Muse Skills editors · Written for this directory
ViewInstall the "Expense Receipt Wrangler" skill. Its full source is below. Create it at ~/workspace/skills/expense-receipt-wrangler/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: expense-receipt-wrangler description: Turn receipt photos into a running expense log: merchant, date, total, and category appended to one CSV. Trigger phrases: "log this receipt", "add this expense", "track this receipt". --- # Purpose Keep a running expense log with zero bookkeeping effort. The user photos a receipt; the skill extracts the fields and appends one row. # Workflow 1. Read the receipt photo. Extract: merchant name, transaction date, total amount, and payment method if shown. 2. Assign a category from the user's category list. Ask the user to set the list once; until then use: groceries, dining, transport, home, health, entertainment, other. 3. If any field is unreadable, ask the user for that field only. Never guess an amount. 4. Append one row to expenses.csv in the workspace: date, merchant, category, total, payment method, photo file name. 5. Confirm back in one line: merchant, total, category. 6. On request ("summarize my spending"), total by category for a date range the user names. # Output Contract - expenses.csv: date,merchant,category,total,payment_method,photo - Confirmations: one line per receipt - Summaries: category totals for the requested range, plain text # Operating Rules - Never guess a total or a date. Ask when the photo is unclear. - Never move, rename, or delete the receipt photo. - The log lives in the user's workspace only. Nothing is sent anywhere. - Never ask for banking logins or card numbers; the photo is the only input.
Reconciliation Checker
Compares two money sources line by line and flags every mismatch.
skillMoney & financeinstructionsworkflowreport format
by Muse Skills editors · Written for this directory
ViewInstall the "Reconciliation Checker" skill. Its full source is below. Create it at ~/workspace/skills/reconciliation-checker/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: reconciliation-checker description: Compares two money sources (invoices vs spreadsheet, payouts vs bank export) and flags every mismatch. Trigger phrases: "reconcile my invoices", "check my reconciliation", "find the mismatches". --- # Purpose Find every line that does not agree between two records of the same money. Typical pairs: invoices against a tracking spreadsheet, payout reports against a bank export, donation receipts against a ledger, platform sales against deposited amounts. Reconciliation Checker normalizes the two sources, matches their lines, and reports what matches, what is missing on either side, and what disagrees. # Workflow 1. Ask which two sources to compare, and get both in a readable form: CSV, spreadsheet, pasted text, or a structured list the user provides. Do not proceed on only one side. 2. Ask which field is the match key: invoice number, order ID, date plus amount, or a combination. Confirm the date format and the currency before matching. 3. Normalize both sources: trim whitespace, standardize dates to one format, and express amounts as plain numbers. Note which side needed the most cleanup; that is where errors hide. 4. Match lines on the agreed key. Mark each line as: matched, only in source A, only in source B, or matched but with a differing field. 5. For lines matched but disagreeing, record the field, the value on each side, and the difference in plain numbers. 6. Sort findings by impact: amount differences first (largest first), then lines present on one side only. 7. Write the report in the Output Contract shape and send it. # Output Contract - Summary: counts of matched lines, lines only in A, lines only in B, and lines with amount differences, plus the total dollar value of all differences. - Mismatch table: one row per issue, in impact order. Each row has the match key, the issue type, the value in source A, the value in source B, and the difference. - Cleanup note: what was normalized, so the user can judge whether the matches are trustworthy. - Next step suggestion: a plain sentence on where to look first (for example, "two payouts are missing on the bank side; check the payout delay policy"). No diagnosis is presented as fact. # Operating Rules - Never edit, overwrite, or append to either source file. Work on copies in memory and report the findings. - Never move money, pay a bill, or contact a bank, client, or platform on the user's behalf. Flag only. - Never treat a guessed match as confirmed. If the match key is ambiguous, say so and list the candidates separately. - Never fabricate a line to make the totals balance. Unmatched lines stay unmatched in the report. - Never share the report or the source data with anyone but the user.