AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Pipa Get Paid

skill-lunchpaillola-pipa-skills-pipa-get-paid · by lunchpaillola

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.

↗ Website ↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-lunchpaillola-pipa-skills-pipa-get-paid

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Pipa Get Paid? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Finance & Payments