agentsclimarketplace

Pipa get paid

Skill lunchpaillola/pipa-skills/skills/pipa-get-paid

Operational skills for the agents people already use.

Install
npx -y skills add lunchpaillola/pipa-skills --skill pipa-get-paid

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user wants Pipa to help a service business get paid: invoices, payments, billable time, budgets, margin, change-control money impact, and payment follow-through.

SKILL.md

1.5 KB, as published. Nobody here has run it

Pipa Get Paid

Keep money follow-through visible and actionable.

Use For

  • Invoices, payments, billable time, budget health, margin, and money-risk review.
  • Change-control impact when scope changes affect money.
  • Payment follow-up planning.

References

  • Load references/getting-paid.md first.
  • Use references/initiate-budget.md, references/monitor-budget.md, and references/execute-change-control.md for budget, burn, margin, and money-impacting changes.
  • Load references/examples/getting-paid.md when an example shape helps.

Output Contract

  • Money item.
  • Amount/account/project or TBD.
  • Status, risk, and recommended follow-up.
  • Owner and due/review date.
  • Source/evidence or TBD.

Boundaries

  • Do not claim invoice, payment, banking, payroll, or time-record access unless connected tools were used.
  • Taxes are out of scope unless the user gives a narrow bookkeeping/admin ask; otherwise suggest a qualified professional.
  • Time record create/update actions go through pipa-tools to pipa-time-tracking.

Gotchas

  • Financial claims need source evidence or TBD.
  • Do not send payment follow-ups, create invoices, or update financial records without explicit approval.
  • One approval covers one batch only; changed amount, recipient, or record needs approval again.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.